Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
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 ?
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.
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.
[HowTo] Install and configure Debian bookworm Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
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...
$ 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:
$ 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)
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.
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...