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

Bug#1070977: marked as done (transition: snappy)



Your message dated Thu, 30 May 2024 18:41:51 +0200
with message-id <CAKjSHr1YjKn8=Ai2oW4pExsrwfFUH-v+Tw=uVfDNRx0bkRjnCg@mail.gmail.com>
and subject line Re: Bug#1070977: transition: snappy
has caused the Debian Bug report #1070977,
regarding transition: snappy
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.)


-- 
1070977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070977
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: affects -1 + src:snappy

Hi RMs,

Upstream of snappy changed function signatures [1] breaking other
applications with the 1.2.0 release. I've added back the original
function signatures calling the new ones to restore the immediate
problem, to restore the ABI. But then this creates ambiguity in the
Compress method signatures [2] making (only) ceph FTBFS. While it can
be patched to avoid it, a proper transition should be done.
I've renamed back the library name which was done due to the C++11 ABI
change with g++ 5.0 back in 2015.

Thanks for considering,
Laszlo/GCS
[1] https://bugs.debian.org/1070217
[2] https://bugs.debian.org/1070785

--- End Message ---
--- Begin Message ---
On Wed, May 22, 2024 at 9:11 AM Emilio Pozuelo Monfort <pochu@debian.org> wrote:
> Looks like this got reported upstream and the symbols got re-added:
[...]
> If that's enough, I assume the package renaming in experimental can be reverted
> and we just update to snappy 1.2.1, keeping the old library package name.
 That's the best solution already provided. As you noted, the
transition is reverted and a normal package update to version 1.2.1
was made. It was built on all architectures, autopkgtests succeeded
and the updated snappy is migrated to testing.
As such, closing this transition request.

Regards,
Laszlo/GCS

--- End Message ---

Reply to: