Summary: | sys-apps/portage-2.1.8.3: repoman does not notice wrong digest of metadata.xml or ChangeLog | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925 | ||
Attachments: | Output of emerge --info |
Description
Andreas K. Hüttel
![]() ![]() Created attachment 233305 [details]
Output of emerge --info
There's a new repoman manifest-check mode that's not in a released version of portage yet. We can make that code trigger for all modes, so that manifest issues will always be detected. Seems like this also affects ChangeLog... huettel@pinacolada ~/Gentoo/sci/sci-electronics/klayout $ ebuild klayout-0.20.2.ebuild install Appending /home/huettel/Gentoo/sci to PORTDIR_OVERLAY... * klayout-0.20.2.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ !! ] !!! Digest verification failed: !!! /home/huettel/Gentoo/sci/sci-electronics/klayout/ChangeLog !!! Reason: Filesize does not match recorded size !!! Got: 509 !!! Expected: 233 huettel@pinacolada ~/Gentoo/sci/sci-electronics/klayout $ repoman RepoMan scours the neighborhood... ebuild.allmasked 1 sci-electronics/klayout Note: use --include-dev (-d) to check dependencies for 'dev' profiles RepoMan sez: "You're only giving me a partial QA payment? I'll take it this time, but I'm not happy." huettel@pinacolada ~/Gentoo/sci/sci-electronics/klayout $ This is fixed in git now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=6938064ec0b64c2896cb849a385910cc558c4032 This is in 2.2_rc68, but I'll leave this bug open until it's in an unmasked version. This is fixed in 2.1.9. |