Bug 565910

Summary:	sys-apps/portage-2.2.20.1: emerge shouldn't die due to a bogus Manifest affecting other ebuild version
Product:	Portage Development	Reporter:	Pacho Ramos <pacho>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Pacho Ramos gentoo-dev

2015-11-16 09:31:24 UTC

As a consequence of bug 565694  people are getting this failure:
>>> Verifying ebuild manifests

!!! Digest verification failed:
!!! /usr/portage/sys-apps/busybox/busybox-9999.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 8493
!!! Expected: 8580
>>> Emerging (1 of 3) media-libs/libpng-1.6.19::gentoo
>>> Emerging (2 of 3) sys-apps/busybox-1.23.1-r1::gentoo
>>> Jobs: 0 of 3 complete, 2 running                Load avg: 1.19, 1.56, 1.37
!!! Digest verification failed:
!!! /usr/portage/sys-apps/busybox/busybox-9999.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 8493
!!! Expected: 8580
>>> Failed to emerge sys-apps/busybox-1.23.1-r1
>>> Installing (1 of 3) media-libs/libpng-1.6.19::gentoo
>>> Jobs: 1 of 3 complete, 1 failed                 Load avg: 2.26, 1.81, 1.47
*** Resuming merge...

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] media-libs/libpng-1.2.54:1.2::gentoo [1.2.52:1.2::gentoo] ABI_X86="(64) -32 (-x32)" 0 KiB

Total: 1 package (1 upgrade), Size of downloads: 0 KiB
>>> Emerging (1 of 1) media-libs/libpng-1.2.54::gentoo
>>> Installing (1 of 1) media-libs/libpng-1.2.54::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 2.27, 1.87, 1.50
 * 
 * The following package has failed to build, install, or execute postinst:
 * 
 *  (sys-apps/busybox-1.23.1-r1:0/0::gentoo, ebuild scheduled for merge)
 * 

 * GNU info directory index is up-to-date.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

As you can see, the Manifest is bogus for busybox-9999.ebuild, but that ebuild won't be used at all and is not the ebuild that will be merged. Wouldn't it be possible to only warn but not die in cases like this? I mean the cases of the ebuild being effectively used having no problem at all with the Manifest

Thanks

Comment 1 Pacho Ramos gentoo-dev

2015-11-16 09:38:24 UTC

Ah, it looks to be caused by "strict" being set as default in FEATURES :/

Comment 2 Zac Medico gentoo-dev

2015-11-16 17:48:59 UTC

(In reply to Pacho Ramos from comment #1)
> Ah, it looks to be caused by "strict" being set as default in FEATURES :/

If you disable "strict" then it won't check digests for any of the files in the repository (it will still check distfiles though). So, there's currently no option to just skip digest checks for other ebuilds in the same directory.