Should bw mark packages as “explicitly installed”?

[vain]

Scenario:

• You install package foo.
• foo has a dependency on bar, so that one gets installed as well.
• bar is a bw item, too, and is supposed to be installed.
• You do a system upgrade or something else that removes bar from the list of dependencies from foo.
• bw sees both packages as installed and is happy.
• Something like apt autoremove might pick up bar as an orphaned package and remove it.

Sounds like an academic example, but we believe this just happened to us.

Should bw mark all packages as “explicitly installed” to prevent tools like apt autoremove from removing such packages?

[trehn]

Yes.

[MaZderMind]

That might explain why a new node has it's python3-requests removed after a while (until the next bw apply which re-installs it manually). I think that just happened on a brand new htz-Server.