Bug#1080177: transition: libxml2

[Aron Xu]

Package: release.debian.org
Severity: normal
User: ***@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-xml-sgml-***@lists.alioth.debian.org,
***@debian.org, ***@packages.debian.org
Control: affects -1 + src:libxml2

Dear Release Managers:

I'd like to request a transition slot to upload libxml2 for unstable
and start this transition.

libxml2 upstream has introduced some breaking changes to libxml2's ABI
, but upstream has concerns about bumping SONAME at the moment[1]. As
discussed previously through mails[2] and IRC, I'd like to do a
transition by renaming the binary package from libxml2 to libxml2n
(the letter "n" is randomly picked) without changing the library
SONAME.Since there are a few hundreds of direct reverse deps of
libxml2 in Debian, an entry of "Provides: libxml2 (=
${source:Version})" is added to avoid breaking the archive heavily
during the transition. It will be removed after the transition has
completed and reverse dependencies have migrated to depend on the new
package name.

I would like to express my sincere gratitude to all those involved in this work.

The Ben file auto-generated in the transition page looks fine to me:

title = "libxml2";
is_affected = .depends ~ /\b(libxml2n|libxml2)\b/;
is_good = .depends ~ /\b(libxml2n)\b/;
is_bad = .depends ~ /\b(libxml2)\b/;

Thanks.

[1]https://gitlab.gnome.org/GNOME/libxml2/-/issues/751
[2]https://bugs.debian.org/1073508

[Debian Bug Tracking System]

tags -1 moreinfo

Bug #1080177 [release.debian.org] transition: libxml2
Added tag(s) moreinfo.

[Sebastian Ramacher]

Control: tags -1 moreinfo

Hi Aron

Post by Aron Xu
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:libxml2
I'd like to request a transition slot to upload libxml2 for unstable
and start this transition.
libxml2 upstream has introduced some breaking changes to libxml2's ABI
, but upstream has concerns about bumping SONAME at the moment[1]. As
discussed previously through mails[2] and IRC, I'd like to do a
transition by renaming the binary package from libxml2 to libxml2n
(the letter "n" is randomly picked) without changing the library
SONAME.Since there are a few hundreds of direct reverse deps of
libxml2 in Debian, an entry of "Provides: libxml2 (=
${source:Version})" is added to avoid breaking the archive heavily
during the transition. It will be removed after the transition has
completed and reverse dependencies have migrated to depend on the new
package name.

Since upstream hasn't made up their mind yet, I think it is preferable
to revert the version in unstable to the last known good version. From
my understanding that is 2.9.14. We can then revisit this transition
when upstream decided how to continue or the transition freeze for
trixie comes close.

libxml2 is a core package where proper handling of the ABI is essential
for us. The time until the transition freeze is hopefully enough to get
some decision with upstream.

Cheers

Post by Aron Xu
I would like to express my sincere gratitude to all those involved in this work.
title = "libxml2";
is_affected = .depends ~ /\b(libxml2n|libxml2)\b/;
is_good = .depends ~ /\b(libxml2n)\b/;
is_bad = .depends ~ /\b(libxml2)\b/;
Thanks.
[1]https://gitlab.gnome.org/GNOME/libxml2/-/issues/751
[2]https://bugs.debian.org/1073508

[Sebastian Ramacher]

Hi Aron,

Post by Sebastian Ramacher
Control: tags -1 moreinfo
Hi Aron

Post by Aron Xu
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:libxml2
I'd like to request a transition slot to upload libxml2 for unstable
and start this transition.
libxml2 upstream has introduced some breaking changes to libxml2's ABI
, but upstream has concerns about bumping SONAME at the moment[1]. As
discussed previously through mails[2] and IRC, I'd like to do a
transition by renaming the binary package from libxml2 to libxml2n
(the letter "n" is randomly picked) without changing the library
SONAME.Since there are a few hundreds of direct reverse deps of
libxml2 in Debian, an entry of "Provides: libxml2 (=
${source:Version})" is added to avoid breaking the archive heavily
during the transition. It will be removed after the transition has
completed and reverse dependencies have migrated to depend on the new
package name.

Since upstream hasn't made up their mind yet, I think it is preferable
to revert the version in unstable to the last known good version. From
my understanding that is 2.9.14. We can then revisit this transition
when upstream decided how to continue or the transition freeze for
trixie comes close.

Any thoughts on that? If not, I will prepare an upload at the end of
this week so that we can get libxml2 unstuck and can work towards a
workable testing for riscv64.

Cheers

[Aron Xu]

Hi,

Post by Sebastian Ramacher
Hi Aron,

Post by Sebastian Ramacher
Control: tags -1 moreinfo
Hi Aron

Post by Aron Xu
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:libxml2
I'd like to request a transition slot to upload libxml2 for unstable
and start this transition.
libxml2 upstream has introduced some breaking changes to libxml2's ABI
, but upstream has concerns about bumping SONAME at the moment[1]. As
discussed previously through mails[2] and IRC, I'd like to do a
transition by renaming the binary package from libxml2 to libxml2n
(the letter "n" is randomly picked) without changing the library
SONAME.Since there are a few hundreds of direct reverse deps of
libxml2 in Debian, an entry of "Provides: libxml2 (=
${source:Version})" is added to avoid breaking the archive heavily
during the transition. It will be removed after the transition has
completed and reverse dependencies have migrated to depend on the new
package name.

Since upstream hasn't made up their mind yet, I think it is preferable
to revert the version in unstable to the last known good version. From
my understanding that is 2.9.14. We can then revisit this transition
when upstream decided how to continue or the transition freeze for
trixie comes close.

Any thoughts on that? If not, I will prepare an upload at the end of
this week so that we can get libxml2 unstuck and can work towards a
workable testing for riscv64.

Please go ahead, I'm still heavily stuck in recent $dayjob stuff...

Thanks,
Aron

[Sebastian Ramacher]

Post by Aron Xu

Post by Sebastian Ramacher

Post by Sebastian Ramacher

Post by Aron Xu
libxml2 upstream has introduced some breaking changes to libxml2's ABI
, but upstream has concerns about bumping SONAME at the moment[1]. As
discussed previously through mails[2] and IRC, I'd like to do a
transition by renaming the binary package from libxml2 to libxml2n
(the letter "n" is randomly picked) without changing the library
SONAME.Since there are a few hundreds of direct reverse deps of
libxml2 in Debian, an entry of "Provides: libxml2 (=
${source:Version})" is added to avoid breaking the archive heavily
during the transition. It will be removed after the transition has
completed and reverse dependencies have migrated to depend on the new
package name.

Since upstream hasn't made up their mind yet, I think it is preferable
to revert the version in unstable to the last known good version. From
my understanding that is 2.9.14. We can then revisit this transition
when upstream decided how to continue or the transition freeze for
trixie comes close.

Any thoughts on that? If not, I will prepare an upload at the end of
this week so that we can get libxml2 unstuck and can work towards a
workable testing for riscv64.

Please go ahead, I'm still heavily stuck in recent $dayjob stuff...

ACK, I have uploaded the attached debdiff (compared to the version in
testing).

Cheers

[Jeremy Bícha]

Aron and Sebastian,

What is the status of updating libxml2 to a newer version in Unstable?

There is a lot of log spam like https://bugs.debian.org/1072577 caused
by the revert to an older libxml.

Thank you,
Jeremy Bícha