Since 30daff5613803667be7422056431116e84c07d59 we check if the repos are
still what we expected them to be when we started and stop calculating
weakremovers.inc if the build didn't stay still for the full runtime of
the pkglistgen. But the exception makes it impossible to spot real
failures - so make this a regular exit
I decided not to reduce it's code because no one knows what the future
will bring exactly (and only then we should decide), but I'll close the
tickets mostly.
The mtime of a file in OBS is the time this content was created for the
first time. As such if the target project isn't moving for a week,
staging select will keep asking you to freeze - even if you just froze.
So instead of relying on OBS to tell the true mtime, set an attribute
in the staging project and read from it. This also gives a way to check
in the webui for the last freeze time
Fixes#2462
Since update project has different set up than GA project, it
should check content from update project prior to GA when run this
script for Leap Respin.
As we don't do automatic origin updates in no project, remove the
update monitors. Those have been paused on botmaster for half a year
and just no project relies on them any longer
In case regex list has not been defined any value, the first element
will be space only, this causes unconditional matched any binary name.
Exit the for loop if the first element is space only.
The service is down for 2 years and more and it was unused ever since.
The idea just never took off (also because it was pretty late in the
cycle and leap wasn't developed much longer the way it used to when
the design for this was created).
For the next SLE/Leap it's just very, very unclear how it will look
like and I'm 99% sure it's not going to go back to old Leap. So the
whole operator needs more work and maintenance than the current team
has, so keep it in the git history only.
It was introduced by #2159 because the various machines were hard to
monitor. Since we moved to botmaster there is no longer a problem with
that and if it ever served us is hard to say as the sentry project's
password is lost for years. So simplify the exception handling by just
throwing it
The staging status doesn't provide the by_project and it's not
really important here, so simplify
Before:
adi:39 review: None/ekiga for ekiga[955924]
After:
adi:39 review: package:ekiga for ekiga[955924]
