Bug#1110012: marked as done (transition: libnl3 [forky])
Your message dated Wed, 24 Sep 2025 12:55:40 +0200
with message-id <8990adc9-b25f-4aa0-a879-bc86e2f0a2ab@debian.org>
and subject line Re: Bug#1110012: transition: libnl3 [forky]
has caused the Debian Bug report #1110012,
regarding transition: libnl3 [forky]
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.)
--
1110012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110012
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: libnl3 [forky]
- From: Chris Hofstädtler <zeha@debian.org>
- Date: Mon, 28 Jul 2025 08:38:40 +0200
- Message-id: <aIca8BsAyg6dQkeb@per.namespace.at>
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libnl3@packages.debian.org
Control: affects -1 + src:libnl3
User: release.debian.org@packages.debian.org
Usertags: transition
Hi,
libnl3 upstream enabled symbol versioning a longer time ago. In
Debian this was temporarily reverted. With libnl3 3.11.0 I want us
to get back in sync with upstream in this regard.
I've done a manual check on direct reverse dependencies, and the
change appears ABI-compatible. Programs linked against old libnl3
binary packages apparently pick up the symbols just fine.
The other way round, programs linked against libnl3 libs from
3.11.0-1 then require the full (with version) symbol name.
While theoretically there is no rebuild of the r-deps needed, I
think we should still rebuild them. I've done a local test rebuild
of all direct r-deps (*) and they build fine.
(*) except ceph, for disk space reasons.
Chris
Ben file (hopefully):
title = "libnl3";
is_affected = .depends ~ /libnl.*-3-200/;
is_good = .depends ~ /libnl.*-3-200 \(>= 3.11.0\)/;
is_bad = .depends ~ /libnl.*-3-200/;
--- End Message ---
--- Begin Message ---
On 04/09/2025 00:17, Chris Hofstaedtler wrote:
* Emilio Pozuelo Monfort <pochu@debian.org> [250903 08:32]:
On 28/07/2025 08:38, Chris Hofstädtler wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libnl3@packages.debian.org
Control: affects -1 + src:libnl3
User: release.debian.org@packages.debian.org
Usertags: transition
The other way round, programs linked against libnl3 libs from
3.11.0-1 then require the full (with version) symbol name.
Have you bumped the minimum version in .symbols then?
Yes.
While theoretically there is no rebuild of the r-deps needed, I
think we should still rebuild them. I've done a local test rebuild
of all direct r-deps (*) and they build fine.
I have scheduled the rebuilds, but I won't track their migration to testing as
that's not strictly needed. You can keep an eye on that asynchronously, e.g. see
if in a week or two the number of dependencies in forky's Package file have been
updated, and file bugs as needed if something is not migrating to testing for
whatever reason.
If you really want a transition page to track this, feel free to propose a ben file.
Cheers,
Emilio
--- End Message ---
Reply to: