Re: Portsnap support on CURRENT

On Fri, Feb 10, 2006 at 02:40:49PM -0800, Freddie Cash wrote:
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

Should usually be good enough:

setenv INDEXFILE INDEX-6

Kris

Attachment: pgpz4il0OEFdy.pgp
Description: PGP signature

Relevant Pages

  • Re: Portsnap support on CURRENT
    ... portversion (from the portupgrade port) to list which of my packages are ... These messages are incorrect (i.e., ...
    (freebsd-current)
  • Re: portversion vs pkg_version
    ... > base install. ... portversion uses the INDEX file to look up port versions. ... INDEX file with portsdb -uU, but this can take a long time depending ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Portupgrade Broke?
    ... Just ran the portversion command for the ... >>first time since last Saturday and the ouptut indicated that my ... Yesterday, I brought all of my packages up-to-date, ran pkgdb -F, ... succeeds port ". ...
    (freebsd-questions)
  • Re: Portsnap support on CURRENT
    ... portversion to list which of my packages ... Investigation of the portsnap source ... to generate INDEX-7: ...
    (freebsd-current)
  • Re: Possible bug in .Net 2.0 udp sockets?
    ... which one is actually incorrect? ... the data in the datagram corrupted, resulting in the wrong ID in the ... Or is EndReceiveFrom returning the wrong port? ... The incoming data was correct -- the port numbers were wrong. ...
    (microsoft.public.dotnet.framework)