Summary: | rsync mirror distributing invalid Manifest for gtk-sharp-2.12.8.tar.bz2 in packages dev-dotnet/{pango,gdk}-sharp | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Piechotka <uzytkownik2> |
Component: | New packages | Assignee: | Mirror Admins <mirror-admin> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | dotnet |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maciej Piechotka
2009-02-09 01:40:59 UTC
grep -r --include="Manifest" gtk-sharp-2.12.8.tar.bz2 /usr/portage/dev-dotnet/ Shows me that the digests are identical in all packages using that tarball. And they all emerge fine, having fetched it from local mirrors. md5sum /usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2 1b12a33df2ab87448848c0cc0733ca77 /usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2 That's the same as the md5 of the upstream tarball: http://ftp.acc.umu.se/pub/gnome/sources/gtk-sharp/2.12/gtk-sharp-2.12.8.md5sum I'll push this tarball straight onto the main mirror and force a re-sync. Can you tell us where you got your tarball from and what its md5sum and size in bytes is? # grep -r --include="Manifest" gtk-sharp-2.12.8.tar.bz2 /usr/portage/dev-dotnet/ /usr/portage/dev-dotnet/gtk-dotnet-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/pango-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/glib-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/gtk-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/gtk-sharp-docs/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/gtk-sharp-gapi/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/gdk-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/glade-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 /usr/portage/dev-dotnet/atk-sharp/Manifest:DIST gtk-sharp-2.12.8.tar.bz2 1605876 RMD160 d287020b230e637869f4fe830961724bd44f7b01 SHA1 3c97abd67e92738e7960f9e0e5f2410e8ff4912b SHA256 b2edc4bb213c1a0fc40dede222116686f04c4ba9196f80c5d1532d5ee2128020 # md5sum /var/tmp/distfiles/gtk-sharp-2.12.8.tar.bz2 1b12a33df2ab87448848c0cc0733ca77 /var/tmp/distfiles/gtk-sharp-2.12.8.tar.bz2 This means that the data on portage mirror were incorrect. (In reply to comment #2) These look like the same results I have. You should not be getting digest errors with that file. (In reply to comment #3) > (In reply to comment #2) > > These look like the same results I have. You should not be getting digest > errors with that file. > I confirm that it now compiles normally. 1. It was some bug in portage 2. Removing Manifest from dev-dotnet/gtk-sharp-gapi and making digest (I've done this to check the case) removed the false digest from the rest That makes no sense whatsoever. Leaving this open to see if anyone else is affected. (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > > These look like the same results I have. You should not be getting digest > > errors with that file. > > > > I confirm that it now compiles normally. > 1. It was some bug in portage > 2. Removing Manifest from dev-dotnet/gtk-sharp-gapi and making digest (I've > done this to check the case) removed the false digest from the rest > I got the same error here. regenerating the digest after removal if it works for me. Somebody post the actual text of this error, please? (In reply to comment #7) > Somebody post the actual text of this error, please? > First, the wrong line in Manifest, DIST gtk-sharp-2.12.8.tar.bz2 207360 RMD160 1eeed0a4c463e7bc417661b89e4f84dc9619d84a SHA1 33647c0e64a285933fb75f578fd6e43ddad4c3e5 SHA256 97b24b283802683214a327146da60689e668e49c4091a87053b6146c36756af6 2009-02-09 05:12:23 (90.4 KB/s) - `/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2' saved [1605876/1605876] ('Filesize does not match recorded size', 1605876L, 207360) !!! Fetched file: gtk-sharp-2.12.8.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 1605876 !!! Expected: 207360 Refetching... File renamed to '/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2._checksum_failure_.Iib6o4' (In reply to comment #8) > (In reply to comment #7) > > Somebody post the actual text of this error, please? > > > > First, the wrong line in Manifest, > > DIST gtk-sharp-2.12.8.tar.bz2 207360 RMD160 > 1eeed0a4c463e7bc417661b89e4f84dc9619d84a SHA1 > 33647c0e64a285933fb75f578fd6e43ddad4c3e5 SHA256 > 97b24b283802683214a327146da60689e668e49c4091a87053b6146c36756af6 > > 2009-02-09 05:12:23 (90.4 KB/s) - > `/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2' saved [1605876/1605876] > > ('Filesize does not match recorded size', 1605876L, 207360) > !!! Fetched file: gtk-sharp-2.12.8.tar.bz2 VERIFY FAILED! > !!! Reason: Filesize does not match recorded size > !!! Got: 1605876 > !!! Expected: 207360 > Refetching... File renamed to > '/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2._checksum_failure_.Iib6o4' > This is from which package? (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > Somebody post the actual text of this error, please? > > > > > > > First, the wrong line in Manifest, > > > > DIST gtk-sharp-2.12.8.tar.bz2 207360 RMD160 > > 1eeed0a4c463e7bc417661b89e4f84dc9619d84a SHA1 > > 33647c0e64a285933fb75f578fd6e43ddad4c3e5 SHA256 > > 97b24b283802683214a327146da60689e668e49c4091a87053b6146c36756af6 > > > > 2009-02-09 05:12:23 (90.4 KB/s) - > > `/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2' saved [1605876/1605876] > > > > ('Filesize does not match recorded size', 1605876L, 207360) > > !!! Fetched file: gtk-sharp-2.12.8.tar.bz2 VERIFY FAILED! > > !!! Reason: Filesize does not match recorded size > > !!! Got: 1605876 > > !!! Expected: 207360 > > Refetching... File renamed to > > '/usr/portage/distfiles/gtk-sharp-2.12.8.tar.bz2._checksum_failure_.Iib6o4' > > > > This is from which package? > I got this from both pango-sharp and gdk-sharp emerge --sync was right before this Anyone experiencing this bug, please note which rsync server you're syncing against. It looks like someone has regenerated the manifests downstream from the CVS server. (In reply to comment #11) > Anyone experiencing this bug, please note which rsync server you're syncing > against. > It looks like someone has regenerated the manifests downstream from the CVS > server. > confirmed, redoing emerge --sync solved all manifest issues here not sure about the bad server, but my mirror list, GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://mirror.datapipe.net/gentoo ftp://gentoo.mirrors.tds.net/gentoo http://64.50.236.52/ http://gentoo.mirrors.tds.net/gentoo" grep -A1 "Starting rsync" /var/log/emerge.log |less should give you a list of all syncs that have been logged. (In reply to comment #13) > grep -A1 "Starting rsync" /var/log/emerge.log |less > should give you a list of all syncs that have been logged. > The last entry: 1234149018: >>> Starting rsync with rsync://140.211.166.165/gentoo-portage 1234149307: === Sync completed with rsync://140.211.166.165/gentoo-portage (In reply to comment #14) > The last entry: > 1234149018: >>> Starting rsync with rsync://140.211.166.165/gentoo-portage > 1234149307: === Sync completed with rsync://140.211.166.165/gentoo-portage That mirror is back to normal rsync -av rsync://140.211.166.165/gentoo-portage/dev-dotnet/pango-sharp/Manifest . You are using a developer profile. This enables FEATURES=digest. Please don't use a developer unless you actually are a developer and know the problems it causes. In this case, the digests are regenerated with a corrupted tarball which leads to all other packages in the depgraph having the incorrect Manifest when they're checked, causing the error described in this bug. This was probably just a tarball that hadn't been completely mirrored yet when another mirror fetched it. That would have cleared up in no time, instead I've spent precious time tracking down wtf could cause this. In the future, please be aware of this. We really are serious when we say that if you don't know EXACTLY what you're doing, you shouldn't enable developer profile. At all. Ever. |