Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.project > #10381
| From | Ondřej Surý <ondrej@sury.org> |
|---|---|
| Newsgroups | linux.debian.project |
| Subject | Re: Binary compatibility policy for security updates and point releases |
| Date | 2019-03-17 08:50 +0100 |
| Message-ID | <xCyIq-6ZD-11@gated-at.bofh.it> (permalink) |
| References | <xCvhw-50z-1@gated-at.bofh.it> <xCyfn-6Ph-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Jakob, the backward incompatible ABI changes are generally something we avoid in stable releases. There might be occasional exception to the rule where it cannot be avoided, but it is not something we take lightly. Ondrej -- Ondřej Surý <ondrej@sury.org> > On 17 Mar 2019, at 08:10, Ximin Luo <infinity0@debian.org> wrote: > > Jakob Leben: >> Hello, >> >> I have not been able to find clear information about Debian policies for ABI compatibility across point releases and security updates. I would assume that no ABI changes at all (backwards compatible or not) are allowed in point releases and security updates. Still, I have not found a clear and unambiguous statement to this effect in Debian documentation. >> >> Could someone please confirm the answer to my question? Would Debian developers consider improving documentation on this topic? >> > > In general, if no documented guarantee exists then you should assume there is no guarantee. > > If you are a developer and you link against a particular version of a library in Debian 9.1 and its ABI changes in 9.2, it's a simple task to rebuild it, and in fact that is what all reverse-dependencies of that library in Debian would themselves have to do. Not a big deal; as a developer you are supposed to deal with these issues and make it transparent to your end users. > > X > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > https://github.com/infinity0/pubkeys.git >
Back to linux.debian.project | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Binary compatibility policy for security updates and point releases Jakob Leben <jakob.leben@gmail.com> - 2019-03-17 05:10 +0100
Re: Binary compatibility policy for security updates and point releases Ximin Luo <infinity0@debian.org> - 2019-03-17 08:20 +0100
Re: Binary compatibility policy for security updates and point releases Ondřej Surý <ondrej@sury.org> - 2019-03-17 08:50 +0100
Re: Binary compatibility policy for security updates and point releases Gilles Filippini <pini@debian.org> - 2019-03-19 23:00 +0100
Re: Binary compatibility policy for security updates and point releases Bastian Blank <waldi@debian.org> - 2019-03-19 23:30 +0100
Re: Binary compatibility policy for security updates and point releases Jakob Leben <jakob.leben@gmail.com> - 2019-03-17 20:30 +0100
Re: Binary compatibility policy for security updates and point releases Ximin Luo <infinity0@debian.org> - 2019-03-17 21:00 +0100
Re: Binary compatibility policy for security updates and point releases Ximin Luo <infinity0@debian.org> - 2019-03-17 22:00 +0100
Re: Binary compatibility policy for security updates and point releases Sam Hartman <hartmans@debian.org> - 2019-03-17 21:30 +0100
Re: Binary compatibility policy for security updates and point releases Florian Weimer <fw@deneb.enyo.de> - 2019-03-19 18:50 +0100
csiph-web