Re: Binary compatibility policy for security updates and point releases

2019-03-19 Thread Bastian Blank
On Tue, Mar 19, 2019 at 10:50:04PM +0100, Gilles Filippini wrote: > Are these incompatible changes from security updates advertised somewhere? > > On a related matter we've just experienced at $work a scientific > software breakage after a recent jessie security upgrade. Jessie does not longer ge

Re: Binary compatibility policy for security updates and point releases

2019-03-19 Thread Gilles Filippini
Hi, Ondřej Surý a écrit le 17/03/2019 à 08:43 : > 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. Are these incom

Re: Binary compatibility policy for security updates and point releases

2019-03-19 Thread Florian Weimer
* Jakob Leben: > Well, there are use cases that are not so simple. For example: I might > deploy Debian 9.1 on an embedded machine sold to a client on the other side > of the world. I have a system for updating my own software which is also > deployed on that machine, but not the rest of the Debia

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Ximin Luo
Sam Hartman: >> "Ximin" == Ximin Luo writes: > > Ximin> Jakob Leben: > >> I have a system for updating my own software which is also > >> deployed > > Ximin> If you Depends: libfoo8, this will prevent dpkg from > Ximin> upgrading the library from libfoo8 to libfoo9 until

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Sam Hartman
> "Jakob" == Jakob Leben writes: Jakob>Well, there are use cases that are not so simple. For Jakob> example: I might deploy Debian 9.1 on an embedded machine Jakob> sold to a client on the other side of the world. I have a Jakob> system for updating my own software which i

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Ximin Luo
Jakob Leben: > I have a system for updating my own software which is also deployed on that > machine, but not the rest of the Debian system. Now, if ABI might change > between 9.2, then I have no guarantee that if I test my software update with > 9.2, it will be work as expected on the client's

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Jakob Leben
On Sun, Mar 17, 2019 at 12:11 AM Ximin Luo wrote: > > In general, if no documented guarantee exists then you should assume there > is no guarantee. > That's what I thought too. If you are a developer and you link against a particular version of a > library in Debian 9.1 and its ABI changes in

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Ondřej Surý
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ý > On 17 Mar 2019, at 08:10, Ximin Luo wrote: > > Jak

Re: Binary compatibility policy for security updates and point releases

2019-03-17 Thread Ximin Luo
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. Stil

Binary compatibility policy for security updates and point releases

2019-03-16 Thread 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