Dev/APT Pinning
< Dev
Jump to navigation
Jump to search
This idea came up originally in context of: https://github.com/Kicksecure/Kicksecure/issues/60
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?
Answers:
- https://lists.debian.org/debian-derivatives/2013/08/msg00005.html
- https://lists.debian.org/debian-derivatives/2013/08/msg00006.html
Example where Kicksecure ™ backports APT pinning instructions broke users systems:
https://forums.whonix.org/t/templates-incorrectly-think-theyre-not-connected-to-a-whonix-gateway/2258/25
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
- 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.
Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.