You are not logged in.
Pages: 1
Hey guys,
I was wondering if anyone thinks it'd be harmful to /always/ favor installing a backported package if it's available. I currently use Stretch, and plan to continue using Stretch, but I'd be curious to build an operating system of Stretch backports whenever possible. Could be fun.
My second question is, how would one go about doing this? Pin stretch-backports higher? I also have bunsen helium-dev backport repositories, would I do the same here?
Offline
Answering my own question a bit...
I made sure stretch backports were enabled in both debian repos as well as bunsenlabs repos. I then created a file, /etc/apt/preferences.d/backports
Package: *
Pin: release a=stretch-backports
Pin-Priority: 800
I am currently doing and apt-get upgrade and then will do an apt-get dist-upgrade. We'll see what breaks, just for the heck of it.
Offline
I hope it works out for you.
Backports are not tested as thoroughly as regular packages, and it's generally not recommended to install them just for the fun of it. Safer to leave it till you specifically need some improvement that a certain backported package offers, and then install that one only.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Yep, acknowledged. This is just for fun in a VM, so it's not something I need to function properly, I am just a bit curious.
Offline
You asked:
I was wondering if anyone thinks it'd be harmful to /always/ favor installing a backported package if it's available.
Answer was yes, maybe.
But if it's a trial VM, then sure, go for it.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
This is a very silly idea.
Just use sid instead, I have always found it to be surprisingly reliable (certainly more so than testing).
Offline
Pages: 1