![]() Registered Member ![]()
|
Hi.
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.
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. EDIT: Maybe "testing" Neon version is based on the latest Kubuntu beta and not on 20.04? If this is so, I think I will have to use Neon "User edition" repository. EDIT 2: So I'm using "user" Neon repositories and now apparently there are no problems. What I don't know is if I will get future updates with "user" repositories since my original packages were installed from "testing" repos. So I'll see how this goes later. |
![]() Registered Member ![]()
|
I have a regular testing installation and have this problem too. The needed udev version is in 20.10, but testing is based on 20.04 LTS.
I'm searching for a solution since I build kdenlive from git to help in testing, and now I'm unable to do it, since the mismatched kf5 versions make the build fail. |
![]() Registered Member ![]()
|
Yes it's weird. Since Neon is always based on Kubuntu LTS versions, it is strange that Testing is using Kubuntu 20.10 versions for those packages.
|
![]() Registered Member ![]()
|
Anyone file a bug report on it? It might not be known until someone points it out in a place the devs are more likely to see it.
On bugs.kde.org file the bug under Neon >> 'Packages Testing Edition'
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
![]() Registered Member ![]()
|
I had searched where to do KDE Neon bug reports and I had not found the information on the Neon web page. I will report now.
EDIT: https://bugs.kde.org/show_bug.cgi?id=427992 |
![]() Registered Member ![]()
|
I switched back to Testing repositories. Apparently today there have been changes in this regard and I can update correctly now. |
Registered users: Bing [Bot], Google [Bot]