Apper problems

[Mustafa Muhammad]

Good morning everybody

Today I was testing the F25 RC-1.1, tried to install google-chrome
(downloaded rpm) and apper crashed (already reported bug):
https://bugzilla.redhat.com/show_bug.cgi?id=1383747

Also, opening apper, and selecting any group results in:
"A problem that we were not expecting has occurred.
Please report this bug with the error description."
"SearchGroups not supported by backend"
https://bugzilla.redhat.com/show_bug.cgi?id=1098735

If we want our users to install RPMs without terminal, I think it
would be reasonable to include something that actually works for F26,
some will hate me for this, but if nothing change before F26, we
better include gnome-software.

The download size for installing it is 9.2M over my F25, and this also
includes flatpack.

This will break our Qt purity even more, but I think
plasma-discover+gnome-software is better than plasma-discover+apper.

Regards
Mustafa

[Kevin Kofler]

Mustafa Muhammad wrote:
>  Today I was testing the F25 RC-1.1, tried to install google-chrome
>  (downloaded rpm) and apper crashed (already reported bug):
>  https://bugzilla.redhat.com/show_bug.cgi?id=1383747 
This one is probably a regression from the KF5 port. (Installing downloaded 
RPMs worked in the kdelibs4 version.)

>  Also, opening apper, and selecting any group results in:
>  "A problem that we were not expecting has occurred.
>  Please report this bug with the error description."
>  "SearchGroups not supported by backend"
>  https://bugzilla.redhat.com/show_bug.cgi?id=1098735 
And this one is a long-known missing feature in PackageKit-hif. This is not 
Apper's fault at all. Get PackageKit fixed.

Workaround: search by name or description instead, you will find your 
package(s) that way. Or use Discover (which uses AppStream for browsing).

>  If we want our users to install RPMs without terminal, I think it
>  would be reasonable to include something that actually works for F26, 
The plan is to ship: https://github.com/anaselli/dnfdragora

(It uses DNF directly without going through the PackageKit layer, and thus 
can browse groups just fine.)

>  some will hate me for this, but if nothing change before F26, we
>  better include gnome-software. 
Why? It has basically the same feature set (and in particular, also the same 
set of things it does NOT do) as Discover.

>  The download size for installing it is 9.2M over my F25, and this
> also
>  includes flatpack. 
That is absolutely HUGE for something as simple as an application browser. 
The Flatpak runtimes are probably the main reason.

>  This will break our Qt purity even more, but I think
>  plasma-discover+gnome-software is better than plasma-discover+apper. 
How is it better to ship 2 app stores with nearly identical functionality 
than an app store and a package manager?

I think shipping Discover and dnfdragora, or even just dnfdragora, is the 
way to go.

        Kevin Kofler

[Mustafa Muhammad]

On Sat, Nov 12, 2016 at 11:43 AM, Kevin Kofler <kevin.kofler(a)chello.at&gt; wrote:
>  Mustafa Muhammad wrote:
> > Today I was testing the F25 RC-1.1, tried to install google-chrome
> > (downloaded rpm) and apper crashed (already reported bug):
> > https://bugzilla.redhat.com/show_bug.cgi?id=1383747
>
>  This one is probably a regression from the KF5 port. (Installing downloaded
>  RPMs worked in the kdelibs4 version.)
>
> > Also, opening apper, and selecting any group results in:
> > "A problem that we were not expecting has occurred.
> > Please report this bug with the error description."
> > "SearchGroups not supported by backend"
> > https://bugzilla.redhat.com/show_bug.cgi?id=1098735
>
>  And this one is a long-known missing feature in PackageKit-hif. This is not
>  Apper's fault at all. Get PackageKit fixed.
>
>  Workaround: search by name or description instead, you will find your
>  package(s) that way. Or use Discover (which uses AppStream for browsing).
>
> > If we want our users to install RPMs without terminal, I think it
> > would be reasonable to include something that actually works for F26,
>
>  The plan is to ship: https://github.com/anaselli/dnfdragora 
The main reason for the mail was the problems (PackageKit or Apper,
the result is inability to install without dnf), I myself mostly use
dnf, but for new users, Discover is much better.

I wasn't aware of dnfdragora, looks good and should be great to include it.

>  (It uses DNF directly without going through the PackageKit layer, and thus
>  can browse groups just fine.)
>
> > some will hate me for this, but if nothing change before F26, we
> > better include gnome-software.
>
>  Why? It has basically the same feature set (and in particular, also the same
>  set of things it does NOT do) as Discover. 
Because it worked for installing the rpm while discover crashed:
https://bugs.kde.org/show_bug.cgi?id=372277

> > The download size for installing it is 9.2M over my F25, and this also
> > includes flatpack.
>
>  That is absolutely HUGE for something as simple as an application browser.
>  The Flatpak runtimes are probably the main reason.
>  
Flatpak should be important, we better included it even without gnome-software.

> > This will break our Qt purity even more, but I think
> > plasma-discover+gnome-software is better than plasma-discover+apper.
>
>  How is it better to ship 2 app stores with nearly identical functionality
>  than an app store and a package manager?
>
>  I think shipping Discover and dnfdragora, or even just dnfdragora, is the
>  way to go. 
I also think Discover and dnfdragora (now I know about it) would be enough.

Regards
Mustafa

>         Kevin Kofler
> _______________________________________________
> kde mailing list -- kde(a)lists.fedoraproject.org
> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org