On Fri, Mar 02, 2018 at 06:10:16AM +0100, Ralf Corsepius wrote: > On 02/28/2018 05:43 PM, Adam Williamson wrote: > > On Wed, 2018-02-28 at 12:14 +0100, Ralf Corsepius wrote: > > > On 02/27/2018 07:27 PM, Richard Shaw wrote: > > > > On Tue, Feb 27, 2018 at 12:16 PM, Adam Williamson > > > > <adamwill@xxxxxxxxxxxxxxxxx <mailto:adamwill@xxxxxxxxxxxxxxxxx>> wrote: > > > > > > > > > > > > Once again, folks, *please* announce your soname bumps, and co-ordinate > > > > rebuilds. (In fact it looks like Zdenek is the maintainer of both > > > > packages and could have rebuilt cups-filters, but just forgot to). > > > > > > > > > > > > Is it time to update the packaging guidelines to enforce setting a > > > > "%global sover <X>" and using it in %files? > > > > > > > > If nothing else it should at least be documented as a best practice. > > > > > > I would be very opposed to this. > > > > > > Even though some folks want rawhide to appear a release, rawhide is not > > > a release. So SONAME breakages are expected to happen in rawhide and > > > maintainers supposed to be reacted upon. > > > > This is not true and I have *specifically* pointed you at the policy > > page which says it is not true, more than once. > > And I have to reiterate my mantra: This plan is a non-realistic illusion. It > simply does not work and will not work. > > > https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master > > > > For updates to rawhide packages, Maintainers SHOULD: > > > > Try not to push a clearly broken build (breaks the default > > buildroot package set, etc) > > Note the "SHOULD" - This is the reflection of what I said above. The SHOULD is necessary as otherwise we'll never be able to do soname bumps, but that doesn't say: be reckless and ignore the people you're giving work to. I think we all agree soname bumps happen and are necessary, what we try to advocate is that they don't happen by accident, that the packager pushing it knows what they are doing and announce it to the people it impacts. Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
