Date: Mon, 23 Jun 2008 05:13:30 -0300 From: Gonzalo Nemmi <gnemmi@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Patch Failures during Portupgrade Message-ID: <200806230513.31024.gnemmi@gmail.com> In-Reply-To: <991123400806230103v45e26ab9u6694a3032a7d5ae@mail.gmail.com> References: <200806231533.06068.shinjii@maydias.com> <991123400806230103v45e26ab9u6694a3032a7d5ae@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 23 June 2008 05:03:34 Odhiambo Washington wrote: > On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell <shinjii@maydias.com> wrote: > > Below is the hunk of ports that continually fail to upgrade due to > > problems with patching. i use the command portupgrade -aDkp -m BATCH=yes > > > > Any assistance with this greatly appreciated. > > Do you have the latest ports tree (via cvsup or csup)? or portsnap fetch extract portsnap update portupgrade -arR and since gettext got updated .. is gonna take a loooooot of time to update all of your ports ... Actually .. from /usr/ports/UPDATING: 20080605: AFFECTS: users of devel/gettext (ie: YOU) AUTHOR: ade@FreeBSD.org As a result of the upgrade to gettext-0.17, the shared library version of libintl has changed, so you will need to rebuild all ports that depend on gettext: # portupgrade -rf gettext # portmaster -r gettext\* Given the scope and sheer number of dependent ports, it may be more advisable to simply blow away all existing install ports (after keeping any local configuration changes), and rebuilding from scratch. Patience is a virtua ... I guess :s -- Blessings Gonzalo Nemmi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806230513.31024.gnemmi>