In other words: avoid, get rid of, disable, uninstall, whatever - but don’t use…
Love 12.1, no real problems except for the above nuisance. Use YaST or zypper.
Am 21.11.2011 14:16, schrieb gminnerup:
>
> In other words: avoid, get rid of, disable, uninstall, whatever - but
> don’t use…
> Love 12.1, no real problems except for the above nuisance. Use YaST or
> zypper.
>
>
Like the father so the son
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
> Like the father so the son
really?? that is so sad…we have gone months now advising folks to
uninstall kpackagekit and now the same thing (new name) with 12.1!!
why do the devs do this??
oh–i never logged a bug against kpackagekit in 11.4–and, now i wonder
if no one did…have you two logged these 12.1 bugs?
–
DD
dump Flash: http://www.bbc.co.uk/news/technology-15797399
Am 21.11.2011 15:03, schrieb DenverD:
>> Like the father so the son
>
> really?? that is so sad…we have gone months now advising folks to
> uninstall kpackagekit and now the same thing (new name) with 12.1!!
>
> why do the devs do this??
>
> oh–i never logged a bug against kpackagekit in 11.4–and, now i wonder
> if no one did…have you two logged these 12.1 bugs?
>
Guilty - you got me
I just removed it without any further thinking about it, maybe not so
much a social act, but I did not even find it worth filing an upstream
bug for something I simply do not want
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
For kpackagekit we had/have the following situation with this problem
(novell bugzilla)
689002 is still new since april
679162 is still new since march
(it has a total of 69 bugs but for different things)
I do not even want to look up apper
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
On 11/21/2011 03:24 PM, Martin Helm wrote:
> I do not even want to look up apper
i held my nose and took a peek and found:
“40 bugs found.”
4 Critical
11 Major
4 Minor
17 Normal (what a strange category for “Severity”
OH man! a search on “apper” returns hits on “mapper” and probably other
variations of apper…so, i give up…
apper is broken and so is bugzilla search.
i find it frustrating!
–
DD
dump Flash: http://www.bbc.co.uk/news/technology-15797399
Yes, poor developers. It will be very difficult to beat YaSt/zypper after so many years of them coming to perfection. They are not halfway and almost nobody understands why they are doing it.
Bur more so the poor uers (especialy newbies, because old hands even do not try it) who are the guinee pigs.
> Yes, poor developers.
i probably wasn’t clear:
the openSUSE developers were/are aware that packagekit (and now apper)
is broken–so, why did they include it in the KDE package?
just remove it! and put in the middle of the screen a big flashing
notice saying the KDE thing was broken and removed, and to run YaST
Online Update every so often…
or just add a cron…or or or or or…or anything to alert the NOOB to
not use the broken bits which are known to kill a system…
> Bur more so the poor uers (especialy newbies, because old hands even do
> not try it) who are the guinee pigs.
well, we certainly do not need our newbies testing software which is
known to be broken prior to shipping…
that just does not make sense!
this is not rocket science: don’t ship software which is known to be
broken…
i mean, if all the 3.x kernels were broken, do you think they would
release 12.1 that wouldn’t boot…anyway??
–
DD
Exactly!
So why isn’t there a zypper based update applet?
What is the reason for using packagekit at all when we got zypper?
I really hoped i wouldn’t have to go to the commandline anymore with opensuse 12.1 to keep my system up to date.
Packagekit doesn’t respect the priority settings for repositories at all.
How hard can it be to get the dumb thing to run “zypper up” ?
On 11/21/2011 05:16 AM, gminnerup wrote:
>
> In other words: avoid, get rid of, disable, uninstall, whatever - but
> don’t use…
> Love 12.1, no real problems except for the above nuisance. Use YaST or
> zypper.
>
>
Thanks for that. I don’t use KDE often, but one of the first things I
did after the installation was to look for ‘kupdater*’ and
‘kpackagekit*’ in order to kill the beasties stone-dead. I could not
find them; yet I was bothered by the exactly same obnoxious and unwanted
behaviour as before, when trying to update while in KDE.
I’m a total newb with linux/openSUSE.
trying to install google’s chrome (which I use on my w7 machines, vista machine, and snow leopard box.
Keep running into apper’s failure.
And I see I should use YaST. OK.
How?
Just curious doesn’t Apper just come with KDE or is it in 12.1 by default?
I don’t use Gnome, so I don’t know if it’s in there too, that’s why I’m asking.
On 11/21/2011 11:26 PM, Operius wrote:
>
> So why isn’t there a zypper based update applet?
there is (kinda), it is called YaST Online Updater (YOU) and i’ve been
using it for years…
zypper is actually a CLI front end for the same back end that YaST
Software Management is a GUI front end for (libzypp, is the action for both)
> What is the reason for using packagekit at all when we got zypper?
there is no reason to use it…which is why i uninstalled it, and
recommend others do also…
For zypper patch you can do: YaST > Software > Online Update.
For* zypper up *you can do: YaST > Software > Software management. You can choose Repositories from the View menu (you may have allready a Reposirories Tab, that does the same). Then choose System, which will show all packages in the panel at right. Go there, and Right click. Choose All in this list > Update when e newer version is available.
You can also do this per repo by choosing that repo at left. When you have only OSS, nonOSS Update and Packman enabled, then you you can restrict to doing Packman only because the others will (normaly) not change (changes for OSS and nonOSS are in Update).
Don’t think Chrome is in the standard repos, at least I couldn’t find it the other day. Just download the RPM for openSUSE from Google, and then double-click on it. Uninstall Apper first.
On 11/22/2011 10:36 AM, gminnerup wrote:
> Uninstall Apper first.
+1 on that! otherwise i think it will try to take over!!
get rid of it, and the openSUSE YaST works will take over and install
Chrome…(i have both Chrome and Chromium [the beta/testing version of
Chrome] installed…
both use far less memory than FF…
–
DD
http://tinyurl.com/DD-Caveat
http://tinyurl.com/DD-Software
On 21/11/11 15:37, DenverD wrote:
>
> OH man! a search on “apper” returns hits on “mapper” and probably other
> variations of apper…so, i give up…
>
> apper is broken and so is bugzilla search.
>
> i find it frustrating!
I’d find it doubly so because the bugzilla search does something I need
in genealogy sites. A search on “robert*” is allowed but not “*bertson”.
Really annoying as I used to program this type of search quite easily in
Fortran77.
Pity Bugzilla doesn’t use wild cards in searches so that “apper” would
get “apper” alone and, if you wanted it, “%apper” would get “mapper,”
and “*apper,” “wrapper,” etc.
–
Graham Davis, Bracknell, Berks.
openSUSE 11.4 (64-bit); KDE 4.7.3; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
On 11/22/2011 01:41 PM, Graham P Davis wrote:
> Pity Bugzilla doesn’t use wild cards
it is an absolute pity that with so many ‘programmers’ around we here,
bugzilla, the wiki and i don’t know what else have to use absolutely
broken search engines…
–
DD
Dear posters,
This thread is becoming a bit of a mess. The original topic was a technical question about installing Chrome IIRC.
But it now seems more like a soapbox with subjects like apper (and family) and the search engines on some web-sites.
Please try to stay on topic.
There is at least one thread that is dedicated to the removal of apper/packagekit and your contributions are welcome there.
For the search engines, I hope you agree that this subforum for technical help on applications on openSUSE is the wrong place. Thus probably deminishing the chance that somebody that could do someyhing about it will read it.
On 2011-11-21 18:48, DenverD wrote:
>> Yes, poor developers.
>
> i probably wasn’t clear:
>
> the openSUSE developers were/are aware that packagekit (and now apper) is
> broken–so, why did they include it in the KDE package?
Because what is broken is the library that connect both to zypper. Apper
works correctly on other distros.
> –
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)