Bug#826739: marked as done (transition: libconfuse)
Your message dated Tue, 14 Jun 2016 19:41:20 +0200
with message-id <9098996d-176e-b704-5e81-3a989daba1a7@debian.org>
and subject line Re: Bug#826593: transition: confuse
has caused the Debian Bug report #826593,
regarding transition: libconfuse
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.)
--
826593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826593
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
Hi release team,
looks like there was an uncoordinated library transition when libconfuse
3.0 was uploaded to unstable bumping the soname.
I guess we should start binNMUing packages found by the autotracker [¹].
Regards,
Michael
[¹] https://release.debian.org/transitions/html/auto-confuse.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 06/06/16 22:31, Aurelien Jarno wrote:
> On 2016-06-06 20:30, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 confirmed
>>
>> On 06/06/16 20:25, Aurelien Jarno wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: transition
>>>
>>> Dear release team,
>>>
>>> Upstream has released a new version of confuse, which includes an ABI
>>> change from libconfuse0 to libconfuse1. I have already uploaded the new
>>> version to experimental, so a tracker is already available [1] to get
>>> the list of reverse dependencies
>>>
>>> In addition I have been able to successfully build all reverse
>>> dependencies against this version on amd64. I therefore do not expect
>>> any particular issue with this transition.
>>
>> Go ahead.
>
> Thanks for the quick answer. I have just uploaded it to sid.
This is over.
Emilio
--- End Message ---
Reply to: