Le jeudi 07 février 2019 à 20:29:45+0100, Andreas Beckmann a écrit : > Package: lxc,lava-dev > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + lava-dispatcher lava-server > Control: found -1 lxc/1:3.1.0+really3.0.3-2 > Control: found -1 lava/2019.01-3 > Control: found -1 lava/2019.01-4 > > Hi, > > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > > This was observed during a test of lava-dev with --install-recommends enabled. > > From the attached log (scroll to the bottom...): > > Setting up lxc (1:3.1.0+really3.0.3-2) ... > Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not > found > Cache read/write disabled: interface file missing. (Kernel needs AppArmor > 2.4 compatibility patch.) > Warning: unable to find a suitable fs in /proc/mounts, is it mounted? > Use --subdomainfs to override. > dpkg: error processing package lxc (--configure): > installed lxc package post-installation script subprocess returned error > exit status 1 > > I can reproduce this in both amd64 and i386 chroots. > I cannot reproduce it with lxc alone (regardles of whether > --install-recommends is enabled) > I cannot reproduce it with lava-dev without --install-recommends > > > cheers,
Hi, I'm not sure that there is something we can do regarding lxc. Am I wrong? Best regards, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
signature.asc
Description: PGP signature
