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