Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Mar 2009 12:34:21 +0300
From:      Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To:        freebsd-ports@FreeBSD.org
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: [headsup] call for assistance with ports broken on -current
Message-ID:  <KcnYQWp5AIQXX2leTjSSHnkimyo@cgr/Aoyjz11KtFDB23HMnFSn04s>
In-Reply-To: <20090302004539.GD17890@lonesome.com>
References:  <20090302004539.GD17890@lonesome.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.  I 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?  I am not eligible to edit the wiki
pages, so can't do it for myself.
-- 
Eygene
 _                ___       _.--.   #
 \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
 /  ' `         ,       __.--'      #  to read the on-line manual
 )/' _/     \   `-_,   /            #  while single-stepping the kernel.
 `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
     _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
    {_.-``-'         {_/            #



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KcnYQWp5AIQXX2leTjSSHnkimyo>