Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.project > #10389

Re: Binary compatibility policy for security updates and point releases

From Gilles Filippini <pini@debian.org>
Newsgroups linux.debian.project
Subject Re: Binary compatibility policy for security updates and point releases
Date 2019-03-19 23:00 +0100
Message-ID <xDuW5-4pe-5@gated-at.bofh.it> (permalink)
References <xCvhw-50z-1@gated-at.bofh.it> <xCyfn-6Ph-5@gated-at.bofh.it> <xCyIq-6ZD-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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 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. The breakage
is caused by the upgrade of ghostscript to 9.26a~dfsg-0+deb8u1. In this
new ghostscript release the pswrite driver used by our software was
deprecated.
The fix is easy (use the ps2write driver instead), but my colleagues are
now very concerned about Debian security upgrades which can introduce
such non backward compatible changes.
Shouldn't backward incompatibilities introduced by security upgrades be
advertised somewhere? At least in the NEWS.Debian file?

Thanks in advance for any input,

_g.


Back to linux.debian.project | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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