[Freedombox-discuss] Unmet dependencies, "Applying updates failed".

[A. F. Cano]

On Tue, Dec 15, 2020 at 09:50:50PM -0500, James Valleroy via Freedombox-discuss wrote:
> On 12/14/20 6:00 PM, A. F. Cano wrote:
> > But the problem after all these packages got installed is that  there
> > are still unmet dependencies.  From cockpit->software updates:
> > 
> > The following packages have unmet dependencies:
> >   php-common: Breaks: php7.3-common but 7.3.15-3 is to be installed
> >   libgc1: Conflicts: libgc1c2 but 1:7.6.4-0.4 is to be installed
> >   fuse3: Breaks: fuse
> >   libgcc1: Depends: gcc-10-base (= 10.1.0-1) but 10.2.0-19 is to be installed
> >   python3-django: Breaks: python-django-common
> >   libmailutils5: Depends: mailutils-common (= 1:3.5-3) but 1:3.10-3 is to be installed
> >   libgc1c2: Conflicts: libgc1 but 1:8.0.4-3 is to be installed
> > 
> > What is the proper way to deal with this?  I've tried to keep the
> > FreedomBox completely standard, not installing anything manually.
> > Could this be related to backports?
> 
> This issue is common on testing/bullseye (until it is frozen for release).
> 
> The manual solution is to try upgrading just one of the listed packages (with "apt install <package>"), and see if that would lead to any important packages (freedombox, apps) being removed. If it would remove an important package, then you can cancel the upgrade. It may remove some non-important or obsolete packages, such as python2 packages, and that is ok.
> 

Ok, thanks.  Since fuse3 looks like the simplest...  But what voluminous
output!  I hope fuse3 is compatible with fuse and thus the packages that
depend on it are not now broken...


$ sudo apt install fuse3
[sudo] password for ac-adm: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libfuse3-3
The following packages will be REMOVED:
  fuse
The following NEW packages will be installed:
  fuse3 libfuse3-3
0 upgraded, 2 newly installed, 1 to remove and 21 not upgraded.
Need to get 119 kB of archives.
After this operation, 255 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian testing/main amd64 libfuse3-3 amd64 3.10.0-1 [84.6 kB]
Get:2 http://deb.debian.org/debian testing/main amd64 fuse3 amd64 3.10.0-1 [33.9 kB]
Fetched 119 kB in 0s (753 kB/s)  
quota not working (qgroup not set)
Selecting previously unselected package libfuse3-3:amd64.
(Reading database ... 99860 files and directories currently installed.)
Preparing to unpack .../libfuse3-3_3.10.0-1_amd64.deb ...
Unpacking libfuse3-3:amd64 (3.10.0-1) ...
dpkg: fuse: dependency problems, but removing anyway as you requested:
 sshfs depends on fuse.
 ntfs-3g depends on fuse.
 exfat-fuse depends on fuse.
 borgbackup depends on fuse.

(Reading database ... 99869 files and directories currently installed.)
Removing fuse (2.9.9-3) ...
update-initramfs: deferring update (trigger activated)
Selecting previously unselected package fuse3.
(Reading database ... 99858 files and directories currently installed.)
Preparing to unpack .../fuse3_3.10.0-1_amd64.deb ...
Unpacking fuse3 (3.10.0-1) ...
Setting up libfuse3-3:amd64 (3.10.0-1) ...
Setting up fuse3 (3.10.0-1) ...
Installing new version of config file /etc/fuse.conf ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.31-5) ...
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.9.0-4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
quota not working (qgroup not set)
Scanning processes...                                                           
Scanning processor microcode...                                                 
Scanning linux images...                                                        

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.