Please remove entry for non-existing object-file from Manifest. Reproducible: Always Steps to Reproduce: 1. emerge gcc-config Actual Results: >>> Verifying ebuild Manifests... !!! A file listed in the Manifest could not be found: /usr/portage/sys-devel/gcc-config/files/wrapper-1.5.0.o Easy workaround: manually remove entry from Manifest
Just recreated the Manifest, should be gone once the mirrors resync.
repoman shouldnt have allowed this in the first place
I suppose we can add a "file.notadded" category for things like this.
i cant think of a reason why repoman should allow a commit when any files exist locally that are not committed
(In reply to SpanKY from comment #4) > i cant think of a reason why repoman should allow a commit when any files > exist locally that are not committed Commit before was done without Portage afaik, not sure if relevant: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/gcc-config/Manifest?revision=1.286&view=markup Commit itself was done with Portage 2.2_pre2, perhaps it was a buggy release: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/gcc-config/Manifest?revision=1.287&view=markup Trying to reproduce with file present: !!! The following files are in your local tree but are not added to the master !!! tree. Please remove them from the local tree or add them to the master tree. Not reproducible, I can't commit it that way as it is blocked. Trying to reproduce with file not present: >>> Creating Manifest for /home/tomwij/gentoo-x86/dev-util/test Not reproducible, the Manifest no longer contains the file. The only way I have on mind to actually reproduce this is to remove the object file during the commit right after manifesting; as then repoman would perceive things to be okay, but proceed with committing the new tampered state. I don't think this is something we can account for. Overall, unless this has happened a lot more times than this one occurrence, I think it's not worth the effort looking into this as it loses more than we gain.
Zac, what do you think... seems file.notadded is still not part of repoman
Yeah a file.notadded error sounds good. As it is, commit bails out abruptly like this: if myunadded: print(red( "!!! The following files are in your local tree" " but are not added to the master")) print(red( "!!! tree. Please remove them from the local tree" " or add them to the master tree.")) for x in myunadded: print(" ", x) print() print() sys.exit(1)
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
