A common workflow is:
* pkg is being marked for deletion by repo-checker [botdel]
* User comes to the rescue and fixes the package, Submits the fix
* Commonly, the delreq is being declined (by factory-maintainer)
* factory-auto declines SR, as pkg now has a delreq and subreq pending
* factory-auto does not consider the 'declined' request as replacable
and complains that it should be revoked (or superseded). Since the
del req was created by repo-checker, 'nobody' has the credentials to
revoke the request. The user, not having a role in the old SR, has
no permission to supersede
So let's just accept a delete request in statet 'declined' as something
that can be replaced by a submit request for the same package.
As image names have a pattern in 15-SP2 (SLE*), change the script that
release to TEST to use this image name pattern instead of list all
images.This will avoid frequently updates in script cause by new image
package submissions.
It takes a long time to sync the repos but ISOs are very quick. This lead
to the problem that openQA already started syncing the build while the
repo was synced up. As the repository is set to unpublished in between
the calls, openQA has no chance to see that more is to come.
So if we release the slow products first, openqa has a better chance to
catch up.
In the past, we had a dashboard reading the version of the current source from the .product file.
Not immediately updating this version after a checkin would have been confusing as the dashboard would
have shown incorrect/outdated information.
the new dashboard (https://factory-dashboard.opensuse.org) reads the source version directly from the
attribute, so this mis-match is eliminated.
The .product files will be updated by pkglistgen in due time.
openqa will keep polling the repository for ready to sync, waiting
for published event is a problem for ToTest repositories that aren't
published. openqa will start syncing when it becomes 'unpublished'
