On 11/08/2016 08:57 AM, Dave Howorth wrote:

It doesn't seem to be. apper seems to be a GUI

It does have a gui, but it lives in the tray (invisibly) and pops up a notification when there are updates. If you click the update button in the notification it will pop up screen from which you can install the updates, or you can dismiss the notification and use yast. That said, both are using zypper as the backend, so there the result is the same in the end. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-11-08 18:37, John Andersen wrote:

On 11/08/2016 08:57 AM, Dave Howorth wrote:

...

It doesn't seem to be. apper seems to be a GUI

It does have a gui, but it lives in the tray (invisibly) and pops up a notification when there are updates. If you click the update button in the notification it will pop up screen from which you can install the updates, or you can dismiss the notification and use yast.

That said, both are using zypper as the backend, so there the result is the same in the end.

Nope. apper uses packagekit. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-11-08 18:50, John Andersen wrote:

On 11/08/2016 09:46 AM, Carlos E. R. wrote:

...

On 2016-11-08 18:37, John Andersen wrote:

...

On 11/08/2016 08:57 AM, Dave Howorth wrote:

...

It doesn't seem to be. apper seems to be a GUI

It does have a gui, but it lives in the tray (invisibly) and pops up a notification when there are updates. If you click the update button in the notification it will pop up screen from which you can install the updates, or you can dismiss the notification and use yast.

That said, both are using zypper as the backend, so there the result is the same in the end.

Nope. apper uses packagekit.

Check you facts Carlos. Packagekit uses zypper.

No. Packagekit uses libzypp, which is also used by zypper. There is a large difference. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-11-08 19:08, John Andersen wrote:

On 11/08/2016 09:54 AM, Carlos E. R. wrote:

...

On 2016-11-08 18:50, John Andersen wrote:

...

On 11/08/2016 09:46 AM, Carlos E. R. wrote:

...

On 2016-11-08 18:37, John Andersen wrote:

...

...

...

...

That said, both are using zypper as the backend, so there the result is the same in the end.

Nope. apper uses packagekit.

Check you facts Carlos. Packagekit uses zypper.

No. Packagekit uses libzypp, which is also used by zypper. There is a large difference.

Libzypp is where the work is done.

zypper - Command line software manager using libzypp < official description

There really isn't a difference in how the work gets done.

Yes, there is. Packagekit doesn't use zypper, it uses the library. It is very different. Both use the library differently and obtain different results some times, and give different information. When a GUI calls the command line manager it is called a frontend to that command line program. This is not the case, both are independent programs. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Le 09/11/2016 à 10:38, John Andersen a écrit :

All the work is done by the library.

if so, why do apper fail when zypper up succeed? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-11-09 10:38, John Andersen wrote:

On 11/08/2016 06:41 PM, Carlos E. R. wrote:

...

Yes, there is. Packagekit doesn't use zypper, it uses the library. It is very different. Both use the library differently and obtain different results some times, and give different information.

Nope. You're wrong Carlos. Zypper doesn't do anything magic.

Who said magic?

Zypper just uses the library.

Packagekit just uses the library. Same thing, same result.

Same thing, yes, but differently. Different results. Still, you said "That said, both are using zypper as the backend," which is not true, and you are agreeing on it now. Sometimes apper finds a conflict, bails out, and people have to use zypper or Yast to solve the conflict. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-11-09 11:43, Vojtěch Zeisek wrote:

Dne středa 9. listopadu 2016 11:38:14 CET, Carlos E. R. napsal(a):

...

On 2016-11-09 10:38, John Andersen wrote:

...

On 11/08/2016 06:41 PM, Carlos E. R. wrote: Zypper just uses the library.

Packagekit just uses the library. Same thing, same result.

Same thing, yes, but differently. Different results. Still, you said "That said, both are using zypper as the backend," which is not true, and you are agreeing on it now.

Sometimes apper finds a conflict, bails out, and people have to use zypper or Yast to solve the conflict.

You can use the very same library in very different ways... As far as I know bot are using libzypp, but the update applet doesn't have way to interact with user (at least it seems to me so), so that I consider it as nearly unusable and immature - as You say, in case of conflicts, one must use some real tool...

Yes, of course. The update applet is designed to work on several distributions, using different backends on each one. It is a tool of the desktop, not of openSUSE. I suppose it is thus limited to the common features of each distribution update engine. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 11/08/2016 10:11 AM, Dave Howorth wrote:

nvisible, how do I know it's running? There's no process called apper. It's man page doesn't show any suitable options. How does it get installed in the tray?

I may be wrong about running in the tray in this systemd world in which we live..... It might be a cron job or something run by systemd and it may run under the name of packagekit -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 08 Nov 2016 17:39:24 +0100 Oliver Kurz wrote:

On Tuesday 08 November 2016 16:23:43 Dave Howorth wrote:

...

Is there a way to be notified of software updates being available in Leap 42.1?

I see web pages that talk about a KDE update applet, but (a) I don't use KDE and (b) it doesn't appear when I search YaST anyway.

regarding '(a)':

Depends very much on what environment you actually use and what you prefer. Because Leap is very stable you can go with automatic application of updates and actually care about "notification" of updates. Or call "pkcon get-updates" to see updates in console.

I presently run LXDE, but I expect that will change sometime. Maybe LXQt, or maybe something else. Call me a luddite but I'm not comfortable with automatic updates. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 08 Nov 2016 18:11:15 +0100 Oliver Kurz wrote:

On Tuesday 08 November 2016 16:59:18 Dave Howorth wrote:

...

Call me a luddite but I'm not comfortable with automatic updates.

You can for example only enable automatic updates for "critical security fixes"

Call me a luddite but I'm not comfortable with automatic updates :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org