| Summary: | sys-libs/db-4.4.20_p4-r1: file size mismatch while fetching | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andrey Korobkov <bugs_gentoo_org.korobkov> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | caleb, cassio |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.mydatabasesupport.com/forums/bsd-freebsd-misc/355745-file-size-mismatch-fetching-database-4-4-20-a.html#post1201986 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge failre log
emerge --info /usr/portage/sys-libs/db/Manifest /usr/portage/sys-libs/db/db-4.4.20_p4-r1.ebuild git diff oracle other diff between old and new ebuilds |
||
|
Description
Andrey Korobkov
2009-03-16 17:06:26 UTC
Hello try resync portage. that probably solve the problem. turnaround is ebuild sys-libs/db-4.4.20_p4-r1.ebuild digest I couldn't reproduce your problem. If it still isn't fixed for you please tell us from which mirrors you downloaded the mismatching files and reopen this bug. It seems to be OK while you have GENTOO_MIRRORS in /etc/make.conf (so that file is downloaded from that mirrors). But when I use paludis (where I forgot to specify any mirror in /etc/paludis/mirrors.conf) it tries to fetch the tarball from the mainstream download site, specified in the ebuild (SRC_URI="http://download.oracle.com/berkeley-db/${MY_P}.tar.gz"). And from THIS mirror the size and cheksums are different! I suppose, portage without mirrors specified, will do the same... Is there any difference between oracle's and other versions of sys-libs/db? Or it's just the different compression level of the tarball? Reproducible: Always Steps to reproduce: 1. set GENTOO_MIRRORS="" in /etc/make.conf 2. rm /usr/portage/distfiles/db-4.4.20.tar.gz 3. emerge -v =sys-libs/db-4.4.20_p4-r1 Expected behavior: fetching the bigger tarball (8112163) from any mirror, checking checksums and normal installing Real behavior: fetching the smaller tarball (7952742) from the oracle's mirror, checking checksums and failing with this message: ('Filesize does not match recorded size', 7952742L, 8112163) !!! Fetched file: db-4.4.20.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 7952742 !!! Expected: 8112163 Refetching... File renamed to '/usr/portage/distfiles/db-4.4.20.tar.gz._checksum_failure_.ZIEGV2' !!! Couldn't download 'db-4.4.20.tar.gz'. Aborting. * Fetch failed for 'sys-libs/db-4.4.20_p4-r1', Log file: * '/var/tmp/portage/sys-libs/db-4.4.20_p4-r1/temp/build.log' >>> Failed to emerge sys-libs/db-4.4.20_p4-r1, Log file: >>> '/var/tmp/portage/sys-libs/db-4.4.20_p4-r1/temp/build.log' * Messages for package sys-libs/db-4.4.20_p4-r1: * Fetch failed for 'sys-libs/db-4.4.20_p4-r1', Log file: * '/var/tmp/portage/sys-libs/db-4.4.20_p4-r1/temp/build.log' Created attachment 185516 [details]
emerge failre log
Created attachment 185517 [details]
emerge --info
Created attachment 185519 [details]
/usr/portage/sys-libs/db/Manifest
Created attachment 185521 [details]
/usr/portage/sys-libs/db/db-4.4.20_p4-r1.ebuild
Created attachment 185524 [details]
git diff oracle other
The tarballs are really different!
Created attachment 185525 [details]
diff between old and new ebuilds
The new ebuild (v 1.3) doesn't change the SOURCE_URI, so the bug is still actual.
|
