Date: Thu, 8 May 2008 17:07:47 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: neon port won't upgrade Message-ID: <20080508220747.GB2922@dan.emsphone.com> In-Reply-To: <20080508210247.GB70286@demeter.hydra> References: <20080508202543.GA70286@demeter.hydra> <482367FF.3000100@adventuras.no> <20080508210247.GB70286@demeter.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 08), Chad Perrin said: > On Thu, May 08, 2008 at 10:52:15PM +0200, Lars Kristiansen wrote: > > Chad Perrin skrev: > > >Let me know if I should take this to the ports mailing list instead of > > >the questions mailing list. > > > > > >This is my problem: > > > > > > # portupgrade neon-0.26.4 > > > ** Port directory not found: www/neon2 > > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > > > - www/neon2 (port directory error) > > > > > >Does anyone have any troubleshooting tips for how I should deal > > >with this? This is the first time I've had a port fail to upgrade > > >because it suddenly seems to have ceased existing. > > > > portupgrade -f -o www/neon26 neon > > > > seemed to work for me > > Isn't this the sort of information that should be in > /usr/ports/UPDATING? In my case, there's nothing in that file that > comes up when I search for the string "neon" (without quotes). Do you update your entire ports tree, or just certain subdirs? My copy of /usr/ports/MOVED ( rev 1.1591 ) has the following: www/neon|www/neon26|2008-05-05|Moved to be able to integrate www/neon26 which portupgrade should have used to determine the new location of the port. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080508220747.GB2922>