Date: Mon, 2 Mar 2009 11:03:38 +0000 From: Florent Thoumie <flz@xbsd.org> To: rea-fbsd@codelabs.ru Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: [headsup] call for assistance with ports broken on -current Message-ID: <a01628140903020303k611258d7q71c6bccea6059ad@mail.gmail.com> In-Reply-To: <KcnYQWp5AIQXX2leTjSSHnkimyo@cgr/Aoyjz11KtFDB23HMnFSn04s> References: <20090302004539.GD17890@lonesome.com> <KcnYQWp5AIQXX2leTjSSHnkimyo@cgr/Aoyjz11KtFDB23HMnFSn04s>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin <rea-fbsd@codelabs.ru> wro= te: > Mark, good day. > > Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote: >> 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. > > Could you or someone else add ports/129881 as the ARPv2 changes > resolution fix for the ospfd? =A0I am not eligible to edit the wiki > pages, so can't do it for myself. Isn't this PR ready for commit already? It seems that the only thing blocking it is maintainer approval, but we're well beyond that now. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a01628140903020303k611258d7q71c6bccea6059ad>