| Summary: | gnome-cups-manager Digests do not match | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stanley Stefanov <sis.stefanov> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | printing |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Stanley Stefanov
2004-10-04 12:24:45 UTC
try deleting the file and fetching again. both the gentoo-mirrors and gnome mirrors ge tthe correct checksum for me. Sorry, didn't work for me. When I do md5sum /usr/portage/net-print/gnome-cups-manager/gnome-cups-manager-0.17.ebuild the result is: f83119ff84b4b8b8f0cc689992285714 (just like in the error mesage) Here is the record in my /usr/portage/net-print/gnome-cups-manager/Manifest MD5 50cfefa3f7053b7d5dd109e582734977 ChangeLog 3244 MD5 b9df51065584c842989a4c1f779ae328 gnome-cups-manager-0.17.ebuild 813 MD5 d69d1ebf1cde9b2670b189f2128a7832 gnome-cups-manager-0.18.ebuild 772 MD5 574309004015c52c39e2f4e8122c18a3 metadata.xml 180 MD5 f63c25f8a2c38d39f08f1a0fa1b40010 gnome-cups-manager-0.23.ebuild 679 MD5 6dae95b443777de3b98de444d36134ec files/digest-gnome-cups-manager-0.17 76 MD5 f48ff0335a5163f1094f5cafb0ad3c78 files/digest-gnome-cups-manager-0.18 76 MD5 38ef34fd59e1c024d719000653111039 files/gnome-cups-manager-0.17-fix_gtk24_deprecation.patch 3301 MD5 1772dd481b0fa6e38d67b284f73df4bf files/gnome-cups-manager-0.18-paren.patch 486 MD5 badc909dc73f068eb167ec0a7e24c096 files/digest-gnome-cups-manager-0.23 76 As you can see the records in the Manifest file for gnome-cups-manager-0.17.ebuild doesn't mach the md5 for my gnome-cups-manager-0.17.ebuild. The same for gnome-cups-manager-0.23.ebuild my md5sum is: 2be4d0c7720ee398858d9323dec5e32f which also differs from the record in the Manifest However gnome-cups-manager-0.18.ebuild has the right checksum I gues if I change the records in the Manifest file to mach my real checksum for 0.17.ebuild and 0.23.ebuld, will do the job, but it stll leaves the problem open. My concern is what are the legitimate values in the Manifest file. what mirror do those files come from ? Last 2 Servers that I used to rsync: 128.193.0.161 134.68.220.74 I beleive the records in the /usr/portage/net-print/gnome-cups-manager/Manifest should be fixed. the manifest hadn't been regenerated after lanius applied the gcc-3.4 patches. it seems repoman wasn'even run on (cvs log Manifest has nothing after 24 august). regenerated the manifest. my apologies for not reading your report closely the first time around. i thought the error was pointing to the tarball being out of date, but it was the manifest. that has been regenreated now . |