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.
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.
Günter
Desk: Tumbleweed, KDE 5, AMD Ryzen 5 3400G, 16Gb, 120Gb SSD, 2 SATA.
Lap: Thinkpad T430, Tumbleweed, Intel i5, 8Gb, SSD.
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.
Henk van Velden
> 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.
Bookmarks