epkgmove needs to regenerate the Manifest after commiting the package to the new location because the $Header: $ CVS keyword tag in ChangeLog and *.ebuild will change during commit. This breaks FEATURES="strict" as portage checks the Manifest against the files in the tree.
Fixed in 1.2: http://dev.gentoo.org/~port001/DevTools/epkgmove/epkgmove-1.2.py
Looking at epkgmove-1.2.py it seems that it only re-commits the Manifest if sign is in FEATURES. It should always be recommited. And forcing a digest regeneration for all ebuilds to just update the Manifest is probably wrong too. The forced digest regeneration forces downloading of the distfiles, if the files are not yet available in DISTDIR. The digests should not be affected by a move.
The Manifest is re-commited when 'ebuild foo digest' is called, and commited once more if 'sign' is in features. 1.3 doesn't regen the digests when not needed. http://dev.gentoo.org/~port001/DevTools/epkgmove/epkgmove-1.3.py
Created attachment 46353 [details, diff] epkgmove-1.3.py.patch The Manifest re-commit should not depend on sign in FEATURES. The sign step is optional before committing the Manifest.
You're miss reading the code. What you are looking at is the gpg signing function which signs the Manifest if 'sign' is in FEATURES. The non-signed Manifest is regenerated and commited before this function is even called.
Doh, I'm the one miss reading my _own_ code lol.
1.3.1 in the usual place
