Re: How did I get into dependency hell and how do I get out?
Ottavio Caruso wrote:
> Hi,
>
>
> $ uname -a
> Linux e130 5.18.0-0.bpo.1-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 5.18.2-1~bpo11+1 (2022-06-14) x86_64 GNU/Linux
> $ cat /etc/debian_version
> 11.2
Your kernel is from backports, so you have at least some
backports installed. What else is in your
/etc/apt/sources.list
/etc/apt/sources.list.d/*
> The following packages have unmet dependencies:
> libglib2.0-dev : Depends: libglib2.0-0 (= 2.66.8-1) but 2.72.1-1 is to be
> installed
> Depends: libglib2.0-bin (= 2.66.8-1)
> Depends: libglib2.0-dev-bin (= 2.66.8-1)
> E: Unable to correct problems, you have held broken packages.
>
>
>
> $ apt-cache policy libglib2.0-0
> libglib2.0-0:
> Installed: 2.72.1-1
> Candidate: 2.72.1-1
> Version table:
> *** 2.72.1-1 100
> 100 /var/lib/dpkg/status
> 2.66.8-1 500
> 500 https://deb.debian.org/debian bullseye/main amd64 Packages
That's a version from later-than-bullseye.
>
> $ apt-get -s -f install libglib2.0-0=2.66.8-1
> NOTE: This is only a simulation!
> apt-get needs root privileges for real execution.
> Keep also in mind that locking is deactivated,
> so don't depend on the relevance to the real current situation!
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
Ignore this unless you do autoremove...
> The following packages will be REMOVED:
> caja caja-admin caja-rename caja-seahorse debian-system-adjustments
> gstreamer1.0-packagekit gvfs-bin libglib2.0-bin mate-control-center
> mate-desktop-environment mate-desktop-environment-core
> mate-desktop-environment-extra mate-desktop-environment-extras
> mate-dock-applet mate-menu mate-notification-daemon mate-power-manager
> packagekit packagekit-tools
> The following NEW packages will be installed:
> notification-daemon
> The following packages will be DOWNGRADED:
> libglib2.0-0
> 0 upgraded, 1 newly installed, 1 downgraded, 21 to remove and 55 not
These are things that I suspect are also from beyond bullseye.
> Oops! How can I downgrade libglib2.0-0 without nuking most of the system?
Remove extra repos from your sources; pin backports to on-demand
only; apt update; downgrade libglib2.0-0, reinstall the packages from the
"will be REMOVED" list.
That will probably clear up your "no longer required" list, too.
-dsr-
Reply to: