2015-08-10 10:55 GMT+02:00 Mickaël Bucas <mbu...@gmail.com>: > > > 2015-08-10 2:15 GMT+02:00 Dale <rdalek1...@gmail.com>: > > > > Howdy, > > > > I'm sure I'm not alone on monitoring -dev to see upcoming changes. I > > noticed they switched to git or something and it seems to have caused a > > bit of trouble. At least I think it may have. I did my usual 'eix-sync > > && emerge -uvaDN world'. The sync took MUCH longer than usual. I'm > > talking a WHOLE LOT longer than usual. My first thought, one time thing > > because of the changes, maybe. Then I got a screen full of this sort of > > stuff. > > > > > > > > * Missing digest for > > '/var/cache/portage/tree/media-libs/fontconfig/fontconfig-2.11.1-r2.ebuild' > [...] > > I got a similar list about all my installed packages. The reason is that the Manifest files have changed. > Before there was a digest for each ebuild in a category, as can be seen here : > https://github.com/gentoo/gentoo-portage-rsync-mirror/blob/master/kde-base/knotes/Manifest > Now there is only the digests for source files > https://gitweb.gentoo.org/repo/gentoo.git/tree/kde-base/knotes/Manifest > > > > > Can I take that "just saying" above back and say FUBAR instead? :-( > > > > Thoughts?? > > > > Dale > > Either the Manifest generator encountered a problem, or the digest for ebuilds is not necessary in new versions of portage, but the latter is less likely in my opinion as it would lower overall security. > I didn't find a bug about this subject, but I don't really know what and where to search...
So the answer was in Git history, in the first commit : https://gitweb.gentoo.org/repo/gentoo.git/log/kde-base/knotes/Manifest?showmsg=1 "3. Transform all Manifests to thin" https://wiki.gentoo.org/wiki/Repository_format/package/Manifest "A Thin Manifest is a Manifest file in which checksums are stored only for distfiles (*DIST* type) and not for files inside the repository. The motivation for that is whenever the repository is fetched through a VCS which ensures local file integrity already." I think I understand the problem a bit better : the CVS repository contained classic Manifest files, and was exposed directly to rsync. The Git repository contains only thin Manifest, but has been set as the source for rsync at one point ! This has already been reported, and solved. https://bugs.gentoo.org/show_bug.cgi?id=557184 Best regards Mickaël Bucas
