Your message dated Wed, 24 Apr 2024 19:18:27 +0200
with message-id <87zftid6ho....@daath.pimeys.fr>
and subject line Re: [pkg-lxc-devel] Bug#934480: lxc: please consider adding
Multi-Arch marking
has caused the Debian Bug report #934480,
regarding lxc: please consider adding Multi-Arch marking
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 ow...@bugs.debian.org
immediately.)
--
934480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxc
Version: 1:2.0.7-2+deb9u2
Severity: wishlist
Dear Maintainer,
Please add Multi-Arch marking to lxc binary packages:
liblxc1, libpam-cgfs[*] can be marked `Multi-Arch: same` without changes;
liblxc-dev probably can be marked `M-A: same` [not sure about /usr/include/*,
needs verification];
lxc likely can be marked `Multi-Arch: foreign`, as it provides
arch-independent services only (CLI/daemons) [needs verification].
(Note [*]: in multi-arch installations, if any foreign-arch tools uses
pam [e.g. sshd:amd64 on :i386 system], it is required to install same set
of libpam-* modules in all enabled arches)
-- System Information:
Debian Release: 9.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldstable-debug'), (500, 'oldstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 4.9.0-10-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R),
LANGUAGE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lxc depends on:
ii init-system-helpers 1.56~bpo9+1
ii libapparmor1 2.11.0-3+deb9u2
ii libc6 2.24-11+deb9u4
ii libcap2 1:2.25-1
ii libgnutls30 3.5.8-5+deb9u4
ii liblxc1 1:2.0.7-2+deb9u2
ii libseccomp2 2.3.1-2.1+deb9u1
ii libselinux1 2.6-3+b3
ii lsb-base 9.20161125
ii python3 3.5.3-1
ii python3-lxc 1:2.0.7-2+deb9u2
Versions of packages lxc recommends:
ii bridge-utils 1.5-13+deb9u1
ii debootstrap 1.0.89
ii dirmngr 2.2.17-3~bpo9+1
ii dnsmasq-base 2.76-5+deb9u2
ii gnupg 2.2.17-3~bpo9+1
ii iptables 1.6.0+snapshot20161117-6
ii libpam-cgfs 2.0.8-1~bpo9+2~local1
ii lxcfs 2.0.8-1~bpo9+2~local1
ii openssl 1.1.0k-1~deb9u1
ii rsync 3.1.2-1+deb9u2
ii uidmap 1:4.4-4.1
Versions of packages lxc suggests:
pn apparmor <none>
pn btrfs-tools <none>
ii lvm2 2.02.168-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 +wontfix
Hi,
Pierre-Elliott Bécue <p...@debian.org> wrote on 19/04/2020 at 00:09:16+0200:
> Le dimanche 11 août 2019 à 15:23:39+0300, Yuriy M. Kaminskiy a écrit :
>> Package: lxc
>> Version: 1:2.0.7-2+deb9u2
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>> Please add Multi-Arch marking to lxc binary packages:
>>
>> liblxc1, libpam-cgfs[*] can be marked `Multi-Arch: same` without changes;
>>
>> liblxc-dev probably can be marked `M-A: same` [not sure about /usr/include/*,
>> needs verification];
>>
>> lxc likely can be marked `Multi-Arch: foreign`, as it provides
>> arch-independent services only (CLI/daemons) [needs verification].
>>
>> (Note [*]: in multi-arch installations, if any foreign-arch tools uses
>> pam [e.g. sshd:amd64 on :i386 system], it is required to install same set
>> of libpam-* modules in all enabled arches)
>
> Hi,
>
> Done for both libpam-cgfs and liblxc1.
>
> For the two other packages, I don't have time to make the verifications,
> but I think you're right. If you have some time to check or get
> confirmations, I'm eager to do the changes.
>
> Cheers!
Not being keen on testing multi-arch stuff in the dark, I'm closing this.
Feel free to reopen it if you have a proper procedure I could use to
determine what tags I can use for bin:lxc and bin:lxc-dev.
Bests,
--
PEB
signature.asc
Description: PGP signature
--- End Message ---
