Date: Mon, 23 Apr 2012 15:04:46 -0400 From: Michael Powell <nightrecon@hotmail.com> To: freebsd-questions@freebsd.org Subject: Re: upgrade of portupgrade Message-ID: <jn4941$ng$1@dough.gmane.org> References: <CAEFCw4vcGmGj6P7xhT-qQyu8Ohe4%2BKTER58B9=RHbovjvdGCUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
n dhert wrote: > Today, my nightly run of portsnap informed me there is un update for: > # pkg_version -vIL= > portupgrade-2.4.9.3.2 < needs updating (index has 2.4.9.3_1,2) > > Since there is no special entry in /usr/ports/UPDATING about the > portupgrade update, > I started my weekly > # portupgrade -yaRrpb > > this gives: > ... > ---> Upgrade of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 > 08:37:14 +0 > 200 > ---> Upgrading 'portupgrade-2.4.9.3,2' to 'portupgrade-2.4.9.3_1,2' > (ports-mgmt > /portupgrade) > ---> Build of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 > 08:37:14 +020 > 0 > ---> Building '/usr/ports/ports-mgmt/portupgrade' > ===> Cleaning for portupgrade-2.4.9.3_1,2^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > ===> Extracting for portupgrade-2.4.9.3_1,2^M > => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M > ===> Refetch for 1 more times files: pkgtools-2.4.9.3.tar.bz2 ^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > => pkgtools-2.4.9.3.tar.bz2 doesn't seem to exist in > /usr/ports/distfiles/.^M > => Attempting to fetch > http://heanet.dl.sourceforge.net/project/portupgrade/pkgt > ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M > fetch: > http://heanet.dl.sourceforge.net/project/portupgrade/pkgtools/2.4.9.3/pkg > tools-2.4.9.3.tar.bz2: Moved Temporarily^M > it does 5 more at other places, then > => Attempting to fetch > http://freefr.dl.sourceforge.net/project/portupgrade/pkgt > ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M > fetch: pkgtools-2.4.9.3.tar.bz2: local file (79394 bytes) is longer than > remote > file (79377 bytes)^M > ... > then 10 more 'Attempting to fetch' with Moved temporarily > then > => Attempting to fetch > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgtool > s-2.4.9.3.tar.bz2^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M > ===> Giving up on fetching files: pkgtools-2.4.9.3.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 > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > *** Error code 1^M > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > *** Error code 1^M > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > ---> Build of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 > +0200 > (consumed 00:00:30) > ---> Upgrade of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 > 08:37:45 +020 > 0 (consumed 00:00:30) > > What's this problem with pkgtools ??? > I have a > $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 > -rw-r--r-- 1 root wheel 79394 Aug 23 2011 > /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 > but no 2.4.9.3_1,2 version > > And, strange: if I try > http://www.freebsd.org/ports, Search for pkgtools in All > it finds nothing ??? Isn't that package described ?? Search for portupgrade instead. > What's going on here and how to solve it ?? I just did this upgrade utilizing portupgrade 2 days ago - 04/20/12 03:34 and did not experience any trouble. However, I noticed the name of the file that was downloaded here was: pkgtools-pkgtools-b99f3ce.tar.gz. This file was 98949 bytes in size. Today I have csup'd my ports tree and did a make fetch for this port and it downloaded a file of the same name as you have described. This file is 79377 bytes in size. I did a make for the port and it again built without error. Sounds like something was out of sync at the time you tried this. Try refreshing your ports again and see if it has been fixed. Also consider the possibility that the mirror you were using wasn't completely up to date. Either the mirror will have caught up since then, or try another mirror. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jn4941$ng$1>