Your message dated Tue, 16 Dec 2025 17:20:57 -0500
with message-id
<CAAajCMbFYJ8Ca8ZzFo==-7i-cAp_oahs1JNfO=ethE69fw=p...@mail.gmail.com>
and subject line Re: can appstream-util be marked Multi-Arch: foreign?
has caused the Debian Bug report #923633,
regarding can appstream-util be marked Multi-Arch: foreign?
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.)
--
923633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923633
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: appstream-util
Version: 0.7.14-1
User: [email protected]
Usertags: rebootstrap
Control: affects -1 + src:gnome-power-manager
gnome-power-manager fails to cross build from source, because it fails
running appstream-util with an Exec format error. Usually, that
indicates that appstream-util was installed for the host architecture
when it was needed for the build architecture. There are multiple ways
to achieve that and one of them is marking appstream-util Multi-Arch:
foreign. Whenever that is the right thing to do, it is preferred.
The interesting question is whether doing so is correct. Multi-Arch:
foreign says that the interface of the package is independent of the
package architecture. Since appstream-util primarily contains programs,
this is at least possible. The manual pages are not very helpful for
finding out what these programs do however. It seems that part of their
job is dealing with XML, which is a textual (and thus
architecture-independent) format. What the other formats are is unclear
to me.
Thus I seek your help with understanding what appstream-util does and
whether we can mark it. Do you know any invocation where the observable
behaviour varies with the architecture of the appstream-util package?
Thanks for your help
Helmut
--- End Message ---
--- Begin Message ---
I'm closing this bug since gnome-power-manager is now cross-buildable.
https://crossqa.debian.net/src/gnome-power-manager
gnome-power-manager switched from appstream-util to appstream (and
appstream is marked as Multi-Arch: foreign). So have all the other
apps listed as affected for this bug except for xiphos. The xiphos bug
is https://bugs.debian.org/1119109 and it seems achievable for
appstream-glib (appstream-util) to be removed from Debian before
Debian 14 is released.
Thank you,
Jeremy Bícha
--- End Message ---
