Re: Portsnap support on CURRENT
- From: Freddie Cash <fcash@xxxxxxxx>
- Date: Fri, 10 Feb 2006 14:40:49 -0800
On Friday 10 February 2006 01:43 pm, Paul Mather wrote:
I've noticed lately a lot of "succeeds port" messages when I run
portversion (from the portupgrade port) to list which of my packages
are out of date and require updating. These messages are incorrect
(i.e., the "port has" version identified by portversion is older than
that in the actual port Makefile), and I don't get incorrect
identifications from either pkg_version or portmanager. (I also don't
get this problem on a RELENG_6 system I have, either.)
After a little looking, I discovered that my /usr/ports/INDEX-7 file is
not being updated. Investigation of the portsnap source reveals that
it only actually generates INDEX, INDEX-5, and INDEX-6 from portsnap
updates in extract_indices(); it doesn't generate INDEX-7.
Workarounds until portsnap does it again, in order of length of time to
generate INDEX-7:
cd /usr/ports ; make fetchindex
cd usr/ports ; make index
pkgdb -U
--
Freddie Cash
fcash@xxxxxxxx
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Portsnap support on CURRENT
- From: Martin Wilke
- Re: Portsnap support on CURRENT
- From: Kris Kennaway
- Re: Portsnap support on CURRENT
- References:
- Portsnap support on CURRENT
- From: Paul Mather
- Portsnap support on CURRENT
- Prev by Date: Re: Portsnap support on CURRENT
- Next by Date: Re: HEADSUP: New pts code triggers panics on amd64 systems.
- Previous by thread: Re: Portsnap support on CURRENT
- Next by thread: Re: Portsnap support on CURRENT
- Index(es):
Relevant Pages
|