[New: openFATE 314498] keep old rpms for some hours after publish
Feature added by: Bernhard Wiedemann (bmwiedemann) Feature #314498, revision 1 Title: keep old rpms for some hours after publish Buildservice: Unconfirmed Priority Requester: Important Requested by: Bernhard Wiedemann (bmwiedemann) Partner organization: openSUSE.org Description: When installing a larger number of packages from an OBS repo (can take a few hours), it often happens that a publish event happens in the middle and zypper can no more download an rpm, because it was deleted on the server side. Workarounding this in zypper is hard and workarounding this in every script calling zypper is ugly. This works for our update repos, because all old rpms are kept in there. And it works for our released product repos, because they do not change after the release. The cleanest way to solve this for OBS repos is to keep old rpms around for at least three hours after a publish happened. For example, it could take the form of a cron.hourly job that searches for repos that were last published x hours ago and then runs rsync --delete on them. Use Case: For our SUSE Cloud Product we do continuous integration testing that automatically installs the latest version of all packages on a fresh VM and this sometimes fails from repo publishing. -- openSUSE Feature: https://features.opensuse.org/314498
participants (1)
-
fate_noreply@suse.de