Why we should avoid Debian APT Pinning
Debian developers would literally hate this.
Okay for end users and sys admins, but not a solution for a Debian derivative.
Example where Kicksecure™ backports APT pinning instructions broke users systems:
user documentation template: Template:Apt-Pinning archived: https://www.kicksecure.com/w/index.php?title=Special:Undelete&target=Template%3AApt-Pinning×tamp=20170721231624
backports by default
- Had resulted to breakage in Qubes. See: https://github.com/QubesOS/qubes-issues/issues/4443
- Debian bug linux-image-amd64 vs linux-headers-amd64 Debian buster-backports version mismatch bpo.2 vs bpo.3 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.
This idea came up originally in context of: https://web.archive.org/web/20220322174537/https://github.com/Whonix/Whonix/issues/60