On 9/25/23 20:18, Levente Polyak wrote:
Hi all,
this is mostly a notification mail about some inconsistencies with dbscripts where under specific circumstances some leftover packages remain in staging or testing. This issue seems to exist since the last major rollout in June.
There seem to be at least two different bugs involved, one in `db remove` and another one in `db move`. I've tracked down the `db remove` one, and am debugging the other issue which also affects libreoffice. I've also written an `fsck` script to detect issues inside the pacman binary repo or within the dbscripts state repo. It seems since June this lead to around 15 occurrences.
If you encounter a new leftover package, please feel welcomed to send me a ping. I'm happy to try to help you, or just check if it may be a new or an existing issue. However, there isn't any actionable for packagers for the time being as leftover packages can't be manually removed via `db remove`. I'll correct the inconsistencies as soon as the bug is resolved.
Hope this helps one or the other packager to get some insights into the existence of this issue.
Cheers, Levente
Hi all, after a massive amount of work the time has come to roll out some major changes to address the most currently known issues and concurrency problems. I will be rolling out multiple batches of updates to dbscripts during the weekend. This means you may not be able to ssh into repos.archlinux.org to release packages for short period of times. If you encounter anything weird, other than not being able to ssh into the repos server, please ping me as soon as possible. Cheers, Levente