Dan Nelson skrev:
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.

If I understand this correctly from:

The MOVED file was updated perhaps wrongly at first and then corrected.
So we who ran pkgdb -fF in the half a day before the correction would be thrown off in this case.

Would an additional line had solved it, like:
www/neon2|www/neon26|2008-05-05|Moved straight to www/neon26

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to