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 0706db69d48e8fa9423587f0d11727075b0d3d5f (commit)
from f2e8d57e7fde40fd5a3e80e1f152ae850ac3c369 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 0706db69d48e8fa9423587f0d11727075b0d3d5f
Author: Florian Pritz <bluewind(a)xinu.at>
Date: Sat Jul 13 20:58:07 2019 +0200
Look for repro packages in live repo pool too
I've cleaned older packages from the archive, but sometimes we do not
rebuild packages in a long long time. We still keep have them in the
repository, but this check does not look for the package there, thus
when trying to db-update, the user sees an error. We fix this by also
looking at currently live packages instead of only relying on the
archive.
This is mostly a hotfix until a better solution is created. Depending on
when/how the ftpdir-cleanup cronjob removes such packages, users may
still see errors when an old package is updated and the cronjob removes
it from the repository before db-update is run.
Signed-off-by: Florian Pritz <bluewind(a)xinu.at>
-----------------------------------------------------------------------
Summary of changes:
db-functions | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
Official repo DB scripts