Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi <houghi@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 19 Jan 2008 13:36:43 +0100
Kevin Miller wrote:
houghi wrote:
I do not update my kernel automagicaly. I do not update anything that
needs my attention. I will read it when I get the mail that it wasn't
updated and then, once a month, do it.
Guess I'm still not clear on exactly what mechanism you're using here.
Is this a script that you wrote or configuration options w/in the
auto-update YaST module?
Standard YaST update module
Well sure. But folks w/bandwidth to burn don't care so if a big patch
is coming done the wire they don't notice much of an inmpact. I, on the
other hand, have a bottom end DSL connection shared w/my family. An OOo
update combined with youtube just about kills any kind of response rate.
On the other hand, it does give one time to go to the kitchen and get a
beer. ;-)
So how do you know how large the updates are? Also I can imagine
(although I have no idea how to do it) that you can do QOS so it leaves
enough bandwith to be able to see your_tube. Downside will be that it
will become slower.
Then you would have known that the update was borked? I doubt that. I
think you would just have clicked OK and had the identical problem.
Sometimes you beat the reaper, sometimes you don't.
So how often have you avoided updating malicious updates by doing it
manually? What are the updates you do NOT update? My guestimate on
answering that would be 'no bad updates were avoided' and 'I do not
update the kernel all the time'. And that is exacly what I do ass well
automagicaly. ;-)
LOL. When one jumps into one of these threads, rarely does one expect
it to turn into something rivaling Dostoevsky. Sigh. :-)
Kafka will be so proud of us. :-D
It is also no reason to give feedback to the developers.
I dunno - it's a fine line between useful input and background noise, me
thinks.
It is up to the developers to make that difference and they have stated
that they ather have a lot of background noice then miss one bug. Just
after openSUSE.org started they had 3 times as many bugreports and they
were happy about it. As long as you can produce a reasonable bugreport,
they will be happy. Oalso if you have a bugreport stating just "It does
not work" or "OPENsuse sucks" it will be closed fastere then it to the
electrons to send over that message.
However if you are a serious heavy bugzilla user you can use
http://almworks.com/deskzilla/overview.html Unfortunatly not OSS and not
free. I do not use it, but it might be handy for others.
https://bugzilla.novell.com/show_bug.cgi?id=353816
Seee how they listen and work when you give feedback?
Sure. Still not fixed yet, but there's a guy looking into it.
Perhaps not. It is sufficiently enough of a hassle that it isn't
readily convenient and that is off-putting to the average user.
I am the average user as well.
I went to the trouble because I want to see timidity fixed.
So you do not want the speed problem you experiecne to be fixed?
Of course, but you and I both know (and have known all along that it's
an issue that they're aware of. But let me ask you this in all
seriousness - how does one report that. The Timidity problem was easy -
specific program and symptoms I could demonstrate. But what sort of bug
report does one open for updating. I mean, one can't just get on and
say 'um guys, updating sucks. It's way slower than apt or even 10.0.
Fix it.'
What kind of feedback is actually helpful to them in that situation from
a guy that's willing to invest 5 or 10 minutes here or there but doesn't
want to make it his life's crusade? I'm looking for specific
constructive guidance here, not just demagoguery and pontificating.
What do you loose by reporting the bug?Fair enough. Since I've already gone through the trouble of signing up
it isn't that much of a stretch to open another case.
W00T!. :-D
Sadly, they closed the ticket with a WONTFIX. Not surprised. They
noted that I got the download from packman and blamed it on audacity.
So back to square one. Maybe my install is just borked. I dunno. Or
maybe it's something I installed somewhere along the line. Or maybe
it's my hardware or??? Hard to say. As it stands I can't use it and
don't have any method/guidence for fixing it. Bummer...
...Kevin
houghi
--
I do not want life insurance.
I want all people to be genuinely grieving when I die.
houghi
.
- Follow-Ups:
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- References:
- Repository 'openSUSE-10.3-Updates' is invalid
- From: mjb
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Michael Soibelman
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Chris Cox
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Nikos Chantziaras
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Chris Cox
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller
- Repository 'openSUSE-10.3-Updates' is invalid
- Prev by Date: Re: Yast
- Next by Date: Re: partitions on a suse 10.2 installation....
- Previous by thread: Re: Repository 'openSUSE-10.3-Updates' is invalid
- Next by thread: Re: Repository 'openSUSE-10.3-Updates' is invalid
- Index(es):