Dev1 Galaxy Forum / apparmor foisted on, by default?

Re: apparmor foisted on, by default?

dummy@example.com (Altoid) — Fri, 18 Mar 2022 21:13:28 +0000

Hello:

rbit wrote:

An alternate option for this particular case ...

Hmm ...
No thanks.

I'd prefer that any and all recommends be something I get to consider installing to then decide and not something that is installed because some Debian packager though it was a good idea.

That is how the Linux bloat we have today started ...

I think that a system-wide block on recommends is a great idea.
Of course, YMMV.

Thank you for your input.

Best,

Re: apparmor foisted on, by default?

dummy@example.com (rbit) — Fri, 18 Mar 2022 20:34:27 +0000

An alternate option for this particular case (apparmor) would be to create a file, e.g. /etc/apt/preferences.d/noapparmor
Contents:

Package: apparmor*
Pin: release n=beowulf
Pin-Priority: -1

Change the release name if you're not using beowulf.

Re: apparmor foisted on, by default?

dummy@example.com (Altoid) — Sat, 12 Mar 2022 22:58:05 +0000

Hello:

fsmithred wrote:

... this could be avoided in packaging, but I doubt you can change the debian devs ...

On this or most anything, methinks.
I fear that they cannot help it.

They've all been inbued with the same dumb-down KoolAid.

fsmithred wrote:

... nobody around here is going to fork the kernel.

Ahh ...
If forking is required, I cannot but agree with you.

fsmithred wrote:

You can avoid that and a lot of other cruft with this:
cat /etc/apt/apt.conf.d/00norecommends APT::Install-Recommends "no";

Right ...
Maybe add this as a commentary to the Release Notes most no one reads? 8^/

eg:
If you do not want the apparmor crap foisted on you without your knowledge when upgrading etc., etc., ...

NB:
For some reason it didn't work from the cmd line as root.
So I just created the file and then edited it.

fsmithred wrote:

... if adding '--no-install-recommends' will work with 'apt upgrade'.

Probably.

I'd also have to change the default /etc/apt/apt.conf.d/99synaptic to false.

I really find it quite tiresome/annoying to have to be on alert for this everytime I upgrade the kernel.
It should not be so.

But then, here we are.

Thanks a lot for your input.
I'll follow your suggestion to avoid this and all recommends in a system-wide manner.

A sort of 'Kill the dog and get rid of the rabies' solution.
Well done. 8^D

Best,

Re: apparmor foisted on, by default?

dummy@example.com (fsmithred) — Sat, 12 Mar 2022 21:59:04 +0000

Yes, this could be avoided in packaging, but I doubt you can change the debian devs on this. And nobody around here is going to fork the kernel. (that's my prediction)

You can avoid that and a lot of other cruft with this:

cat /etc/apt/apt.conf.d/00norecommends 
APT::Install-Recommends "no";

I don't know if adding '--no-install-recommends' will work with 'apt upgrade'. If so, that's another way to avoid it.

apparmor foisted on, by default?

dummy@example.com (Altoid) — Sat, 12 Mar 2022 21:49:23 +0000

Hello:

A question to something that has baffled me for the longest while ...

Why (in #$%&@'s name) does upgrading the kernel require that apparmor be installed?
Just whose bright idea was this?

And more important yet: is it in line with Devuan policies?

Start-Date: 2022-03-12  09:34:39
Commandline: apt upgrade
Install:
linux-headers-4.19.0-19-common:amd64 (4.19.232-1, automatic)
linux-headers-4.19.0-19-amd64:amd64 (4.19.232-1, automatic)
linux-image-4.19.0-19-amd64:amd64 (4.19.232-1, automatic)
apparmor:amd64 (2.13.2-10, automatic)   <-------------------------  why?
--- snip ---

Can't this be avoided when packaging for Devuan by removing it from the recommends list?

Just asking, because choice and all that.

Best,