Your message dated Tue, 10 Mar 2026 10:20:09 +0000
with message-id <[email protected]>
and subject line Re: Bug#1121321: lordsawar: depends on superseded libxml++2.6
has caused the Debian Bug report #1121321,
regarding lordsawar: depends on superseded libxml++2.6
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.)
--
1121321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121321
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lordsawar
Version: 0.3.2+frogknows-1.1
Severity: normal
Tags: forky sid upstream
Control: block 1038804 by -1
User: [email protected]
Usertags: oldlibs libxml++2.6
Binaries produced by this source package depend on libxml++2.6, a C++
wrapper around libxml2.
libxml++2.6 is no longer maintained upstream (#1038804). It has been
superseded by libxml++-3.0, which was itself superseded by libxml++-4.0
(RFP: #819562) and libxml++-5.0 (RFP: #1121304).
If this package is ported to one of the newer libraries, packaging the new
version will require packaging the new library first. I haven't marked
#819562 and #1121304 as blockers for this bug, because I don't know which
one would be more appropriate.
smcv
--- End Message ---
--- Begin Message ---
Version: 0.3.2+frogknows-2
On Mon, 24 Nov 2025 at 13:10:56 +0000, Simon McVittie wrote:
Binaries produced by this source package depend on libxml++2.6, a C++
wrapper around libxml2.
This was fixed:
lordsawar (0.3.2+frogknows-2) unstable; urgency=medium
...
* Upgrade dependency from libxml++2.6 to libxml++-5.0
—
https://tracker.debian.org/news/1718116/accepted-lordsawar-032frogknows-2-source-into-unstable/
--- End Message ---
