Hi Paul,
thank you for the explanation. So the dependency on chromium is the
problem on these architectures.
Chromium is used to render tables in tables to pdf if command line
option -a is given.
Otherwise Chromium is not used.
If it helps to change the dependency to chromium and chromium-sandbox
from Depends to Recommends I would like to ask Georges to do so.
Yours Dirk
On 14.02.24 16:47, Paul Gevers wrote:
Hi,
On 14-02-2024 14:27, Georges Khaznadar wrote:
At the same time,
https://buildd.debian.org/status/package.php?p=mediawiki2latex
says that the package could be installed,
I understand the confusing but the word "installed" on buildd.d.o
means something else than that you can install the binaries. It means
that the packages were incorporated (installed) into the archive.
so its runtime dependencies
are correct, on architectures: amd64, arm64, armel, armhf, i386,
mips64el,
ppc64el, riscv64, s390x, alpha, hurd-i386, ia64, ppc64, sparc64.
Maybe you can try to install the binaries in a clean environment (I've
done so, pasted below).
Paul
root@autopkgtest-lxc-vtalsf:/tmp/autopkgtest-lxc.c47fu43n/downtmp/build.Nel/src#
apt install mediawiki2latex
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mediawiki2latex : Depends: chromium but it is not installable
Depends: chromium-sandbox but it is not installable
Recommends: calibre but it is not going to be
installed
Recommends: latex2rtf but it is not going to be
installed
Recommends: libreoffice but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.