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

Bug#1085204: marked as done (transition: libzip)

Your message dated Sun, 27 Oct 2024 18:02:50 +0100
with message-id <Zx5yOvkMgKvCaBH-@ramacher.at>
and subject line Re: Bug#1085204: transition: libzip
has caused the Debian Bug report #1085204,
regarding transition: libzip
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.)


-- 
1085204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085204
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
X-Debbugs-Cc: libzip@packages.debian.org, Ondřej Surý <ondrej@debian.org>
Control: affects -1 + src:libzip

Dear Release Team,

please grant a transition slot for the libzip transition.

Upstream has changed the soname from 4 to 5 quite a while ago, but until
now that had been reverted in the Debian packaging, cf.
https://sources.debian.org/src/libzip/1.7.3-1.1/debian/patches/0001-Reintroduce-dummy-zip_archive_set_tempdir-function-t.patch/
https://tracker.debian.org/news/1023453/accepted-libzip-151-2-source-into-experimental/
https://tracker.debian.org/news/1122959/accepted-libzip-161-3-source-into-unstable/

However, the libzip packaging has now been adjusted to reflect this.
For reference, according to upstream the dropped symbol was never fully
implemented or documented, and they are not aware of any software ever
using it. (They had private software where they thought it might be
useful, but then never needed it.)
In Debian, that symbol is only referenced in code copies of libzip, cf.
https://codesearch.debian.net/search?q=zip_archive_set_tempdir&literal=1

libzip itself has successfully built on all release architectures in
experimental, and I have successfully tested a rebuild of all
build-rdeps on amd64 against that version. Well, except for two which
currently FTBFS anyway and are not in testing: mysql-workbench #1074563
and xtrkcad #1074722. (Well, and qgis, but that was due to my build
environment having too limited resources.) So on that side things are
looking safe.

The information on
https://release.debian.org/transitions/html/auto-libzip.html looks correct
to me.

Ben file:

title = "libzip";
is_affected = .depends ~ "libzip4t64" | .depends ~ "libzip5";
is_good = .depends ~ "libzip5";
is_bad = .depends ~ "libzip4t64";

Cheers,
Flo

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 2024-10-24 20:53:27 +0200, Florian Ernst wrote:
> On Wed, Oct 23, 2024 at 03:18:29PM +0200, Florian Ernst wrote:
> > On Wed, Oct 23, 2024 at 01:54:01PM +0200, Emilio Pozuelo Monfort wrote:
> > > On 16/10/2024 11:49, Florian Ernst wrote:
> > > > [...]
> > > > The information on
> > > > https://release.debian.org/transitions/html/auto-libzip.html looks correct
> > > > to me.
> > > 
> > > Go ahead.
> > 
> > Thanks, just uploaded.
> 
> FWIW, the package has been autobuilt and uploaded on all architectures
> except for hurd-amd64, and its autopkgtest has also succeeded on all
> architectures it was executed on.

The old binaries got removed from testing. Closing

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: