[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924459: marked as done (transition: libdmtx)

Your message dated Thu, 18 Apr 2019 12:02:00 +0000
with message-id <a4a51bf0-0db5-4122-7957-84f9b52272e3@thykier.net>
and subject line Re: Bug#924459: transition: libdmtx
has caused the Debian Bug report #924459,
regarding transition: libdmtx
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
924459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924459
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Control: block -1 by 908815
X-Debbugs-Cc: Roberto Lumbreras <rover@debian.org>

As discussed with jmw at the Cambridge BSP, libdmtx0a has broken ABI
without changing its SONAME (#908815). Judging by the name, this isn't the
first time. The quickest way to a correct situation in buster seems to
be a transition to a new binary package name libdmtx0b that represents
the new ABI, which is currently waiting in NEW for experimental.

Ben file:

title = "libdmtx";
is_affected = .depends ~ "libdmtx0a" | .depends ~ "libdmtx0b";
is_good = .depends ~ "libdmtx0b";
is_bad = .depends ~ "libdmtx0a";

Only a few packages are affected:

dmtx-utils: dmtx-utils
openrpt: libopenrpt1v5
         openrpt
postbooks: postbooks
prison-kf5: libkf5prison5
visp: libvisp-detection3.1

In addition, dmtx-utils 0.7.6-1.1 will need to be unblocked (it just
removes a hard-coded libdmtx0a dependency so that the binNMU will be
installable: #924254). I've verified that dmtx-utils 0.7.6-1.1, when
rebuilt against libdmtx0b, gets a libdmtx0b (>= 0.7.5) dependency and
passes some simple tests.

For future Debian releases, it would be helpful if the maintainer of
libdmtx could teach their upstream about ABIs[1], and be extra-careful
to check for compatibility when importing new upstream releases. Adding
autopkgtests might also be useful: if updating libdmtx had caused the
old dmtx-utils to fail its tests, then we might have detected this sooner.

Thanks,
    smcv

[1] Maybe useful:
    https://events.static.linuxfound.org/sites/events/files/slides/Binary_Compatibility_for_library_devs.pdf

--- End Message ---
--- Begin Message --- 
Simon McVittie:
> On Wed, 13 Mar 2019 at 08:55:29 +0000, Simon McVittie wrote:
>> As discussed with jmw at the Cambridge BSP, libdmtx0a has broken ABI
>> without changing its SONAME (#908815).
> ...
>> Only a few packages are affected:
>>
>> dmtx-utils: dmtx-utils
>> openrpt: libopenrpt1v5
>>          openrpt
>> postbooks: postbooks
>> prison-kf5: libkf5prison5
>> visp: libvisp-detection3.1
> 
> I've uploaded libdmtx/0.7.5-2.2; please unblock it (debdiff attached)
> and schedule binNMUs as appropriate. I think this might be the right
> incantation:
> 
> unblock libdmtx/0.7.5-2.2
> 
> and
> 
> nmu dmtx-utils_0.7.6-1.1 openrpt_3.3.14-2 prison-kf5_5.54.0-1 visp_3.1.0-2 . ANY . -m 'Rebuild against libdmtx0b'
> dw dmtx-utils_0.7.6-1.1 openrpt_3.3.14-2 prison-kf5_5.54.0-1 visp_3.1.0-2 . ANY . -m 'libdmtx-dev (>= 0.7.5-2.2)'
> nmu postbooks_4.11.3-2 . ANY . -m 'Rebuild against libdmtx0b'
> dw postbooks_4.11.3-2 . ANY . -m 'libopenrpt-dev (>= 3.3.14-2+b1)'
> 
> libdmtx does still have a RC bug regarding an inconsistent d/copyright,
> opened after its excursion through the NEW queue (#926646); but only the
> maintainer can fix that one, and IMO a buster-ignore might be appropriate.
> 
> Thanks,
>     smcv
> 

This transition appears to be complete and everything migrated AFAICT,
so I will be closing the bug now.

Thanks,
~Niels

--- End Message ---
Reply to: