Re: How to handle ABI breakage in Rawhide

2021-12-07 Thread Florian Weimer
* Robert Relyea: > On 12/6/21 7:11 PM, Kevin Kofler via devel wrote: >> Florian Weimer wrote: >>> That's not actually true, though, and it does not make much sense. If >>> upstream commits to an ABI, versioning is not even required technically. >> Hardly any upstream actually commits to an ABI *f

Re: How to handle ABI breakage in Rawhide

2021-12-07 Thread Robert Relyea
On 12/6/21 7:11 PM, Kevin Kofler via devel wrote: Florian Weimer wrote: That's not actually true, though, and it does not make much sense. If upstream commits to an ABI, versioning is not even required technically. Hardly any upstream actually commits to an ABI *forever*. Even if the ABI has n

Re: How to handle ABI breakage in Rawhide

2021-12-06 Thread Kevin Kofler via devel
Florian Weimer wrote: > That's not actually true, though, and it does not make much sense. If > upstream commits to an ABI, versioning is not even required technically. Hardly any upstream actually commits to an ABI *forever*. Even if the ABI has not changed for 10 years, that does not mean that

Re: How to handle ABI breakage in Rawhide

2021-12-06 Thread Florian Weimer
* Otto Urpelainen: > Vitaly Zaitsev via devel kirjoitti 6.12.2021 klo 11.01: >> On 06/12/2021 03:39, Bernie Innocenti via devel wrote: >>> What are the current Fedora packaging guideline regarding ABI >>> stability of shared libraries? >> The package maintainer should ask upstream to bump the sove

Re: How to handle ABI breakage in Rawhide

2021-12-06 Thread Otto Urpelainen
Vitaly Zaitsev via devel kirjoitti 6.12.2021 klo 11.01: On 06/12/2021 03:39, Bernie Innocenti via devel wrote: What are the current Fedora packaging guideline regarding ABI stability of shared libraries? The package maintainer should ask upstream to bump the soversion field and if it is rejec

Re: How to handle ABI breakage in Rawhide

2021-12-06 Thread Vitaly Zaitsev via devel
On 06/12/2021 03:39, Bernie Innocenti via devel wrote: What are the current Fedora packaging guideline regarding ABI stability of shared libraries? The package maintainer should ask upstream to bump the soversion field and if it is rejected, bump it manually in downstream. -- Sincerely, Vi

Re: How to handle ABI breakage in Rawhide

2021-12-05 Thread David Airlie
On Mon, Dec 6, 2021 at 12:49 PM Bernie Innocenti wrote: > > Hello David, > > This spirv-tools-libs build changed the ABI of libSPIRV-Tools.so in > Rawhide on Nov 23: > https://koji.fedoraproject.org/koji/buildinfo?buildID=1858749 > > The shared lib has no soversion, and other libs in Fedora depend