Date: 19 Oct 2005 09:19:11 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Rem P Roberti <remegius@comcast.net> Cc: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Portversion question Message-ID: <44sluxy78w.fsf@be-well.ilk.org> In-Reply-To: <4355610E.3050903@comcast.net> References: <435558E2.1040900@comcast.net> <44sluyr20j.fsf@be-well.ilk.org> <4355610E.3050903@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rem P Roberti <remegius@comcast.net> writes: > Lowell Gilbert wrote: > > >Rem P Roberti <remegius@comcast.net> writes: > > > > > >>I have crontab run cvsup, and make a new port index for me nightly. > >>This morning I ran portversion -l and found that there was a package > >>it regarded as not being up to date. However, neither portmanager or > >>portupgrade picked up the non-current package. Why would portversion > >>indicate a package that is not up to date, and either of the two > >>upgrade programs not find it also? > >> > > > >A bug? > >A port that was moved? [see /usr/ports/MOVED] > > > >There are probably other possible reasons, but you didn't give us much > >to go on... > > > > > The port in question is libmng, which is in the graphics directory. > The current version is 1.0.8, and that is exactly what pkg_info shows > as being installed. Portversion continues to show it as out of date. > I have no doubt that my newbieness is missing something here, and I'd > love to find out what it is :) Pretty puzzling, actually, but seeing the exact output would help a lot. On the other hand, the libmng port is now up to 1.0.9... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44sluxy78w.fsf>