Advertising

Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl

When Upgrading

Started by Ze_Mind, June 22, 2024, 03:42:26 AM

Previous topic - Next topic

Ze_Mind

I ran a update and upgrade, and I get this nasty fellow. And I try to fix it, but, umm..

mind@mind-system:~$ sudo apt upgrade
You might want to run 'apt --fix-broken install' to correct these.
Unsatisfied dependencies:
 libavif16 : Depends: libsvtav1enc1d1 (>= 1.7.0+dfsg) but it is not installed
Error: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
mind@mind-system:~$ sudo apt --fix-broken install
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libcbor0.8          libjavascriptcoregtk-4.1-0  libllvm15     libwebkit2gtk-4.1-0
  libgupnp-igd-1.0-4  libjim0.81                  libunibreak5
Use 'sudo apt autoremove' to remove them.

Installing dependencies:
  libsvtav1enc1d1

Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 698
  2 not fully installed or removed.
  Download size: 2,169 kB
  Space needed: 6,918 kB / 849 GB available

Continue? [Y/n] y
Get:1 http://deb.debian.org/debian trixie/main amd64 libsvtav1enc1d1 amd64 1.7.0+dfsg-2+b1 [2,169 kB]
Fetched 2,169 kB in 0s (9,146 kB/s)       
(Reading database ... 203752 files and directories currently installed.)
Preparing to unpack .../libsvtav1enc1d1_1.7.0+dfsg-2+b1_amd64.deb ...
Unpacking libsvtav1enc1d1:amd64 (1.7.0+dfsg-2+b1) ...
dpkg: error processing archive /var/cache/apt/archives/libsvtav1enc1d1_1.7.0+dfsg-2+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libSvtAv1Enc.so.1', which is also in package libsvtav1enc1:amd64 2:1.6.0-dmo1
Errors were encountered while processing:
 /var/cache/apt/archives/libsvtav1enc1d1_1.7.0+dfsg-2+b1_amd64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

msseufert

I signed up just to answer this.

This is an upstream issue from Sparky's perspective. The issue is with Debian testing/Trixie, which it appears Sparky or yourself are using. This issue, however, is resolved in Debian Sid so it's already fixed from an upstream perspective and options currently are to wait for Debian to backport the fix from Sid to Trixie or perhaps the Sparky devs can do that sooner.

View the most recent posts on the forum