Bug 427992

Summary: Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
Product: [KDE Neon] neon Reporter: YAFU <yafulinux>
Component: Packages Testing EditionAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: jr, neon-bugs, sitter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description YAFU 2020-10-19 17:39:17 UTC
Hi.
Neon 20.04 (testing)

For a few days I have been having a dependency problem with "libkf5solid5_5.75.0+p20.04+git20201017.0151-0_amd64.deb" package. Apparently it depends on libudev1 >=246.6, but Ubuntu 20.04 repositories version is 245.4.

====
$ pkcon update
Getting updates               [=========================]         
Finished                      [=========================]         
Loading cache                 [ ==                      ]         QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
                              [=========================]         
Testing changes               [=========================]         
Finished                      [=========================]         
Fatal error: The following packages have unmet dependencies:
  libkf5solid5: Depende: libkf5solid5-data (= 5.75.0+p20.04+git20201015.0112-0) but 5.75.0+p20.04+git20201017.0151-0 is to be installed
==========
==
I clarify that my installation is not a pure Neon installation. I had a Kubuntu 20.04 installation to which I added Neon repository (testing), and after various dependencies fixes using "aptitude", I was able to have Neon without problems, until a few days ago where this problem appeared.

Related Thread:
https://forum.kde.org/viewtopic.php?f=309&t=168336&p=438685#

There are other people there having problems with udev too.
Comment 1 YAFU 2020-10-19 17:52:16 UTC
I clarify that this was until yesterday. Then I switched to "user" repositories. So if there were changes today in "testing" that fixed the problem, I have not tested it.
Comment 2 YAFU 2020-10-19 18:05:15 UTC
I switched back to Testing repositories. Apparently today there have been changes in this regard and I can update correctly now. Sorry I didn't try this today, I didn't know there were changes.
Comment 3 YAFU 2020-10-19 23:47:53 UTC
As this has been resolved with the latest packages, I mark this as fixed. I'm not sure if only moderators were allowed to do it, sorry if that's the case.