On Tue, 2017-03-14 at 09:30 +0100, Richard Biener wrote:
In the past I was (repeatedly) asking for "old" shlib packages _not_ to be pruned like this but "garbage collected" only. Both from _repository (to avoid dances when doing SONAME updates in Ring-0) and of course from published repositories.
But appearantly it's not annoying often enough to warrant fixing...
Oh it IS annoying enough - at least from a distro-building PoV; sadly, not for OBS it seems. We are currently seeking options on how to design our process to make sure we can avoid this... so far the idea in my head is: * when a delete request is 'ready to accept' - don't accept it, but only build-disable the pkg and wipe the binaries of the package in openSUSE:Factory/standard => this results in the package to be gone from /standard, but the binaries remain in /snapshot * once /standard is copied to /snapshot (so in fact, the snapshot had been built, tested AND published), ultimately accept the delete request Now this sounds very simplistic, but to get it right might be a bit more complex - especially when taking into account that the time between disabling /standard and having the binaries removed from /snapshot is not exactly clear - and we also have to make sure to catch all linked packages of the first one. Add on top of that a new package might be introduced to replace the old one, then the workflow is again different. But this is what we are currently trying to work out from the distro process side of things - as the tooling so far does not allow us to 'just go ahead'. cheers, Dominique