A semi-common pattern is for one maintainer to stage a rebuild of a
package due to e.g. cascading repository-wide python/boost/whatever
rebuilds, and then for the original maintainer of the package to not
notice and update the package in the stable repo, leaving an out of date
rebuild in staging
At the point when it was being run, the signature was not yet moved to
PKGPOOL.
Signed-off-by: Eli Schwartz
---
Discovered while debugging the verify branch.
db-update | 2 +-
test/cases/db-update.bats | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via 948a181f5f09ca1cc03d450081f296222ca26d2f (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, verify-update-plus-rebuild has been created
at 77c72694e608decd63978f3ae6d941487476ef98
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via f11a038c43270a70eafdba34ff33e134b6726a04 (commit)
via
