The last couple of times these two apps have required an update the file sizes have had mis-matchs. It is easy to fix, FOR ME, as I just digest the ebuilds in question and away it goes, however, I have setup a couple of boxes for, shall we say, less technically savvy, friends and this stops the cron job I have set up from completing the upgrade for them. As the build works OK after I have digested the ebuilds, I think it is just someone being slack .. Can the "someone" be asked to double check in future? I only ask as it is the same two packages for the last couple of times, not your usual, trivial type of mistake that happens from time to time, but an ongoing problem with just these two apps.
# emerge -f xextproto Calculating dependencies... done! >>> Emerging (1 of 1) x11-proto/xextproto-7.0.2 to / >>> Downloading 'http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2' --09:15:10-- http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2 => `/usr/portage/distfiles/xextproto-7.0.2.tar.bz2' Resolving xorg.freedesktop.org... 131.252.208.36 Connecting to xorg.freedesktop.org|131.252.208.36|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 68,323 (67K) [application/x-tar] 100%[===================================================================================================>] 68,323 81.35K/s 09:15:11 (81.15 KB/s) - `/usr/portage/distfiles/xextproto-7.0.2.tar.bz2' saved [68323/68323] * xextproto-7.0.2.tar.bz2 MD5 ;-) ... [ ok ] * xextproto-7.0.2.tar.bz2 RMD160 ;-) ... [ ok ] * xextproto-7.0.2.tar.bz2 SHA1 ;-) ... [ ok ] * xextproto-7.0.2.tar.bz2 SHA256 ;-) ... [ ok ] * xextproto-7.0.2.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xextproto-7.0.2.tar.bz2 ;-) ... [ ok ] # emerge -f xcmiscproto Calculating dependencies... done! >>> Emerging (1 of 1) x11-proto/xcmiscproto-1.1.2 to / >>> Downloading 'http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2' --09:15:52-- http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2 => `/usr/portage/distfiles/xcmiscproto-1.1.2.tar.bz2' Resolving xorg.freedesktop.org... 131.252.208.36 Connecting to xorg.freedesktop.org|131.252.208.36|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 36,750 (36K) [application/x-tar] 100%[===================================================================================================>] 36,750 60.22K/s 09:15:53 (60.05 KB/s) - `/usr/portage/distfiles/xcmiscproto-1.1.2.tar.bz2' saved [36750/36750] * xcmiscproto-1.1.2.tar.bz2 MD5 ;-) ... [ ok ] * xcmiscproto-1.1.2.tar.bz2 RMD160 ;-) ... [ ok ] * xcmiscproto-1.1.2.tar.bz2 SHA1 ;-) ... [ ok ] * xcmiscproto-1.1.2.tar.bz2 SHA256 ;-) ... [ ok ] * xcmiscproto-1.1.2.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xcmiscproto-1.1.2.tar.bz2 ;-) ... [ ok ]
I'm not sure why it happened on this or the remote system, hasn't got anything the same, is even different chipset/cpu. Just the same ebuilds failed for the stated reason and was fixed with re-digest all machines. Can re-digesting fix on-board file size reads? ..clutching at straws madly here :-) OH well, live and learn, I'll keep my eye on it any, OK?
You need to delete the old tarballs from /usr/portage/distfiles; we can't do much about upstream silently changing them without version bump. :(
(In reply to comment #3) > You need to delete the old tarballs from /usr/portage/distfiles; we can't do > much about upstream silently changing them without version bump. :( > Thanks Jakub, have done so and is fixed :-)
