[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#969468: marked as done (lintian: Can't opendir(/dev/.lxd-mounts): Permission denied)

Your message dated Thu, 3 Sep 2020 09:55:26 -0700
with message-id <CAFHYt56G7omeWVkFaTwOwEnjezJ8uiAXKDZuJi9tMcVGfT2ptw@mail.gmail.com>
and subject line Re: lintian: Can't opendir(/dev/.lxd-mounts): Permission denied
has caused the Debian Bug report #969468,
regarding lintian: Can't opendir(/dev/.lxd-mounts): Permission denied
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 owner@bugs.debian.org
immediately.)


-- 
969468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969468
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.92.0
Severity: important


lintian 2.92.0 is broken inside a lxd container:

$ lxc exec debian -- sudo -iu jak env -C $PWD lintian apt_2.1.1.dsc 
Can't opendir(/dev/.lxd-mounts): Permission denied
 at /usr/share/perl/5.30/File/Find.pm line 387.
        File::Find::_find_dir(HASH(0x55f401c79d48), "/dev", 8) called at /usr/share/perl/5.30/File/Find.pm line 236
        File::Find::_find_opt(HASH(0x55f401c79d48), "/dev") called at /usr/share/perl/5.30/File/Find.pm line 760
        File::Find::find(HASH(0x55f401c79d48), "/dev") called at /usr/lib/x86_64-linux-gnu/perl5/5.30/Proc/ProcessTable.pm line 162
        Proc::ProcessTable::_get_tty_list(Proc::ProcessTable=HASH(0x55f401c79cd0)) called at /usr/lib/x86_64-linux-gnu/perl5/5.30/Proc/ProcessTable.pm line 136
        Proc::ProcessTable::initialize(Proc::ProcessTable=HASH(0x55f401c79cd0)) called at /usr/lib/x86_64-linux-gnu/perl5/5.30/Proc/ProcessTable.pm line 79
        Proc::ProcessTable::new("Proc::ProcessTable") called at /usr/share/lintian/bin/../lib/Lintian/Pool.pm line 250
        Lintian::Pool::process(Lintian::Pool=HASH(0x55f3fb8493c8), Lintian::Profile=HASH(0x55f3fd1cfbc0), SCALAR(0x55f3fd229fb8), HASH(0x55f3fd21c510), GLOB(0x55f3fabd0560), Lintian::Output::EWI=HASH(0x55f3fbca3388)) called at /usr/bin/lintian line 761

This makes it fail its autopkgtest test suite on Ubuntu armhf:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/l/lintian/20200829_110043_f9a6a@/log.gz

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--- End Message ---
--- Begin Message --- 
Hi,

> lintian 2.92.0 is broken inside a lxd container:

In a technical sense, it may be a problem with your container. Lintian
tries to read the process table, which apparently does not work in lxd
unless modifications are made. At the same time, the autopkgtest jobs
also fail in Debian CI, which is why the issue was addressed in this
commit, still unreleased:

https://salsa.debian.org/lintian/lintian/-/commit/451dc2169655137a8e7c5e9dfc459f31db7525c8

The issue was resolved with a commit in Lintian because to comply with
the autopkgtest specification Lintian would have to specify the
restriction 'isolation-machine', which is not supported in Debian CI.
In that sense, your lxd container cannot be expected to work, either.

For comparison, none of the autopkgtest jobs on Salsa CI have the
issue. You may wish to check out whatever they did. I think they use
lxd (and I believe I saw the relevant code a few days ago) but cannot
find it now.

Thanks for reporting this issue, and thanks for making Lintian better
for everyone!

Kind regards
Felix Lechner

--- End Message ---
Reply to: