Date: Sun, 28 Aug 2005 23:09:08 +0200 From: Karol Kwiatkowski <freebsd@orchid.homeunix.org> To: Trey Sizemore <trey@fastmail.fm> Cc: freebsd-questions@freebsd.org Subject: Re: Can't upgrade a number of packages Message-ID: <431227F4.7050906@orchid.homeunix.org> In-Reply-To: <20050828123212.4c35cb77@localhost> References: <20050828123212.4c35cb77@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Trey Sizemore wrote: > I'm getting the following when trying to upgrade packages with known > upgrades: > > salamander# portversion -v -l '<' [...] > evolution-2.2.3 < needs updating (port has 2.2.3_1) [...] > salamander# portupgrade -v evolution > ---> Session started at: Sun, 28 Aug 2005 12:29:03 -0400 > ** No need to upgrade 'evolution-2.2.3' (>= evolution-2.2.3). (specify > -f to force) > ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > - mail/evolution (evolution-2.2.3) > ---> Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed > ---> Session ended at: Sun, 28 Aug 2005 12:29:05 -0400 (consumed 00:00:02) [...] > Any ideas on what might be causing this and how to fix? It happened to me a few times. It's because information about the ports tree in INDEX file is newer than the ports tree itself (or at least that's how I see it). Just cvsup your ports tree and get new INDEX file (make fetchindex && portsdb -u). Regards, Karol -- Karol Kwiatkowski <freebsd at orchid dot homeunix dot org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431227F4.7050906>