Re: Portsnap support on CURRENT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Feb 10, 2006 at 04:43:33PM -0500, 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.

So, is /usr/sbin/portsnap currently supported on CURRENT? It appears to
keep /usr/ports up to date, just not the index file. For now, I've
switched to using sysutils/portmanager from ports for upgrading ports,
but I'm not entirely happy with that for a variety of reasons. Plus,
some /usr/ports/UPDATING instructions advocate using portupgrade
explicitly, so it would be nice to have portupgrade working fully. :-)


I had the same problem (on CURRENT, with 6.x working perfectly.) Like
you I tracked it down to the INDEX file not being updated.

My temporary hack is to simply rn pkgdb -Fu (hrm, who thought of those
flags?) :) before running portversion.


- --

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Drusilla: Your face is a poem. I can read it.
Xander: It doesn't say 'spare me' by any chance?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFD7RNV+lTVdes0Z9YRAut+AJ9DHw6gITkhvEFcaMIuQwBUmSiYzACghlWG
ya2mwldzlGpP0Eq2XUxQXVU=
=9/Uh
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Updating Ports on Production Servers
    ... won't quite work if the flags you want to ... # opportunity to override settings in port Makefiles. ... >> The bad part about using portupgrade is that you can't specify any ...
    (freebsd-isp)
  • Re: portupdate xorg-server
    ... Any port upgrading tool belongs in a port, ... Never did I claim portupgrade fails where a normal make install would succeed. ...
    (freebsd-questions)
  • Re: Portsnap support on CURRENT
    ... These messages are incorrect ... the "port has" version identified by portversion is older than ... setenv INDEXFILE INDEX-6 ...
    (freebsd-current)
  • Re: A portupgrade question
    ... I've run portupgrade -a to upgrade a bunch of ports, ... portupgrade has tried to install mysql-client, ... to install it again (or if it needs upgrading, ... handled through the ldconfig_compat port which installs precisely one file: ...
    (freebsd-questions)
  • Re: portupdate xorg-server
    ... If portupgrade is failing on a port ... Any port upgrading tool belongs in a port, ... normal make install would succeed. ... so why waste time in debugging them. ...
    (freebsd-questions)