Remove Jessie from APT after Buster update

New to Debian (Or Linux in general)? Ask your questions here!

Remove Jessie from APT after Buster update

Postby GonzagueGB » 2020-08-13 23:56

Hi everyone,

First question here and Debian total noob. Yet I have a few VPS with running WP install and I need to upgrade from Jessie to Buster.
I tried to upgrade from 8, to 9 and then to 10, everything went smoothly, the test VPS did not burn into flames and the two WP installs on it are running just fine.

However, and despite changing the sources.list each time I am using the command APT for updates I have jessie still popping up. as such

Hit http://deb.debian.org buster InRelease
Get:1 http://deb.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org buster-updates InRelease [51.9 kB]
Get:3 https://packages.sury.org jessie InRelease
Ign https://packages.sury.org jessie InRelease
Get:4 https://packages.sury.org jessie Release.gpg
Ign https://packages.sury.org jessie Release.gpg
Get:5 https://packages.sury.org jessie Release
Ign https://packages.sury.org jessie Release


When I am doing a search in APT I have the following mention of Jessie

root@XXXX:~# cd /etc/apt
root@XXXX:/etc/apt# grep -rni jessie
apt.conf.d/50unattended-upgrades:13:// n,codename (eg, "jessie", "jessie-updates")
apt.conf.d/50unattended-upgrades:22:// ${distro_codename} Installed codename (eg, "jessie")
apt.conf.d/50unattended-upgrades:27:// "o=Debian,n=jessie";
apt.conf.d/50unattended-upgrades:28:// "o=Debian,n=jessie-updates";
apt.conf.d/50unattended-upgrades:29:// "o=Debian,n=jessie-proposed-updates";
apt.conf.d/50unattended-upgrades:30:// "o=Debian,n=jessie,l=Debian-Security";
Binary file trusted.gpg.d/debian-archive-jessie-security-automatic.gpg matches
Binary file trusted.gpg.d/debian-archive-jessie-stable.gpg matches
Binary file trusted.gpg.d/debian-archive-jessie-automatic.gpg matches
sources.list.d/php7.3.list:1:deb https://packages.sury.org/php/ jessie main
root@XXXX:/etc/apt#


What should I do to resolve this and get ride of Jessie when I want to update/upgrade.

Thank you.

Note: I am a total beginner to please keep it any answer noob-friendly ;-)
GonzagueGB
 
Posts: 2
Joined: 2020-08-13 23:43

Re: Remove Jessie from APT after Buster update

Postby sunrat » 2020-08-14 02:10

GonzagueGB wrote:When I am doing a search in APT I have the following mention of Jessie...

...
sources.list.d/php7.3.list:1:deb https://packages.sury.org/php/ jessie main


Looks like you installed php7.3 from that repo, sources file is in /etc/sources.list.d/ directory. If you go to https://packages.sury.org/php/dists/ you will see the jessie repo is not there any more. You should change that source to buster but maybe you have to upgrade php through stretch first. Not sure about that. Either way you may have to import a new release key for the new repo. php7.3 is in buster repo anyway, there's probably no need to keep that 3rd party sury repo at all.
Upgrading release versions is a major undertaking and you should read, understand, and follow the Release Notes -
https://www.debian.org/releases/stable/releasenotes
https://www.debian.org/releases/stretch/releasenotes
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 3181
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Remove Jessie from APT after Buster update

Postby stevepusser » 2020-08-14 06:17

A newbie-friendly way to find these mystery entries is to install inxi and run "inxi -r" in a terminal. It will tell where the list file lives that's creating that channel.
MX Linux packager and developer
User avatar
stevepusser
 
Posts: 11981
Joined: 2009-10-06 05:53

Re: Remove Jessie from APT after Buster update

Postby arid » 2020-08-14 19:20

stevepusser wrote:A newbie-friendly way to find these mystery entries is to install inxi and run "inxi -r" in a terminal. It will tell where the list file lives that's creating that channel.


Excellent! Some of you are getting the message of ease of use available in Debian.

Now you go into synaptic, surely you use it as it's a standard install in that ancient stable and there you can easily edit your sources.

Here are mine to ponder:

Code: Select all
/etc/apt/sources.list
  1: deb http://deb.debian.org/debian/ unstable main contrib non-free
  2: deb https://packages.siduction.org/fixes/ unstable main contrib non-free
  3: deb http://packages.siduction.org/extra/ unstable non-free contrib main
  4: deb http://packages.siduction.org/extra/ experimental main
  5: deb http://deb.debian.org/debian/ experimental main contrib non-free



Ahhhhhhhhh, can't get none of that there ancient stable stuff here. :mrgreen:
There's no drama in my sid......
arid
 
Posts: 94
Joined: 2014-05-08 18:40
Location: Aridzona

Re: Remove Jessie from APT after Buster update

Postby sunrat » 2020-08-14 21:03

arid wrote:Now you go into synaptic, surely you use it as it's a standard install in that ancient stable and there you can easily edit your sources.

Here are mine to ponder:

Code: Select all
/etc/apt/sources.list
  1: deb http://deb.debian.org/debian/ unstable main contrib non-free
  2: deb https://packages.siduction.org/fixes/ unstable main contrib non-free
  3: deb http://packages.siduction.org/extra/ unstable non-free contrib main
  4: deb http://packages.siduction.org/extra/ experimental main
  5: deb http://deb.debian.org/debian/ experimental main contrib non-free



Ahhhhhhhhh, can't get none of that there ancient stable stuff here. :mrgreen:


That's just about the worst sources you could possibly suggest for a "Debian total noob"
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 3181
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Remove Jessie from APT after Buster update

Postby GonzagueGB » 2020-08-16 01:11

Thanks everyone for your comments.

I spent some times to remove every notion of Jessie in these files and replace it by Buster, it worked... However, I was a bit cocky and try to push my luck and XXX it up. The problem, for me is the transition from MySQL to mariaDB.

I came to the conclusion, that it would be easier to get a new VPS and install everything from scratch (OVH is stuck with Debian 8 in their Wordpress offering) and migrate. I will try that soon. Hope I won't have to bother you again ;-)
GonzagueGB
 
Posts: 2
Joined: 2020-08-13 23:43


Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable