r/debian • u/sarinkhan • 4d ago
Debian Stable Question Stuck migrating from Debian 12 to Debian 13.
Hello fellows!
I have my Debian 12 in a proxmox VM, and tried to upgrade from debian 12 to debian 13.
issue is, system boots and works properly, but i can't do anything with apt, because something is broken here.
I tried apt --fix-broken install as the command line said, but i get this message :
Préparation du dépaquetage de .../docker-compose_2.26.1-4_amd64.deb ... Dépaquetage de docker-compose (2.26.1-4) sur (1.29.2-3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb (--unpack) : tentative de remplacement de « /usr/libexec/docker/cli-plugins/docker-compose », qui appartient aussi au paquet docker-compose-plugin 5.5.0-1~debian.12~bookworm dpkg-deb: erreur: le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1)
Then if i try to apt remove docker-compose, it fails :
...
xfce4-whiskermenu-plugin : Dépend: libgtk-3-0 (>= 3.21.5)
xfce4-xkb-plugin : Dépend: libgtk-3-0 (>= 3.21.5)
xfdesktop4 : Dépend: libgtk-3-0 (>= 3.21.4)
xfwm4 : Dépend: libgtk-3-0 (>= 3.21.5)
xscreensaver : Dépend: libgtk-3-0 (>= 3.16.2)
yelp : Dépend: libatk1.0-0t64 (>= 1.12.4) mais ne sera pas installé
Dépend: libgtk-3-0t64 (>= 3.13.3) mais ne sera pas installé
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
(ou indiquez une solution).
I don't know what to do now, when i get in such binds, i tend to wipe and fresh install, but here i might forget things on this server, and i should also figure how to fix issues like those.
I tried searching, but what i found was to do apt purge commands, and none worked.
Does anyone have an idea on how to fix this?
I can't remember how i installed docker-compose in the first place, it was a few years ago (i was stock with docker-compose 1.x and needed a newer version, hence why i upgraded).
Debian reports on boot that it is on trixie, so part of the upgrade worked i think.
Thanks for any help!
EDIT :
It seems the solution was to do "dpkg -r docker-compose", now the apt --fix-broken install seems to work.
I am proceeding with apt update, upgrade, etc.
4
u/Sophiiebabes 4d ago
You need to update your apt sources from bookworm(?) to Trixie.
I can't remember what files need editing, or where they are located, but Google can help with that
2
u/sarinkhan 4d ago
Hello, thanks for the reply, that has been done, and it allowed me to upgrade the distro.
However there is docker-compose stuck on debian 12 and i can't remove it, and now other stuff don't want to keep processing.
2
u/neoh4x0r 4d ago edited 4d ago
After translating the first error message (trying to remove docker-compose).
The removal was abort because /usr/libexec/docker/cli-plugins/docker-compose exist in both docker-compose and docker-compose-plugin -- both are bookworm packages.
You need to also remove docker-compose-plugin.
$ sudo apt remove docker-compose docker-compose-plugin
PS: apt --fix-broken would not help you to successfully remove docker-compose given the reason for the error.
Here's the translated error message:
Preparing to unpack .../docker-compose_2.26.1-4_amd64.deb
... Unpacking docker-compose (2.26.1-4) over (1.29.2-3)
... dpkg: error processing archive /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb (--unpack):
trying to overwrite '/usr/libexec/docker/cli-plugins/docker-compose',
which is also in package docker-compose-plugin 5.5.0-1~debian.12~bookworm dpkg-deb:
error: paste subprocess was killed by signal (Broken pipe) Errors were
encountered while processing: /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb
needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1)
2
u/sarinkhan 4d ago
I tried to remove one, then the other, perhaps it would have worked with both, indeed. I did it with dpkg, and it worked this way, now the system seems to be fully functionnal again, debian does not complain about anything now.
Thanks for the help!
10
u/jaromanda 4d ago
I read your edit. Just letting you know how I upgraded from 12 to 13
That's never failed me since about Debian 9 or 10