Re: Backports and upgrade to buster
- Date: Fri, 24 May 2019 12:33:21 -0400
- From: Cindy Sue Causey <butterflybytes@xxxxxxxxx>
- Subject: Re: Backports and upgrade to buster
And hi! :)
On 5/23/19, Michael Lange <klappnase@xxxxxxxxxx> wrote:
> On Thu, 23 May 2019 11:44:14 +0300
> Georgios <gpdsbe+debian@xxxxxxxxxxx> wrote:
>> Hi there!
>> I'm thinking installing debian on a new laptop. The problem is that the
>> current version is stretch that comes with an old kernel that doesn't
>> support my wifi card.
>> I was thinking about using backports to install the latest kernel.
>> I have the following questions.
>> When I install stable and use a kernel from backport when you install it
>> you upgrade a couple of packages like libglib, firmware-linux-free etc
>> When the buster is released what happens when i try to upgrade the
>> system from stretch to buster?
>> Do I have to remove backports from sources.list?
>> What happens to the packages that were upgraded from backports? Are they
>> replaced by the new stable packages?
> before starting an upgrade from stretch to buster (or any oldstable to
> stable) you should remove backports from the sources.list at any rate. In
> my own personal experience the best bet is to remove anything except the
> deb http://ftp.de.debian.org/debian/ stretch main contrib non-free
> from the sources.list prior to the upgrade. Usually this gives you a
> smooth upgrade procedure. Packages from backports (or multimedia or
> whatever one may use in addition to plain debian) will be replaced by the
> new stable packages if these are newer. If you need (or just want)
> anything from backports (or multimedia or whatever) just re-install these
> packages after the upgrade.
Because of the speed of dialup, I go the extra step of backing up
/var/lib/apt/lists, too, just in case that directory's contents
somehow get zapped in the process. Afterward, I run a quick "diff"
comparison to see if anything notable needs put back in place.
Most times nothing needs changed after previously favored
/etc/apt/sources.list lines are put back in place. If something does
need replaced, it's most likely due to a mistake on my part.
Backing up that lists directory is just a precautionary step I have to
take relative to my usage circumstances. It only takes 2 seconds to
both create and then later delete. In return, the step can save (and
HAS SAVED) many HOURS of wear and tear on my computer, my Internet
service provider's servers, AND MOST IMPORTANTLY (*to me*), whatever
VOLUNTEER Debian repository host(s) might be affected each time.
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *