upgrade of portupgrade
FreeBSD at ShaneWare.Biz
Mon Apr 23 09:24:32 UTC 2012
On 23/04/2012 17:13, n dhert wrote:
> Today, my nightly run of portsnap informed me there is un update
> for: # pkg_version -vIL= portupgrade-184.108.40.206.2< needs updating
> (index has 220.127.116.11_1,2)
> => SHA256 Checksum mismatch for pkgtools-18.104.22.168.tar.bz2.^M ===>
> Giving up on fetching files: pkgtools-22.214.171.124.tar.bz2 ^M Make sure
> the Makefile and distinfo file
> (/usr/ports/ports-mgmt/portupgrade/dist info)^M are up to date. If
> you are absolutely sure you want to override this^M check, type "make
> NO_CHECKSUM=yes [other args]".^M *** Error code 1^M
> What's this problem with pkgtools ??? I have a $ ls -la
> /usr/ports/distfiles/pkgtools-126.96.36.199.tar.bz2 -rw-r--r-- 1 root
> wheel 79394 Aug 23 2011
> /usr/ports/distfiles/pkgtools-188.8.131.52.tar.bz2 but no 184.108.40.206_1,2
> And, strange: if I try http://www.freebsd.org/ports, Search for
> pkgtools in All it finds nothing ??? Isn't that package described
> What's going on here and how to solve it ??
The issue would appear to be the recent update was messed up. You are
getting an error as the distfile you have has a different md5sum than
what was saved to the port files.
pkgtools is the name of the project, even though the sourceforge project
name and the port name is portupgrade. On github it is pkgtools.
I would guess the port name was chosen to prevent conflicts with pkg_*
named tools in the base system.
I would wait for the maintainer to sort things out. Currently you can
download a tar.gz from github or a tar.bz from sourceforge both
identified as 220.127.116.11 but there is some file differences between them.
As this is a new maintainer just taken over the port about a week ago
you may want to email them or submit a pr.
More information about the freebsd-questions