go back to stable

Help with issues regarding installation of Debian

go back to stable

Postby kmchen » 2019-09-12 06:58

Hi,

I have actually a Debian Strech / Sid installed and would like to go to a stable Buster. Here is my conf:

Code: Select all
root@kmcs:/home/kmc# ll /etc/apt/preferences.d/
total 4
-rw-r--r-- 1 root root 48 avril 28 22:13 testing-avec-sid
root@kmcs:/home/kmc# cat /etc/apt/preferences.d/testing-avec-sid
Package: *
Pin: release n=sid
Pin-Priority: 100
root@kmcs:/home/kmc# cat /etc/apt/sources.list
#

# deb cdrom:[Debian GNU/Linux 8 _stretch_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150908-22:00]/ stretch main

deb http://httpredir.debian.org/debian/ stretch main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free

# stretch-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch-updates main contrib non-free

#backports
deb http://httpredir.debian.org/debian stretch-backports main contrib non-free

#Unstable
deb http://httpredir.debian.org/debian/ sid main contrib non-free


Can I do that safely or do I have to do a complete reinstall ?

Any help apreciated
Développeur WEB
http://www.webologix.com
kmchen
 
Posts: 52
Joined: 2013-04-24 06:29

Re: go back to stable

Postby Dai_trying » 2019-09-12 07:16

While I imagine this might be possible I cannot think of a reason why you would attempt it, considering a full installation can be done easily I would say it would yield a better quicker cleaner result.
Dai_trying
 
Posts: 772
Joined: 2016-01-07 12:25

Re: go back to stable

Postby Hallvor » 2019-09-12 08:16

As an experiment, go for it. I would run tasksel and remove the desktop environment and anything but the core system, and then use apt pinning to attempt a downgrade.

If you want a sensible suggestion, just do a clean install.
Lenovo Thinkpad T440S, Intel Core i7-4600U CPU @ 2.10GHz, 8 GB RAM, 256 GB SSD, Debian Buster (KDE)
User avatar
Hallvor
 
Posts: 942
Joined: 2009-04-16 18:35
Location: Norway

Re: go back to stable

Postby sunrat » 2019-09-12 10:35

Back up all your data first. See my sig. ;)
“ 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: 2826
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: go back to stable

Postby None1975 » 2019-09-14 16:37

I have actually a Debian Strech / Sid installed and would like to go to a stable Buster. Can I do that safely or do I have to do a complete reinstall ?

You can go from stable --> testing --> unstable. But the reverse direction is not "possible". Actually, if you are an expert and if you are willing to spend some time and if you are real careful and if you know what you are doing, then it might be possible to go from unstable to testing and then to stable. The installer scripts are not designed to do that. So in the process, your configuration files might be lost and...
OS: Debian 10.1 Buster / WM: Xmonad
Debian Wiki | DontBreakDebian, My config files in github
User avatar
None1975
 
Posts: 935
Joined: 2015-11-29 18:23
Location: Lithuania, Vilnius

Re: go back to stable

Postby kmchen » 2019-09-16 06:05

Thanks for your messages. I had not receive mail notifications - don't know why, my email is correct - and did not know there had answers.

I finaly unpined Sid and did a normal dist upgrade with success:

Code: Select all
$ cat /etc/apt/preferences.d/testing-avec-sid
Package: *
Pin: release n=sid
Pin-Priority: -1

$ cat /etc/apt/sources.list

# deb cdrom:[Debian GNU/Linux 8 _stretch_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150908-22:00]/ stretch main

deb http://httpredir.debian.org/debian/ stretch main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free

# stretch-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch-updates main contrib non-free

#backports
deb http://httpredir.debian.org/debian stretch-backports main contrib non-free

#Unstable
deb http://httpredir.debian.org/debian/ sid main contrib non-free

deb http://deb.debian.org/debian buster main contrib non-free
deb-src http://deb.debian.org/debian buster main contrib non-free

deb http://security.debian.org/debian-security buster/updates main contrib
deb-src http://security.debian.org/debian-security buster/updates main contrib

$ apt dist-upgrade


Upgrade executed succesfully but I had to reinstall KDE, what I did without problems, and now mysql disappeared too and I can't re-install it.
Following https://linuxize.com/post/how-to-instal ... debian-10/, that I executed as root in spite of sudoer, that install broke and now here is the situation:

Code: Select all
   $ dpkg -l mysql*
    Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
    | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-tr
    |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
    ||/ Nom                             Version          Architecture Description
    +++-===============================-================-============-===================
    un  mysql                           <aucune>         <aucune>     (aucune description
    ii  mysql-apt-config                0.8.13-1         all          Auto configuration
    ii  mysql-client                    5.7.27-1debian10 amd64        MySQL Client meta p
    un  mysql-client-5.0                <aucune>         <aucune>     (aucune description
    un  mysql-client-5.1                <aucune>         <aucune>     (aucune description
    un  mysql-client-5.5                <aucune>         <aucune>     (aucune description
    un  mysql-client-5.6                <aucune>         <aucune>     (aucune description
    un  mysql-client-5.7                <aucune>         <aucune>     (aucune description
    un  mysql-client-core-5.0           <aucune>         <aucune>     (aucune description
    un  mysql-client-core-5.1           <aucune>         <aucune>     (aucune description
    un  mysql-client-core-5.5           <aucune>         <aucune>     (aucune description
    un  mysql-client-core-5.6           <aucune>         <aucune>     (aucune description
    un  mysql-client-core-5.7           <aucune>         <aucune>     (aucune description
    un  mysql-cluster-commercial-client <aucune>         <aucune>     (aucune description
    un  mysql-cluster-commercial-server <aucune>         <aucune>     (aucune description
    un  mysql-cluster-community-client  <aucune>         <aucune>     (aucune description
    un  mysql-cluster-community-server  <aucune>         <aucune>     (aucune description
    un  mysql-commercial-client         <aucune>         <aucune>     (aucune description
    un  mysql-commercial-server         <aucune>         <aucune>     (aucune description
    ii  mysql-common                    5.8+1.0.5        all          MySQL database comm
    un  mysql-common-5.6                <aucune>         <aucune>     (aucune description
    ii  mysql-community-client          5.7.27-1debian10 amd64        MySQL Client
    rc  mysql-community-server          5.7.27-1debian10 amd64        MySQL Server
    un  mysql-server-5.0                <aucune>         <aucune>     (aucune description
    un  mysql-server-5.1                <aucune>         <aucune>     (aucune description
    un  mysql-server-5.5                <aucune>         <aucune>     (aucune description
    un  mysql-server-5.6                <aucune>         <aucune>     (aucune description
    un  mysql-server-5.7                <aucune>         <aucune>     (aucune description
    un  mysql-server-core-5.0           <aucune>         <aucune>     (aucune description
    un  mysql-server-core-5.1           <aucune>         <aucune>     (aucune description
    un  mysql-server-core-5.5           <aucune>         <aucune>     (aucune description
    un  mysql-server-core-5.6           <aucune>         <aucune>     (aucune description
    un  mysql-server-core-5.7           <aucune>         <aucune>     (aucune description
    lines 1-38/38 (END)
    $ sudo apt install mysql-server
...
Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes.
Les paquets suivants contiennent des dépendances non satisfaites :
 default-mysql-server-core : Dépend: mariadb-server-core-10.3 mais ne sera pas installé
 mysql-server : Dépend: mysql-community-server (= 5.7.27-1debian10) mais ne sera pas installé
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
   (ou indiquez une solution).

    root@kmcs:/home/kmc# apt remove mysql-community-client
...
    Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes.
    Les paquets suivants contiennent des dépendances non satisfaites :
     akonadi-backend-mysql : Dépend: default-mysql-client-core mais ne sera pas installé ou
                                      virtual-mysql-client-core
     default-mysql-server-core : Dépend: mariadb-server-core-10.3 mais ne sera pas installé
     mysql-client : Dépend: mysql-community-client (= 5.7.27-1debian10) mais ne sera pas installé
    E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
       (ou indiquez une solution).

    root@kmcs:# apt --fix-broken install
...
    Les paquets supplémentaires suivants seront installés :
      mariadb-server-core-10.3
    Les NOUVEAUX paquets suivants seront installés :
      mariadb-server-core-10.3
    0 mis à jour, 1 nouvellement installés, 0 à enlever et 7 non mis à jour.
...
    Souhaitez-vous continuer ? [O/n]
    (Lecture de la base de données... 312391 fichiers et répertoires déjà installés.)
    Préparation du dépaquetage de .../mariadb-server-core-10.3_1%3a10.3.17-0+deb10u1_amd64.deb ...
    Dépaquetage de mariadb-server-core-10.3 (1:10.3.17-0+deb10u1) ...
    dpkg: erreur de traitement de l'archive /var/cache/apt/archives/mariadb-server-core-10.3_1%3a10.3.17-0+deb10u1_amd64.deb (--unpack) :
     tentative de remplacement de « /usr/share/mysql/charsets/Index.xml », qui appartient aussi au paquet mysql-community-client 5.7.27-1debian10
    dpkg-deb: erreur: coller subprocess was killed by signal (Relais brisé (pipe))
    Des erreurs ont été rencontrées pendant l'exécution :
     /var/cache/apt/archives/mariadb-server-core-10.3_1%3a10.3.17-0+deb10u1_amd64.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)


Any help apreciated
Développeur WEB
http://www.webologix.com
kmchen
 
Posts: 52
Joined: 2013-04-24 06:29

Re: go back to stable

Postby Bloom » 2019-09-16 06:19

You cannot go back to stable (current stable is buster, not stretch) by changing the repositories. They don't go back to earlier versions that way.
The best and fastest way to go back to stable from Sid is to reinstall.
User avatar
Bloom
 
Posts: 193
Joined: 2017-11-11 12:23

Re: go back to stable

Postby kmchen » 2019-09-16 14:46

so I did a reinstall and now not only mysql has to be reinstalled:
mysql
php-fpm
apache
amarok
special usb sound card drivers
...

and all /etc.. 15years of cutomisations

Many of these were workin after upgrade (apache, sounds,.. did not test all but a lot of saved work)
If someone come on that post, do really think about reinstalling a system instead of upgrading...
Développeur WEB
http://www.webologix.com
kmchen
 
Posts: 52
Joined: 2013-04-24 06:29


Return to Installation

Who is online

Users browsing this forum: No registered users and 4 guests

fashionable