[arch-projects] [dbscripts] [PATCH 1/3] testing2x: be more generic and accept multiple testing repos
Currently multilib is a second-class citizen the way it is lumped into
community, and dbscripts cannot even keep track of whether it
constitutes a testing repo. Teach config to track both testing and
staging repos just like the stable ones, and teach testing2x to search
through TESTING_REPOS to determine which one it is operating on.
Signed-off-by: Eli Schwartz
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 or testing.
Then the the out of date package gets moved and ends up breaking things,
possibly via a package downgrade, possibly via breaking compatibility
with a much more targeted rebuild uploaded all at once. Ultimately,
Things Happen™ and the repository hierarchy gets broken.
Prevent this by enforcing for all packages that exist in
multiple levels of the repo: staging -> testing -> stable
That updates to one must come with an update to all the others.
Signed-off-by: Eli Schwartz
Don't allow anomalous testing packages floating around after a rebuild
which are older than stable.
Signed-off-by: Eli Schwartz
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 or testing.
Then the the out of date package gets moved and ends up breaking things,
possibly via a package downgrade, possibly via breaking compatibility
with a much more targeted rebuild uploaded all at once. Ultimately,
Things Happen™ and the repository hierarchy gets broken.
Prevent this by enforcing for all packages that exist in
multiple levels of the repo: staging -> testing -> stable
That updates to one must come with an update to all the others.
Signed-off-by: Eli Schwartz
Don't allow anomalous testing packages floating around after a rebuild
which are older than stable.
Signed-off-by: Eli Schwartz
participants (1)
-
Eli Schwartz