I used to use the following work flow: 1) repoman commit --ask ... -- to perform repoman checks, update the Manifests, 2) test the package using emerge, 3) answer 'yes' to commit. That doesn't work any longer with --echangelog=y as it updates the ChangeLog after regenerating Manifest and thus makes it no longer valid. I'd appreciate if the Manifest update could either be delayed, or ChangeLog update moved earlier (or even later, i.e. after asking).
(In reply to comment #0) > I used to use the following work flow: > > 1) repoman commit --ask ... -- to perform repoman checks, update the > Manifests, > 2) test the package using emerge, > 3) answer 'yes' to commit. Seems like an odd workflow. I guess that most people test the package with emerge before they issue the repoman commit command. > That doesn't work any longer with --echangelog=y as it updates the ChangeLog > after regenerating Manifest and thus makes it no longer valid. I'd > appreciate if the Manifest update could either be delayed, or ChangeLog > update moved earlier (or even later, i.e. after asking). We could easily regenerate the corresponding Manifest immediately after each ChangeLog is modified.
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=908de31ae2049eef02432d73478a403ffcad1ead
Here's a little tweak so that it only regenerates the Manifest when --ask it specified: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=8063586060f7d4abfa02639ba72c0e9b38ed634a
This is fixed in 2.1.11 and 2.2.0_alpha111.
