Description
Description
Event Timeline
Comment Actions
Can you share the command you used? Also, what is in your /etc/apt/sources.list (or /etc/apt/sources.list.d/* ?
Comment Actions
apt dist-upgrade
sources.list content
# # deb cdrom:[Debian GNU/Linux none _Green_ - Official Snapshot amd64 LIVE/INSTALL Binary 20180120-02:05]/ green main # deb cdrom:[Debian GNU/Linux none _Green_ - Official Snapshot amd64 LIVE/INSTALL Binary 20180120-02:05]/ green main deb http://repo.pureos.net/pureos/ green main deb http://repo.puri.sm/pureos/ green main deb-src http://repo.puri.sm/pureos/ green main #Added by software-properties deb-src http://repo.pureos.net/pureos/ green main
sources.list.d list
. ..
Comment Actions
This is not so surprising for a 'dist-upgrade'. I don't know if you want to do the dist-upgrade or not, perhaps you need those important packages and don't want them removed, but if you like you can try just doing a regular apt upgrade that will not be as invasive.
Comment Actions
Okay, thx. I tried it because I did not want retainet packages. Then should I wait theses packages can be upgraded without theses conflicts?
root@echedey-500-500ns:~# apt upgrade Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Calculando la actualización... Hecho Los siguientes paquetes se han retenido: gir1.2-rb-3.0 liblxc1 libpython3-dbg libpython3-dev libpython3-stdlib librhythmbox-core10 lxc python3 python3-dbg python3-dev python3-lxc python3-minimal python3-openshot rhythmbox rhythmbox-plugins 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 15 no actualizados.
Comment Actions
Yes, that would be my advice. You can do a dist-upgrade anyway and try and fix your system if it gets in a misconfigured state, but that can be time consuming and difficult. Usually with ten days or so that type of package conflict goes away as new software and bug fixes come into the repos.