Your message dated Sun, 31 May 2026 18:45:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#1138084: nmu: tinyxml2_11.0.0+dfsg-1
has caused the Debian Bug report #1138084,
regarding nmu: tinyxml2_11.0.0+dfsg-1
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.)
--
1138084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1138084
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:tinyxml2
User: [email protected]
Usertags: binnmu
Heya,
There seems to be a discrepancy in changelog.Debian.gz between loong64
and other arches. Inspecting it, it looks like the debian changelog has
been trimmed to a different length in loong64 compared to other
architectures, and this is making it so that libtinyxml2-11 and
libtinyxml2-dev are not co-installable between loong64 and other arches
despite being Multi-Arch: same.
libtinyxml2-11 conflicts on /usr/share/doc/libtinyxml2-11/changelog.Debian.gz
on loong64 <-> amd64, arm64, armhf and 4 more
libtinyxml2-dev conflicts on
/usr/share/doc/libtinyxml2-dev/changelog.Debian.gz on loong64 <-> amd64, arm64,
armhf and 4 more
I assume that the difference in changelog.Debian.gz truncation comes
from when bookworm became oldstable, so I think a rebuild across all
architectures should fix it.
nmu tinyxml2_11.0.0+dfsg-1 . ANY . unstable . -m "Rebuild to sync up
changelog.Debian.gz contents"
--
Thanks,
Loong Jin
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 2026-05-28 16:01:12 +0800, Chow Loong Jin wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: [email protected]
> Control: affects -1 + src:tinyxml2
> User: [email protected]
> Usertags: binnmu
>
> Heya,
>
> There seems to be a discrepancy in changelog.Debian.gz between loong64
> and other arches. Inspecting it, it looks like the debian changelog has
> been trimmed to a different length in loong64 compared to other
> architectures, and this is making it so that libtinyxml2-11 and
> libtinyxml2-dev are not co-installable between loong64 and other arches
> despite being Multi-Arch: same.
>
> libtinyxml2-11 conflicts on
> /usr/share/doc/libtinyxml2-11/changelog.Debian.gz on loong64 <-> amd64,
> arm64, armhf and 4 more
> libtinyxml2-dev conflicts on
> /usr/share/doc/libtinyxml2-dev/changelog.Debian.gz on loong64 <-> amd64,
> arm64, armhf and 4 more
>
> I assume that the difference in changelog.Debian.gz truncation comes
> from when bookworm became oldstable, so I think a rebuild across all
> architectures should fix it.
>
> nmu tinyxml2_11.0.0+dfsg-1 . ANY . unstable . -m "Rebuild to sync up
> changelog.Debian.gz contents"
Scheduled
Cheers
--
Sebastian Ramacher
--- End Message ---
