Bug 463947 - Wrong dependencies make it impossible to update/install packages
Summary: Wrong dependencies make it impossible to update/install packages
Status: RESOLVED NOT A BUG
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR critical
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-06 22:43 UTC by ray
Modified: 2023-01-10 18:12 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ray 2023-01-06 22:43:34 UTC
After today update there is absolutely chaon in dependencies. kmail, akregator, korganizer are gone. when I try instal kmail 

Investigating (0) libkf5messageviewer5:amd64 < none -> 4:22.12.1-0xneon+22.04+jammy+release+build24 @un puN Ib >
Broken libkf5messageviewer5:amd64 Depends on libkf5mbox5:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build14 @rc uH >
  Considering libkf5mbox5:amd64 2 as a solution to libkf5messageviewer5:amd64 10
  Re-Instated libkf5mbox5:amd64
Broken libkf5messageviewer5:amd64 Depends on libqca-qt5-2:amd64 < none | 2.3.4-1build1 @un uH > (>= 2.3.5)
  Considering libqca-qt5-2:amd64 0 as a solution to libkf5messageviewer5:amd64 10
  Re-Instated libqca-qt5-2:amd64
Investigating (0) kdepim-runtime:amd64 < none -> 4:22.12.1-0xneon+22.04+jammy+release+build26 @rc puN Ib >
Broken kdepim-runtime:amd64 Depends on kio-ldap:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build12 @rc uH >
  Considering kio-ldap:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated kio-ldap:amd64
Broken kdepim-runtime:amd64 Depends on kio-sieve:amd64 < none | 4:22.12.1-0xneon+22.04+jammy+release+build23 @un uH >
  Considering kio-sieve:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated kio-sieve:amd64
Broken kdepim-runtime:amd64 Depends on libsasl2-modules-kdexoauth2:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build13 @un uH >
  Considering libsasl2-modules-kdexoauth2:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated libsasl2-modules-kdexoauth2:amd64
Broken kdepim-runtime:amd64 Depends on libetebase0:amd64 < none | 0.5.3-0xneon+22.04+jammy+release+build2 @un uH > (>= 0.5.3)
  Considering libetebase0:amd64 0 as a solution to kdepim-runtime:amd64 0
  Re-Instated libetebase0:amd64
Broken kdepim-runtime:amd64 Depends on libkf5dav5:amd64 < none | 1:5.101.0-0xneon+22.04+jammy+release+build17 @rc uH >
  Considering libkf5dav5:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated libkf5dav-data:amd64
  Re-Instated libkf5dav5:amd64
Broken kdepim-runtime:amd64 Depends on libkolabxml1v5:amd64 < none | 1.2.1-1build1 @un uH > (>= 1.1.0)
  Considering libkolabxml1v5:amd64 0 as a solution to kdepim-runtime:amd64 0
  Re-Instated libkolabxml1v5:amd64
Broken kdepim-runtime:amd64 Depends on libkpimgapicalendar5:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build13 @un uH >
  Considering libkpimgapicalendar5:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated libkpimgapicalendar5:amd64
Broken kdepim-runtime:amd64 Depends on libkpimgapicontacts5:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build13 @un uH >
  Considering libkpimgapicontacts5:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated libkpimgapicontacts5:amd64
Broken kdepim-runtime:amd64 Depends on libkpimgapitasks5:amd64 < none | 22.12.1-0xneon+22.04+jammy+release+build13 @un uH >
  Considering libkpimgapitasks5:amd64 1 as a solution to kdepim-runtime:amd64 0
  Re-Instated libkpimgapitasks5:amd64
Broken kdepim-runtime:amd64 Depends on libqca-qt5-2:amd64 < none -> 2.3.4-1build1 @un uN IPb > (>= 2.3.5)
  Considering libqca-qt5-2:amd64 0 as a solution to kdepim-runtime:amd64 0
Done
Comment 1 ray 2023-01-07 16:21:29 UTC
i've disable archive.ubuntu in apt but this don't help

Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 5.15.0-57-generic (64-bit)
Graphics Platform: X11
Comment 2 ray 2023-01-08 02:43:24 UTC
network settings gone too, reinstall plasma-nm giving this:

Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) plasma-nm:amd64 < none -> 4:5.26.5-0xneon+22.04+jammy+release+build15 @un puN Ib >
Broken plasma-nm:amd64 Depends on qml-module-org-kde-prison:amd64 < none | 5.101.0-0xneon+22.04+jammy+release+build16 @un uH >
  Considering qml-module-org-kde-prison:amd64 1 as a solution to plasma-nm:amd64 10101
  Re-Instated qml-module-org-kde-prison:amd64
Broken plasma-nm:amd64 Depends on libkf5modemmanagerqt6:amd64 < none | 5.101.0-0xneon+22.04+jammy+release+build11 @rc uH >
  Considering libkf5modemmanagerqt6:amd64 1 as a solution to plasma-nm:amd64 10101
  Re-Instated libkf5modemmanagerqt6:amd64
Broken plasma-nm:amd64 Depends on libopenconnect5:amd64 < none | 8.20-1 @un uH > (>= 7.05)
  Considering libopenconnect5:amd64 0 as a solution to plasma-nm:amd64 10101
  Re-Instated libxmlsec1:amd64
  Re-Instated libxmlsec1-openssl:amd64
  Re-Instated libpskc0:amd64
  Re-Instated libtommath1:amd64
  Re-Instated libtomcrypt1:amd64
  Re-Instated libstoken1:amd64
  Re-Instated libtss2-tctildr0:amd64
  Re-Instated libopenconnect5:amd64
Broken plasma-nm:amd64 Depends on libqca-qt5-2:amd64 < none | 2.3.4-1build1 @un uH > (>= 2.3.5)
  Considering libqca-qt5-2:amd64 0 as a solution to plasma-nm:amd64 10101
  Re-Instated libqca-qt5-2:amd64
Comment 3 ray 2023-01-08 02:47:17 UTC
there was wayland downgrades few mins a go when i try apt again so assume there is work in progress to fix these mess.
Comment 4 Riccardo Robecchi 2023-01-09 14:20:13 UTC
I can see the issues, too. Marking this as confirmed.
Comment 5 ray 2023-01-09 15:03:42 UTC
for time being i've resolved problem with aptitude
Comment 6 Riccardo Robecchi 2023-01-09 15:04:11 UTC
As pointed out by someone on the Telegram KDE Neon group, removing the /etc/apt/preferences.d/98-jammy-overrides file fixes the issue. This seems like a packaging error as there is a new file named "99-jammy-overrides", when it should have ben "98-jammy-overrides" (or vice-versa).
Comment 7 ray 2023-01-09 15:36:13 UTC
after remove 98-jammy-overrides

these packages are new now (seems upgraded again from time i mentioned earlier about wayland) 

libsnmp-base/jammy-security 5.9.1+dfsg-1ubuntu2.4 all [upgradable from: 5.9.1+dfsg-1ubuntu2.2]
libsnmp40/jammy-security 5.9.1+dfsg-1ubuntu2.4 amd64 [upgradable from: 5.9.1+dfsg-1ubuntu2.2]
libwayland-bin/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
libwayland-client0/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
libwayland-cursor0/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
libwayland-dev/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
libwayland-egl1/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
libwayland-server0/jammy 1.21.0-0xneon+22.04+jammy+release+build13 amd64 [upgradable from: 1.20.0-1ubuntu0.1]
w3m-img/jammy-security 0.5.3+git20210102-6ubuntu0.1 amd64 [upgradable from: 0.5.3+git20210102-6build3]
w3m/jammy-security 0.5.3+git20210102-6ubuntu0.1 amd64 [upgradable from: 0.5.3+git20210102-6build3]

someone from dev team can point us what to do:
leave 99-jammy-overrides or rename to 98-jammy-overrides as replacement for 98-jammy-overrides i just removed.

Suspect when new update arrive wrong name can make new problems
Comment 8 Jonathan Riddell 2023-01-09 15:46:29 UTC
98-jammy-overrides comes from the upgrader from the 20.04 base and it should be removed.

99-jammy-overrides is in the neon-settings-2 package.  Because it is treated as a "conf file" by dpkg it often will not be upgraded even when the package has a newer version.  Download and replace with this file
https://invent.kde.org/neon/neon/settings/-/raw/Neon/unstable/etc/apt/preferences.d/99-jammy-overrides?inline=false
Comment 9 Gaël de Chalendar (aka Kleag) 2023-01-10 18:07:49 UTC
Got the same problem. Following advice from comments 6 and 8 solved the problem.
Thanks.