Your message dated Sun, 28 Sep 2025 13:55:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#1106888: transition: libxml2, libxslt, xmlsec1 - one
transition to bind them all
has caused the Debian Bug report #1106888,
regarding transition: libxml2, libxslt, xmlsec1 - one transition to bind them
all
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 [email protected]
immediately.)
--
1106888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106888
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Tags: forky
X-Debbugs-CC: [email protected]
[this bug is NOT targeted to the upcoming trixie release]
The transition is also discussed in https://bugs.debian.org/1102294
I'm proposing to target these three transitions at the beginning of the
forky cycle, because these will entangle with many other transitions.
libxml2 2.14.x finally comes with a changed upstream soname, which
should make this transition easier than the previous attempts.
Lucas Nussbaum made a test rebuild
(http://qa-logs.debian.net/2025/05/23/), which I used to file bug reports at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libxml2.14;[email protected]
Note, that I only filed bug reports that I was able to reproduce for
Ubuntu, where this transition is almost done (at least migrated). There
are still unfixed issues, however these seem to be outside key packages
and didn't need initial fixing for starting this transition.
The auto tracker should be updated, or a new tracker be created:
title = "libxml2";
is_affected = .build-depends ~ /libxml2-dev/ | .depends ~ /(^|
)(libxml2-16|libxml2)([ ,]|$)/;
is_good = .depends ~ /\b(libxml2-16)\b/;
is_bad = .depends ~ /(^| )(libxml2)([ ,]|$)/;
--- End Message ---
--- Begin Message ---
On 31/05/2025 11:39, Matthias Klose wrote:
Package: release.debian.org
Tags: forky
X-Debbugs-CC: [email protected]
[this bug is NOT targeted to the upcoming trixie release]
The transition is also discussed in https://bugs.debian.org/1102294
I'm proposing to target these three transitions at the beginning of the
forky cycle, because these will entangle with many other transitions.
libxml2 2.14.x finally comes with a changed upstream soname, which
should make this transition easier than the previous attempts.
Lucas Nussbaum made a test rebuild
(http://qa-logs.debian.net/2025/05/23/), which I used to file bug reports at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libxml2.14;[email protected]
Note, that I only filed bug reports that I was able to reproduce for
Ubuntu, where this transition is almost done (at least migrated). There
are still unfixed issues, however these seem to be outside key packages
and didn't need initial fixing for starting this transition.
The auto tracker should be updated, or a new tracker be created:
title = "libxml2";
is_affected = .build-depends ~ /libxml2-dev/ | .depends ~ /(^|
)(libxml2-16|libxml2)([ ,]|$)/;
is_good = .depends ~ /\b(libxml2-16)\b/;
is_bad = .depends ~ /(^| )(libxml2)([ ,]|$)/;
libxml2.9 has been removed from testing, and libxml2_2.14.5 is in testing. Let's
close this bug.
Cheers,
Emilio
--- End Message ---
