Re: Bug#981442: apparmor: Please do not install by default or depend on python3
Hello, intrigeri, le lun. 01 févr. 2021 09:16:23 +0100, a ecrit: > Samuel Thibault (2021-01-31): > > As of Debian bullseye alpha3, apparmor is getting installed by default > > even in the base system, > > To be clear, in this context "base system" is d-i terminology, right? Yes. That's when one selects no task, so the absolute minimum that gets installed. > > bringing with it python3 and thus 30MB of > > various stuff that didn't used to get installed in the past, which I do > > not think we want. > > Could you please confirm whether "in the past" means "in Stretch and > older" here, or something else? I'm surprised here. It does seem that Stretch, even as 10.0, does install apparmor and thus python, indeed. But I check for the install size before each Debian release, and did not notice that. Perhaps the apparmor recommendation appeared late in the Stretch process. I'm not sure whether debian-boot was aware that python ended up getting installed. > > or avoid making it hardly depend on python3? > > The only reason why apparmor "Depends: python3" in current testing/sid > is that /usr/sbin/aa-status is written in Python. > > Upstream commit 8f9046b1b179190d0003ae1beacf460ee93c5090, included in > upstream 3.0.0 release, and thus in Debian experimental already, > ported that program to C, which should allow dropping the dependency > on python3. I did not check how hard it would be to backport > this commit. That would be great to backport! Samuel
Re: Bug#981442: apparmor: Please do not install by default or depend on python3
Samuel Thibault, le dim. 31 janv. 2021 13:19:28 +0100, a ecrit: > Cc-ing the linux package maintainers since that's what recommends > apparmor, thus pulling the 30MB. Actually, that not only pulls python3 but also perl, libicu, and in the end with dependencies, that amounts to 114MB. Samuel > Samuel Thibault, le dim. 31 janv. 2021 12:10:43 +0100, a ecrit: > > Package: apparmor > > Version: 2.13.6-7 > > Severity: important > > > > Hello, > > > > As of Debian bullseye alpha3, apparmor is getting installed by default > > even in the base system, bringing with it python3 and thus 30MB of > > various stuff that didn't used to get installed in the past, which I do > > not think we want. Could you have a look at not installing apparmor by > > default, or avoid making it hardly depend on python3? > > > > Samuel > > > > -- System Information: > > Debian Release: bullseye/sid > > APT prefers testing > > APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, > > 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), > > (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), > > (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, > > 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) > > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE > > not set > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages apparmor depends on: > > ii cdebconf [debconf-2.0] 0.256 > > ii debconf [debconf-2.0] 1.5.74 > > ii libc6 2.31-9 > > ii lsb-base11.1.0 > > ii python3 3.9.1-1 > > > > apparmor recommends no packages. > > > > Versions of packages apparmor suggests: > > pn apparmor-profiles-extra > > pn apparmor-utils > > > > -- debconf information excluded
Re: Bug#981442: apparmor: Please do not install by default or depend on python3
Hello, Cc-ing the linux package maintainers since that's what recommends apparmor, thus pulling the 30MB. Also Cc-ing d-b for information. Samuel Samuel Thibault, le dim. 31 janv. 2021 12:10:43 +0100, a ecrit: > Package: apparmor > Version: 2.13.6-7 > Severity: important > > Hello, > > As of Debian bullseye alpha3, apparmor is getting installed by default > even in the base system, bringing with it python3 and thus 30MB of > various stuff that didn't used to get installed in the past, which I do > not think we want. Could you have a look at not installing apparmor by > default, or avoid making it hardly depend on python3? > > Samuel > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, > 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), > (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), > (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, > 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages apparmor depends on: > ii cdebconf [debconf-2.0] 0.256 > ii debconf [debconf-2.0] 1.5.74 > ii libc6 2.31-9 > ii lsb-base11.1.0 > ii python3 3.9.1-1 > > apparmor recommends no packages. > > Versions of packages apparmor suggests: > pn apparmor-profiles-extra > pn apparmor-utils > > -- debconf information excluded