Your message dated Sat, 30 Dec 2023 12:32:50 +0100
with message-id <[email protected]>
and subject line Re: Bug#1059698: Please do a maintainer upload to enable 
riscv64 cross-building
has caused the Debian Bug report #1059698,
regarding Please do a maintainer upload to enable riscv64 cross-building
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.)


-- 
1059698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059698
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libkeyutils1
Version: 1.6.3-2+b1

Currently, libkeyutils1 is the last blocker to automatically set up an
essential cross-build environments for riscv64:

$ docker run --rm -it debian:sid
root@d897052b9483:/# dpkg --add-architecture riscv64
root@d897052b9483:/# apt update
...
root@032073e91e5f:/# apt install build-essential libc6-dev:riscv64
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:
 libkrb5-3:riscv64 : Depends: libkeyutils1:riscv64 (>= 1.5.9) but it is not 
installable
E: Unable to correct problems, you have held broken packages.
root@032073e91e5f:/# apt-get install build-essential libc6-dev:riscv64
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:
 libkrb5-3:riscv64 : Depends: libkeyutils1:riscv64 (>= 1.5.9) but it is not 
installable
E: Unable to correct problems, you have held broken packages.


It looks like this is caused by libkeyutils1:amd64 and
libkeyutils1:riscv64 having different versions and, thus, refuse to be
installed at the same time. I've resolved it locally by rebuilding
keyutils for riscv64 using the same version as for the other archs.

Would be great to resolve that by performing a maintainer upload for
this package to sid for all architectures (not sure if
libkeyutils1:riscv64 could be "downgraded" from 1.6.3-2+b1 to 1.6.3-2, I
suspect not).

--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix

Hi Jan,

On Sat, Dec 30, 2023 at 12:16:29PM +0100, Jan Kiszka wrote:
> It looks like this is caused by libkeyutils1:amd64 and
> libkeyutils1:riscv64 having different versions and, thus, refuse to be
> installed at the same time. I've resolved it locally by rebuilding
> keyutils for riscv64 using the same version as for the other archs.

Yes. keyutils was binNMUed on riscv64 and hence is not coinstallable
with anything else.

> Would be great to resolve that by performing a maintainer upload for
> this package to sid for all architectures (not sure if
> libkeyutils1:riscv64 could be "downgraded" from 1.6.3-2+b1 to 1.6.3-2, I
> suspect not).

The way to resolve this is to binNMU everything else to match the +b1 of
riscv64. We're aware riscv64 generally is not version-synced with other
architectures. The release team has decided to not solve this problem
yet as it would cause very many binNMUs. When riscv64 enters testing, it
will be synced, but not now.

I also note that having crossbuild-essential-riscv64 is another missing
prerequisite for cross building. See #1022540

Thus I request more patience here. Sorry for the inconvenience.

Helmut

--- End Message ---

Reply via email to