Date: Mon, 2 Mar 2009 18:20:33 -0500 From: Michael Proto <mike@jellydonut.org> To: freebsd-ports@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: [headsup] call for assistance with ports broken on -current Message-ID: <1de79840903021520n8442177g9d17b0131913e7c9@mail.gmail.com> In-Reply-To: <20090302004539.GD17890@lonesome.com> References: <20090302004539.GD17890@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 1, 2009 at 7:45 PM, Mark Linimon <linimon@lonesome.com> wrote: > FYI, here's what I posted to ports@ yesterday. =A0Any help fixing these > would be appreciated. =A0(We've already knocked off several of the ones > I initially posted.) > > mcl > > ----- Forwarded message from Mark Linimon <linimon@lonesome.com> ----- > > From: Mark Linimon <linimon@lonesome.com> > To: ports@FreeBSD.org > Subject: [headsup] call for assistance with ports broken on -current > > With 8.0 coming up, it's time to take a look at the ports that have > been broken by some recent changes to freebsd-current. =A0I have put > a list of these ports, categorized by which change, on the wiki at > http://wiki.freebsd.org/PortsBrokenOnCurrent. > > These changes are: tty changes, jail changes, import of strndup(3), > ARP v2, libusb20, and possibly VFS. =A0(libusb20 has not yet been run > through pointyhat, and its list is probably incomplete.) > What about non-ports breakage, ie- /bin/sh read builtin failing after the tty changes :) http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/129566 Thanks, Proto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1de79840903021520n8442177g9d17b0131913e7c9>