Date: Thu, 8 May 2008 16:45:06 -0600 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: neon port won't upgrade Message-ID: <20080508224505.GA70669@demeter.hydra> In-Reply-To: <20080508230012.2056d4db@gumby.homeunix.com.> References: <20080508202543.GA70286@demeter.hydra> <482367FF.3000100@adventuras.no> <20080508210247.GB70286@demeter.hydra> <20080508230012.2056d4db@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, May 08, 2008 at 11:00:12PM +0100, RW wrote: > On Thu, 8 May 2008 15:02:47 -0600 > Chad Perrin <perrin@apotheon.com> wrote: > > > On Thu, May 08, 2008 at 10:52:15PM +0200, Lars Kristiansen wrote: > > > > > > > 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). > > Actually, isn't portupgrade supposed to handle moved origins > automatically? There's an --ignore-moved option, and in the > script there's some code for finding the new origin at the top of the > function do_upgrade(). Good point. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Phillip J. Haack: "Productivity is not about speed. It's about velocity. You can be fast, but if you're going in the wrong direction, you're not helping anyone." [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkgjgnEACgkQ9mn/Pj01uKUIRwCfW9znmZ7BXFIcZwBJvuHxIJ9m x5EAn2p8KZHaBFAeH9aPiDC1qFWd2tBl =d87e -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080508224505.GA70669>