https://bugs.kde.org/show_bug.cgi?id=404217
--- Comment #4 from Tim Richardson <t...@growthpath.com.au> --- I think the search result is wrong. Searching for kdevelop gets a different result (the package I find has reviews and installs). The search result from 'develop' is for a package which looks the same but has no reviews. It's the sort of thing you see when you get results from a (say) flatpak result and a .Deb result. However the bad result does not identify itself as a flatpak or snap package. It is very confusing. When using Muon there is no confusion. You get one result and it works. So Discover is doing something wrong. On Wed, 13 Feb. 2019, 05:22 Nate Graham <bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=404217 > > --- Comment #3 from Nate Graham <n...@kde.org> --- > The problem isn't finding it, it's installing it. Tim reported that upon > attempting to install, Discover gave this error message: > > > OBSERVED RESULT > > Error: can not resolve dependency > Which comes from PackageKit, which is reporting an issue with the current > state > of the distro packages. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
