[sorry, unintended personal reply the first time :( ] On Tue, 08 May 2012 20:53:22 +0530, Sven Burmeister wrote:

Am Dienstag, 8. Mai 2012, 15:04:15 schrieb phanisvara das:

...

On Tue, 08 May 2012 14:54:23 +0530, Basil Chupin

wrote:

...

... Can anyone throw some light on the above error message, please? (Or do I simply turn off the daily Online Update feature?)

practically everybody i know of has either disabled or uninstalled apper. it doesn't work, full stop. get rid of it & forget it.

That wrong in two ways. First of all apper is just a front-end to packagekit and packagekit is powered by a zypp-backend. Hence most issues you think are apper's fault are zypp backend bugs.

i didn't assign fault anywhere, apper, packagekit, or zypp libs. zpper works fine, but once you put it together with apper & packagekit, it stops working. it doesn't install needed patches, reports wrong patches as missing, and doesn't usually stop on it's own, blocking access to zypper or yast. if you call this working ok, i beg to differ

Second, apper works nicely for most situations and is very useful as a notifier since it is not an option to make users check for updates via zypper or running some yast module.

i'm not suggesting this solution for your SLES/D customers, but to basil, who clearly stated that he runs regular updates via zypper. for him, apper is neither needed nor useful, and just a source of trouble. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-05-08 20:52, DenverD wrote:

so, it is easiest to disable/ignore the program combo which does not work (apper & zypp)..

It is not apper & zypper. It just has a library to communicate with zypper libs, however they are called - but it takes its own decisions. Upstream develops apper and its libraries, openSUSE develops the backend that connects to zypper libs. The result is this "thing", that even talking to zypper can not respect zypper tabooes, probably because upstream decided not to have them or something. Whatever. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+pbEAACgkQIvFNjefEBxprygCfSKsX76ht5ocYaPH7p4tN1ABx AEoAoNJHDZ83s8m2QtnTlJTrnMQavjIv =XNh8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, 09 May 2012 00:22:52 +0530, DenverD wrote:

On 05/08/2012 05:23 PM, Sven Burmeister wrote:

...

Am Dienstag, 8. Mai 2012, 15:04:15 schrieb phanisvara das:

...

On Tue, 08 May 2012 14:54:23 +0530, Basil Chupin

wrote:

...

... Can anyone throw some light on the above error message, please? (Or do I simply turn off the daily Online Update feature?)

practically everybody i know of has either disabled or uninstalled apper. it doesn't work, full stop. get rid of it& forget it.

That wrong in two ways. First of all apper is just a front-end to packagekit and packagekit is powered by a zypp-backend. Hence most issues you think are apper's fault are zypp backend bugs.

and, to me (don't know about you--ymmv) i would rather disable apper than zypp, zypper or YaST..

you're joking, aren't you? you can not LIVE without zypper, while life goes on pretty much as always without apper & packagekit.

YaST Online Update and/or "zypper patch" works just fine for me..

(almost) always has. (while i prefer "zypper up" to ~ patch.)

so, it is easiest to disable/ignore the program combo which does not work (apper & zypp)..

yes.

btw: i also had to disable packagekit in 11.3, and chose to ignore/disable whatever it was called in KDE3 (on openSUSE 10.3)

since that time i haven't had either of them on my system. one or two libraries related to packagekit have to remain, due to some other dependencies, but alone they don't do any harm. what i don't understand is why this is neither being fixed nor removed. i do believe sven burmeister when he says that it works in many cases. after all, when things go right people don't write about them. but here & at the forums i've seen dozens of frustrated users complaining about apper, and the solution has always been "remove." not only from rash youngsters like myself, but also from seasoned & respected pillars of the community. looking from the outside, this doesn't appear to be such a huge problem -- not something like akonadi/strigi in KDE, which works (or doesn't) in thousands of layers. but then i've never really looked at this, because it's easy to remove and, at least for me, no great loss not to have. are the dev.s playing pingpong, apper saying it's zypper's fault and vice versa, and then all agree to blame packagekit? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Montag, 14. Mai 2012, 23:41:55 schrieb phanisvara das:

i doubt it's really the zypper backend at fault. if that was the case, why does packagekit act up the same way in fedora?

excerpt from "TLWIR 37: Fedora 17 Takes Off" (http://beginlinux.com/blog/2012/05/tlwir-37-fedora-17-takes-off/ ):

Did you not read the thread? It was about a specific error message and as I suspected zypper patch showed the same error. Packagkitd dies after some time if nothing calls it again. Just to be clear, there are bugs in all apps, including packagkit and apper. Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless. It hinders bugfixing and it demotivates devs that are not at fault etc. The only useful approach is to help people debugging and that way find out where the bug is acutally at. That's why I asked to try zypper patch instead of zypper up in order to make sure it is actually a packagekit or apper bug. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, May 14, 2012 at 2:12 PM, phanisvara das wrote:

On Tue, 15 May 2012 02:06:01 +0530, Sven Burmeister wrote:

...

...

i doubt it's really the zypper backend at fault. if that was the case, why does packagekit act up the same way in fedora?

excerpt from  "TLWIR 37: Fedora 17 Takes Off" (http://beginlinux.com/blog/2012/05/tlwir-37-fedora-17-takes-off/ ):

Did you not read the thread? It was about a specific error message and as I suspected zypper patch showed the same error. Packagkitd dies after some time if nothing calls it again. Just to be clear, there are bugs in all apps, including packagkit and apper. Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless. It hinders bugfixing and it demotivates devs that are not at fault etc. The only useful approach is to help people debugging and that way find out where the bug is acutally at. That's why I asked to try zypper patch instead of zypper up in order to make sure it is actually a packagekit or apper bug.

my my, aren't we touchy on this topic.

i did not, at least did not mean to blame apper in particular. it's just that apper is the user-facing application in this case, and using it results very often in the same hangup that was described by the OP (basil c.) as the beginning of this thread. the same thing has been experienced by very many others, including myself.

perhaps apper is the best application under the sun, but it does and must use other libraries, which also, on their own, are pretty good app.s.

(actually, i can't say this about packagekit, since i'm only aware of it's existence n combination with apper & zypper libs, and that doesn't look good. but to give it the benefit of the doubt, i'll assume it does very many other things very well.)

in the article i quoted above (you didn't read that, did you?) apper isn't even mentioned; only that packagekit starts with the system (fedora 17) and blocks the package management system, like apper does (in conjunction with others, and i don't know which one is to blame!) in openSUSE.

of course it's not the same bug, it's a different distro. my uneducated guess would be that it's packagekit's fault; either by doing something wrong, or being so difficult to deal with that both fedora & OS dev.s don't get it right for some reason.

i must admit that i'm not burning with desire to fix that bug. i can live very well without the whole triumvirat of apper/packagekit/zypp. i just remove those packages, and if others have similar problems, that's what i suggest. perhaps i can manage to include a disclaimer in the future, that it's not a loyal or helpful way of doing things...

-- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I prefer to be able to use my system and not find my access to YAST software management blocked every time I try and access it over debugging what is supposed to be the stable version of the OS and applications I am running usually. This "bug" was most frustration until I removed "apper' Nothing should ever block or lock me out of YAST software management. -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Google Voice 661 769 6201 +SMS openSUSE Linux 12.1 KDE 4.7.2 Known and FlameBait and  The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, May 14, 2012 at 2:33 PM, phanisvara das wrote:

trying to reply to your specific statements:

On Tue, 15 May 2012 02:06:01 +0530, Sven Burmeister wrote:

...

Did you not read the thread? It was about a specific error message and as I suspected zypper patch showed the same error. Packagkitd dies after some time if nothing calls it again. Just to be clear, there are bugs in all apps, including packagkit and apper.

i'm pretty sure that what basil c. experienced was not another zypper bug that may make the rounds now. i'm not running 12.1 very often these days, doing all my work on 12.2. there's a zypper & YAST bug there, too, but that may be something completely different. i've looked into the bug tracker re. that factory bug, but not into 12.1 bugs.

...

Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless.

it's useless for people trying to fix the bug, but for the user in this situation it enables him to use his packagemanagement system again. that's something.

not everybody feels equally motivated to put time & energy into any bug that appears anywhere. in my opinion, the automatic apper reminding thing isn't required. since you obviously feel different, you should go ahead and help fix it -- but you can't expect people who aren't interested in the feature to help very much.

...

It hinders bugfixing and it demotivates devs that are not at fault etc.

well, if the recommendation to not use something that often doesn't work is evil, then i'm afraid that's what i am.

...

The only useful approach is to help people debugging and that way find out

...

where the bug is acutally at. That's why I asked to try zypperpatch instead of zypper up in order to make sure it is actually apackagekit or apper bug.

just read the whole conversation again. it looks as if he got the option to try to kill packagekit, which he did, and then zypper patch could run.

i still see the same bug, that packagekit, being called by apper, blocks access for other package management tools, and after it's asked to quit, via dialog or kill command, things work again. that's always been there, but a nuisance, so for those who don't care for apper, uninstalling is still the easiest way to solve the problem -- personally, not for the whole part of humanity that uses openSUSE or SLES/D. that's cold-hearted and uncaring, i know, but what to do. i've got limited time for this and i prefer to spend it on things that are important for me, too.

-- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

When I tried to kill it at the notification if just would not kill it. I couldn't make it let go via that route. I had to go into HTOP and kill it there. All I wanted to do was mange my own software. I didn't need that issue blocking what I wanted to do right now. -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Google Voice 661 769 6201 +SMS openSUSE Linux 12.1 KDE 4.7.2 Known and FlameBait and  The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 15 May 2012 04:08:33 +0530, Sven Burmeister wrote:

You missed the point. You mixed my replies to a specific issue, Basil's original conflict http://picpaste.com/snapshot1-xCgPnMpz.png , with something I never replied to, i.e. the packagkitd blocking zypper. Hence I skip the ladida resulting from your confusion about the chronological order and quoted text of my replies.

you know what, i still don't agree with you, but am not interested to continue this. i prefer my confusion to this discussion. i get my main benefit from listening in these mailing lists & forums. sometimes i try to help, but in future i'll just avoid that, since apparently i don't understand what's going on. will save me quite some time, botheration, and not affect my use of openSUSE. have a nice day. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 15/05/12 09:34, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-05-15 00:38, Sven Burmeister wrote:

...

Am Dienstag, 15. Mai 2012, 03:03:31 schrieb phanisvara das:

...

Your, Carlos' et. al. answer to Basil's original mail would not have solved the issue, i.e. were useless. Not at all, it did help to find the solution.

...

I know that because zypper patch showed the same conflict and removing apper would not have changed that. No, that is not true. He said:

]> I just ran 'zypper patch' and found that it came up with the message which is referred to the error message I got. The only thing is that it ]> provided a choice and therefore a solution on how to overcome this dependency problem.

Zypper did the correct thing, it posted a message and the solution. Apper did not.

...

Your hating on apper lead you to the wrong conclusion and made you give some unhelpful and useless, regarding solving the original issue, advice. I, we, do not hate apper. It is simply a useless piece of software, problems are solved by removing it.

- -- Cheers / Saludos,

GIRLS! GIRLS! Before you pull each other's hair out and scratch out the eyes permit me to summarise what occurred after I wrote my first post which started this thread. I had just installed my new x86_64 system and found that I kept getting notification (the sun-looking icon on the taskbar) that there is an update(s) which needs to be put thru. I click on this widget and then apper (as I found later that this is what it is called) comes up with a dependency error (a copy of which I posted on picpaste). I ignore it but it keeps haunting me. To see if there are in fact a patch to be done I ran YaST> Package>All Packages option which shows that there is nothing to be updated. While I am doing this I get replies telling me that apper is "a very badand naughty boy" and should be removed, and if I did this then my problem would disappear. I followed this advice and I no longer had that sun-looking widget appear on my taskbar. Sven of course is giving advise on all of this and in one of his messages he mentions that "zypper patch" should also show that there is some patch(es) to be done just as apper is doing. I ran "zypper patch" and found that, yes, there was a patch which had to be done just like apper did BUT "patch" also provided solutions/options on how to overcome the dependency problem - whereas apper didn't (and which is why I went to YaST and then simply uninstalled apper to get rid of that pesky widget). By choosing the right option(s) in 'patch' I overcame the dependency problem and had the patch installed. What I now do every morning is run "zypper patch" etc - but I have NOT re-installed apper. Why have it when 'zypper patch' does the same job PLUS it shows details on how to solve dependency hassles should they arise? So, this is the summary of events. But the one thing which stands out quite clearly is: why didn't YaST show that there really was a patch which needed to be applied? Apper did, 'zypper patch' did but not YaST. Now I DO remember that in the past YaST showed that patches had to be done but not in this case. Why not? BC -- Using openSUSE 12.1 x86_64 KDE on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-05-15 05:06, Ed Greshko wrote:

On 05/15/2012 10:36 AM, Basil Chupin wrote:

...

GIRLS! GIRLS! Before you pull each other's hair out and scratch out the eyes permit me to summarise what occurred after I wrote my first post which started this thread.

I hope you realize that you've enforced a negative stereotype of women.

He could have said "boys" and the meaning would have been the same. I would have seen no disrespect. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+yONoACgkQIvFNjefEBxq2GQCgm1UjZgAfwnC3yJ/1hELBnn2P rqkAoLBjFIc1MIab2/jxPRSmViQb6pHZ =TC26 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 15 May 2012 15:53:16 +0530, Insomniactoo wrote:

Good way to get people who are disagreeing on a subject to 'help' you. I hope that one comes back around and kicks ya in the teeth.

i really _love_ this community. [/sarcasm] i'll still be monitoring this list for the tecnical expertise to be found here, but won't interact with you guys in general. that's different in the forums, where there's less expertise, but more decency. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 15 May 2012 02:06:01 +0530, Sven Burmeister wrote:

Just to be clear, there are bugs in all apps, including packagkit and apper.

you dont'say...

Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless. It hinders bugfixing and it demotivates devs that are not at fault etc. The only useful approach is to help people debugging and that way find out where the bug is acutally at. That's why I asked to try zypper patch instead of zypper up in order to make sure it is actually a packagekit or apper bug.

if any of the dev.s who are working on this would comment here and say something like: "hey guys, we need help fixing this apper situation, please install it, run it through strace (or whatever), and help us figure out what goes wrong...," that would probably motivate me. since i don't want to use it, i'm not automatically motivated. you telling me it's my duty to help debug every application under the sun, even though i don't care for them, including apper, doesn't motivate me either. if i see somebody is in trouble and i could help them, i'd probably want to do so. but for all i know apper/packagekit/zypp has been forgotten or given up on by it's developers. that's at least what it looks like, without inside information. unless i learn something different, i won't use it, and won't recommend to others to do so. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-05-14 22:36, Sven Burmeister wrote:

blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos)

Just for the record, I did not do that at first. I was convinced by others. And rightly so, I believe after some time. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+xl5AACgkQIvFNjefEBxofFACfSSgY2EjEupzrqaAw48y5T/j+ DB4AnRKcVI2WxptsCxKH/cg3hfetnWj3 =frCU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Dienstag, 8. Mai 2012, 12:23:01 schrieb jdd-gmane:

Le 08/05/2012 11:24, Basil Chupin a écrit :

...

Can anyone throw some light on the above error message, please? (Or do I simply turn off the daily Online Update feature?)

simply ignore it, everbody have the same (or nearly)

Not a good idea. Run YaST or zypper to resolve the conflict, they will show the same issue. After that apper continuous to work. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Dienstag, 8. Mai 2012, 18:11:34 schrieb jdd-gmane:

no, no issue with zypper or yast, and I can't go to yast every time apper ask for

most/every time, it's an error that come at the very end of the work and the update is done

You did not have a look at the error message, did you? What you are talking about is something different and while maybe annoying does not hinder any updates at all. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/05/12 01:25, Sven Burmeister wrote:

...

Le 08/05/2012 11:24, Basil Chupin a �crit :

...

Can anyone throw some light on the above error message, please? (Or do I simply turn off the daily Online Update feature?) simply ignore it, everbody have the same (or nearly) Not a good idea. Run YaST or zypper to resolve the conflict, they will show

Am Dienstag, 8. Mai 2012, 12:23:01 schrieb jdd-gmane: the same issue. After that apper continuous to work.

Sven

One would think so but in my original post I wrote, "I have also use YaST to check if any Packages need updating/upgrading but even this returns advice that nothing is needed to be updated/upgraded. YaST's Dependency Check also shows that no files have dependency problems.". This is what made me ask the question re the error message. BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/05/12 14:07, Sven Burmeister wrote:

Am Mittwoch, 9. Mai 2012, 13:01:24 schrieb Basil Chupin:

...

One would think so but in my original post I wrote, "I have also use YaST to check if any Packages need updating/upgrading but even this YaST online update module and zypper patch?

If zypper up works but zypper patch shows the same behaviour it is something like https://bugzilla.novell.com/show_bug.cgi?id=743748

Oh dear :-( . I remember reading quite some time ago that using "up" in zypper also included updating any patches (zypper patch). Obviously I either misunderstood what I read or something change. I just ran 'zypper patch' and found that it came up with the message which is referred to the error message I got. The only thing is that it provided a choice and therefore a solution on how to overcome this dependency problem. I applied the patch using zypper - and the system is still working so it must have been a successful application of the patch :-) . Thanks for the prompt showing that "up" does not include "patch" in zypper. BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/05/12 18:35, Roger Luedecke wrote:

On Wed, 2012-05-09 at 18:01 +1000, Basil Chupin wrote:

...

On 09/05/12 14:07, Sven Burmeister wrote:

...

Am Mittwoch, 9. Mai 2012, 13:01:24 schrieb Basil Chupin:

...

One would think so but in my original post I wrote, "I have also use YaST to check if any Packages need updating/upgrading but even this YaST online update module and zypper patch?

If zypper up works but zypper patch shows the same behaviour it is something like https://bugzilla.novell.com/show_bug.cgi?id=743748 Oh dear :-( .

I remember reading quite some time ago that using "up" in zypper also included updating any patches (zypper patch).

Obviously I either misunderstood what I read or something change.

I just ran 'zypper patch' and found that it came up with the message which is referred to the error message I got. The only thing is that it provided a choice and therefore a solution on how to overcome this dependency problem.

I applied the patch using zypper - and the system is still working so it must have been a successful application of the patch :-) .

Thanks for the prompt showing that "up" does not include "patch" in zypper.

BC

What is difference between 'up' and 'patch?'

In a terminal, type 'man zypper' and look for "Update Management Control". BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-05-09 13:19, George Olson wrote:

On 05/09/2012 04:35 PM, Roger Luedecke wrote:

...

What is difference between 'up' and 'patch?'

Please correct me if I am wrong since I am new at this, but I understand it like this. "zypper up" updates all the installed packages to newer versions of those packages, and "zypper patch" applies corrective fixes to installed packages without updating them to newer versions.

Close, but not quite. That's the consequence of what it does. zypper patch, which is equivalent to yast online update (YOU), only applies updates that come from the updates repo. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+qVPwACgkQIvFNjefEBxqQSgCgqFFVjqk3nSlwAe/xb9ec2kQS 70AAn3NaQKCW4u7YvMeeHkSexk5YaGdb =Zfdf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-05-10 02:35, george olson wrote:

I am glad you mentioned that, because I didn't know that from reading the manual. In the zypper manual, it doesn't say anything under the zypper patch section that it only applies updates that come from the updates repo, and it gives an option for applying updates from whatever repo you want to specify:

It happens that the only repo that contains patches is the updates repo. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+rFIsACgkQIvFNjefEBxpbDwCeKI+zKzCX56DRjA3DtL1EnPx6 +L0An1zmcXh4uvipAzgFUJFFKY8ZRtOB =LYxk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/05/12 20:33, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-05-08 11:24, Basil Chupin wrote:

...

Everyday the Online Update widget shows me that there is an update available and when I run this I get this error message: Uninstall apper. It is broken.

Thank you Carlos, jdd and Phanisvara. Tomorrow morning apper goes to the place where all naughty-type applications go :-) . BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org