As of this writing, the following changes are needed to resolve the issues I know about that are triggering bug 577722: * Dipper's copy of portage needs to be updated to 2.3.0 * As a result, dipper needs repoman 2.3.0 in package.accept_keywords and installed Zac made a change to ChangeLog generation that landed in 2.3.0. That change is here: https://gitweb.gentoo.org/proj/portage.git/commit/?id=8e57a8b34cc552267dd987f744f04d021041c75b Basically, the check to see if the ChangeLog needs regenerating now checks whether the ChangeLog mtime exactly matches the newest commit to that package directory. Once the ChangeLog is regenerated, its mtime is set to match the commit time of the newest commit it contains. *NOTE*: the first rsync-gen run with --update-changelogs after this update will regenerate all ChangeLogs, because their mtimes are wrong (and there are some instances where their contents are wrong too). While we're at it, I have two patches for thicken_manifests.py. The first was attached to bug 577722, but I'm attaching it here so everything is in one place. The second fixes some edge cases mrueg and I noticed. There's one last thing that is a nice-to-have. It would be great if there was some way for me to get access to the rsync-gen stagedir and finaldir on dipper without needing somebody to reactivate my user account on dipper. I was thinking rsync exports that are either restricted to a certain IP address, or require a password to access.
Created attachment 449976 [details, diff] patch 1
Created attachment 449978 [details, diff] patch 2
> * As a result, dipper needs repoman 2.3.0 in package.accept_keywords and installed Repoman 2.3.0 is now stable on amd64, so no package.accept_keywords entry is needed anymore.
All of this is live
