This idea came up originally in context of: https://github.com/Whonix/Whonix/issues/60 ^[archive]

Summary[edit]

Debian developers would literally hate this.

Okay for end users and sys admins, but not a solution for a Debian derivative.

More Details[edit]

Question: Can a package pull a another package from another repository to be added? ^[archive]

Answers:

• https://lists.debian.org/debian-derivatives/2013/08/msg00005.html ^[archive]
• https://lists.debian.org/debian-derivatives/2013/08/msg00006.html ^[archive]

Example where Whonix ™ backports APT pinning instructions broke users systems:

https://forums.whonix.org/t/templates-incorrectly-think-theyre-not-connected-to-a-whonix-gateway/2258/25 ^[archive]

Misc[edit]

• user documentation template: Template:Apt-Pinning

backports by default[edit]

• Had resulted to breakage in Qubes. See: https://github.com/QubesOS/qubes-issues/issues/4443 ^[archive]
• Debian bug linux-image-amd64 vs linux-headers-amd64 Debian buster-backports version mismatch bpo.2 vs bpo.3 ^[archive] shows that just enabling backports repository might lead to issues. In this example, breaking all kernel modules due to kernel image vs kernel headers version mismatch from backports packages.debian.org.

---

---

	100px
Fosshost	About Advertisements

---

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier | Whonix ™ Wiki

---

Follow:

Support:

Donate:

Priority Support | Investors | Professional Support

Whonix ™ | © ENCRYPTED SUPPORT LP | Freedom Software / Open Source (Why?)

The personal opinions of moderators or contributors to the Whonix ™ project do not represent the project as a whole.