Apparently, along with the recent xorg-7.3 release, x11-proto/xextproto-7.0.2 had its manifest updated and signed. As near as I can tell, the new size for the tarball, xextproto-7.0.2.tar.bz2 , is incorrect. Old and correct (AFAICT) size, 68323 bytes, new size according to Manifest, 68342. Herbert Laubner (laubner at gmx dot net) posted a question about it to the gentoo-amd64 list (thread here: http://thread.gmane.org/gmane.linux.gentoo.amd64/11747 ), thus causing me to sync and see what was going on. Before doing so, I noted the old file size (68323) and that the ebuild and Manifest hadn't been touched since February. After the sync, new Manifest with a different tarball size. It no longer matched my distfiles version, so I deleted that and redownloaded, only to get the same (old) size. Finally, seeing the old bugs filed and that upstream had stealthed a change in 2006 without changing the version, I checked the official one directly off of http://xorg.freedesktop.org/releases/individual/proto/ , and got exactly the same (old) size, 68323. Thus, xorg.freedesktop.org itself is providing the old 68323 sized file. I've no idea where 68342 came from at all, but it doesn't appear to be right, or at least it doesn't agree with what upstream itself is serving. Duncan
*** Bug 191679 has been marked as a duplicate of this bug. ***
This apply to every package in x11-proto/, at least those installed with xorg-x11
confirmed! please fix, this might scare new users away ;)
*** Bug 191718 has been marked as a duplicate of this bug. ***
@vapier - you broke all the x11-proto/* manifests on your arm/s390/sh stable session. Maybe you'd like to fix it?
x11-libs/libXp also is broken, I'll report bak, if I encounter more
*** Bug 191725 has been marked as a duplicate of this bug. ***
x11-apps/bdftopcf is another candidate failing
blame repoman for breaking category level commits
actually, repoman was doing the right [over ambitious] thing here ... X rereleased many tarballs way back without changing names when and i still have the old ones
*** Bug 191745 has been marked as a duplicate of this bug. ***
*** Bug 191751 has been marked as a duplicate of this bug. ***
*** Bug 191753 has been marked as a duplicate of this bug. ***
*** Bug 191766 has been marked as a duplicate of this bug. ***
*** Bug 191768 has been marked as a duplicate of this bug. ***
*** Bug 191774 has been marked as a duplicate of this bug. ***
*** Bug 191783 has been marked as a duplicate of this bug. ***
When it says "RESOLVED FIXED", does that mean it should work now?
I don't know why this is "fixed" - but actually -- it does not work
Yes. Now when I try to emerge one of these packages, say x11-proto/xextproto-7.0.2, I get a digest verification failure on SHA1. (See below). >>> Emerging (1 of 56) x11-proto/xextproto-7.0.2 to / >>> Downloading 'http://distfiles.gentoo.org/distfiles/xextproto-7.0.2.tar.bz2' --00:48:47-- http://distfiles.gentoo.org/distfiles/xextproto-7.0.2.tar.bz2 => `/usr/portage/distfiles/xextproto-7.0.2.tar.bz2' Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 64.50.236.52, ... Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 68,323 (67K) [application/x-tar] 100%[====================================>] 68,323 --.--K/s 00:48:47 (582.64 KB/s) - `/usr/portage/distfiles/xextproto-7.0.2.tar.bz2' saved [68323/68323] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xextproto-7.0.2.tar.bz2 ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/distfiles/xextproto-7.0.2.tar.bz2 !!! Reason: Failed on SHA1 verification !!! Got: 724c82cb9f393ae3cf71a178c328608b17ccccac !!! Expected: 1effb08b6e3e80e48391c68343000bd160851615
*** Bug 191786 has been marked as a duplicate of this bug. ***
evieext-1.0.2.tar.bz2 in x11-proto/evieext-1.0.2 still fails.
(In reply to comment #20) > !!! Digest verification failed: > !!! /usr/portage/distfiles/xextproto-7.0.2.tar.bz2 > !!! Reason: Failed on SHA1 verification > !!! Got: 724c82cb9f393ae3cf71a178c328608b17ccccac > !!! Expected: 1effb08b6e3e80e48391c68343000bd160851615 It takes time to reach the rsync mirrors but it's been fixed in cvs: http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-proto/xextproto/Manifest?r1=1.44&r2=1.45 (In reply to comment #22) > evieext-1.0.2.tar.bz2 in x11-proto/evieext-1.0.2 still fails. I've fixed that just now.
*** Bug 191818 has been marked as a duplicate of this bug. ***
*** Bug 192017 has been marked as a duplicate of this bug. ***
