Errors when 'apt upgrade'

[Epidemia]

Hello,

I have the following output when doing apt upgrade:

Code: Select all

Setting up libpam0g-dev:amd64 (1.4.0-6) ...
Setting up libclutter-imcontext-0.1-bin (0.1.4-3.1) ...
Cannot load module /usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so: GModule (/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch)
/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so does not export Clutter IM module API: GModule (/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch)
dpkg: error processing package libclutter-imcontext-0.1-bin (--configure):
 installed libclutter-imcontext-0.1-bin package post-installation script subprocess returned error exit status 1
Setting up firmware-misc-nonfree (20210208-3) ...
Setting up linux-libc-dev:amd64 (5.10.19-1) ...
Setting up linux-image-amd64 (5.10.19-1) ...
Setting up libuim8:amd64 (1:1.8.8-9) ...
dpkg: dependency problems prevent configuration of ibus-clutter:amd64:
 ibus-clutter:amd64 depends on libclutter-imcontext-0.1-bin; however:
  Package libclutter-imcontext-0.1-bin is not configured yet.

dpkg: error processing package ibus-clutter:amd64 (--configure):
 dependency problems - leaving unconfigured

It started to happen when I switched from Debian 10.6 to testing.

Could someone help to resolve those errors?

[Hallvor]

Assuming your sources.list is as it should be, try

Code: Select all

# apt -f upgrade

[Epidemia]

Assuming your sources.list is as it should be, try

Code: Select all

# apt -f upgrade

Hallvor, thank you for prompt reply!

You're right. I changed my sources.list according to the How to upgrade to Debian (next-stable) Testing section of this guide: https://wiki.debian.org/DebianTesting, i.e. my /etc/apt/sources.list looks like the following:

Code: Select all

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

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

But at the time of my initial post, I forgot to add the last line above.

Please let me know if my /etc/apt/sources.list is still incorrect.

Now it doesn't display any errors, but I have the following output:

Code: Select all

sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
    <bunch of packages here>
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
    <bunch of packages here>
0 upgraded, 0 newly installed, 0 to remove and 220 not upgraded.

Do I need to get rid of that kept-back packages warning or it's normal for the testing branch?

[dilberts_left_nut]

and 220 not upgraded

Code: Select all

sudo apt full-upgrade

[Hallvor]

Your sources.list looks fine. Don't worry about security not being enabled when upgrading. I disabled it when upgrading my system to Bullseye yesterday, and it worked fine regardless.

Yes, you must do the full-upgrade, as stated above, and let us know if there are any problems.

From the manpages:

upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be
removed. If an upgrade for a package requires the removal of an installed package the upgrade for this package isn't performed.

full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole.

[Epidemia]

dilberts_left_nut and Hallvor, thank you! full-upgrade resolved everything.

May I ask: should we always use full-upgrade instead of upgrade? (i.e. not only during a serious upgrades like stable -> testing)

From the man page as well as a table from this (https://unix.stackexchange.com/a/536620) answer, keeping the system up-to-date with full-upgrade makes more sense to me. But I've read somewhere on SE, that full-upgrade is dangerous or something like that. However, I don't have any cases when it could be dangerous on top of my mind.

[Hallvor]

To my knowledge, apt full-upgrade should be used in a non-stable environment (=testing or unstable), but keep an eye on what it wants to do. If it wants to remove your desktop environment, don't wildly press y.

apt upgrade won't break anything, but it won't fully upgrade the system (if files will have to be deleted to resolve dependencies).

Since stable doesn't need to resolve any dependencies, apt update && apt upgrade is the only command I use to keep a stable release up to date.

[Epidemia]

To my knowledge, apt full-upgrade should be used in a non-stable environment (=testing or unstable), but keep an eye on what it wants to do. If it wants to remove your desktop environment, don't wildly press y.

apt upgrade won't break anything, but it won't fully upgrade the system (if files will have to be deleted to resolve dependencies).

Since stable doesn't need to resolve any dependencies, apt update && apt upgrade is the only command I use to keep a stable release up to date.

Hallvor, thank you! I've got an idea of when to use each of them