Your message dated Wed, 03 Sep 2025 03:50:39 +0000
with message-id <[email protected]>
and subject line Bug#1112637: fixed in xmbmon 2.05-12
has caused the Debian Bug report #1112637,
regarding xmbmon FTBFS on !x86: <sys/io.h> not found
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.)


-- 
1112637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112637
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xmbmon
Severity: important
Tags: ftbfs

xmbmon fails to build from source on all non-x86 architectures as it 
attempts to #include <sys/io.h>. This has been the case for many years 
and is probably fine. However, QA stuff can run into this problem and 
documenting the FTBFS lowers the noise on the QA side. An alternative 
would be to forbid building on non-x86:

    Build-Depends: unsupported-architecture [!any-amd64 !any-i386]

I'm not sure that that's better than the status quo though. In any case, 
this report should not be worrying. It probably works fine on x86 and 
may not be useful elsewhere.

Helmut

--- End Message ---
--- Begin Message ---
Source: xmbmon
Source-Version: 2.05-12
Done: наб <[email protected]>

We believe that the bug you reported is fixed in the latest version of
xmbmon, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
наб <[email protected]> (supplier of updated xmbmon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 03 Sep 2025 05:09:38 +0200
Source: xmbmon
Architecture: source
Version: 2.05-12
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: наб <[email protected]>
Closes: 1112637
Changes:
 xmbmon (2.05-12) unstable; urgency=medium
 .
   * Team upload
   * d/control: Architecture: any -> i386 x32 amd64 (Closes: #1112637)
Checksums-Sha1:
 4a1fe7156d4caeb55dffac5ae9e1c028849dc059 2077 xmbmon_2.05-12.dsc
 5626e32850f08e3331811c701b51351cea9c72ad 143004 xmbmon_2.05.orig.tar.gz
 922e3847c52b90039eb7f1694b62bc0bedf12ca6 14500 xmbmon_2.05-12.debian.tar.xz
 c09c83eb32907083fbdb11429b02df8d003168eb 7783 xmbmon_2.05-12_source.buildinfo
Checksums-Sha256:
 dcdcd66b29d2a2552ea09c6aa315ee5f13a168607212a8a6cb7bbe8968946e25 2077 
xmbmon_2.05-12.dsc
 36d00816cda354636fd9896c6bcfdfded0a3c10a77f6bfffb82004c46e5536ab 143004 
xmbmon_2.05.orig.tar.gz
 47dcc3ec4973a784690d5d84c1f1a6516975967ebc4c612b2ba4ee700d0055ed 14500 
xmbmon_2.05-12.debian.tar.xz
 6ee44e6f8b9ffeae06e1b393a16986e40fba6fe1b4555ff1c0c4636fdc421f7f 7783 
xmbmon_2.05-12_source.buildinfo
Files:
 eb3f1ac2093adfcda04f02d0060584ac 2077 admin optional xmbmon_2.05-12.dsc
 b454be9327c34c42af5ad4372251f5b0 143004 admin optional xmbmon_2.05.orig.tar.gz
 1eb014c6962b67a21b55089b69c1e3a2 14500 admin optional 
xmbmon_2.05-12.debian.tar.xz
 55a0359091a57ac2b9c1cff95e524a2e 7783 admin optional 
xmbmon_2.05-12_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJWBAEBCgBAFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmi3smgiHG5hYmlqYWN6
bGV3ZWxpQG5hYmlqYWN6bGV3ZWxpLnh5egAKCRC8/QsBjSZY8TzLD/0erm+IKRCF
5/2VRgj9KMAuXFsbZX9O53hdx5SGDcf7p5fsWeeu3TOJw96iTtSoIFpgQ706lDHW
8m7nOOzMrqWQzriy0arQ0r/yAJ8/PlqxODhRk2dSiAKODLPTEJa7jWU3lALSyvcJ
TK/G5nvvREuLkXy7CdQ5AyQRjFm4/ngu13Ux+gpEOApThlA9IuISsXukHm8Id1Cs
NDuPB2XWikK1ZozufWJOOmIzL4hzxt4ypGRWa6+M68zJBj3gIrHAxTJeeif1uRrC
6AY6HCLQa11V+7qr03Pd6x4MFtd7xEi/9Dys009ezdTnClkETHL3US7Vh2OpF6Q8
IfEc47W+M8fRMP+OgB8KbhYebZm3BM8YKcFYpl7g4fBKHKfoES6JT2dvp/DdRZ8O
rf7O5hG1ytkz5pHYY48yBF8Tv5spN9dQJM04OM/6dFEUOpnWoq38JuR/JqHFw4FR
kO5C6aB5jLvAcOHiraldcapHu23TQpBAjrwN7Ak40DF5IjOxhcfjgdCregzFFO3X
vLke0aaWoYX2Qkbgb1pg1tjOoNRjOOxJuEc9f4d/ETSD8dU9rpJ/Thtl0gW3kJEm
oRyqNeKVW2UJHhQkFtvH5fyrfcDMPByQO2PP3sesBTygozllCQoCkK09NbqiZMn/
EjmKroEDI+lVrnYixqePm5iYp/l57i2SxQ==
=7F+t
-----END PGP SIGNATURE-----

Attachment: pgpVYazNZO_vs.pgp
Description: PGP signature


--- End Message ---

Reply via email to