Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: Kevin Miller <millerboys@xxxxxxxxxxxxx>
- Date: Wed, 16 Jan 2008 16:43:20 -0900
houghi wrote:
That I would not call 'automatic'. I would not even call that
semi-automatic. As far as I can tell, you decide on each package.
Sure, but I don't have to search for them. The system lets me know when
there's a new package. If they're small I can kick them off and not be
impacted. If it's something like a kernel update I can put it off and
not burn up my bandwidth.
Then it is strange that you do not use it. What crontab can do, you can
do as well. I think it strange if you are bothered by something that
should be running in the background.
Updates do pretty much run in the background. But they consume
bandwidth. The load on my system may be minimal, even at the same time
the load on my connection is maxed out.
It's also nice to be able to hold off on an update too. You may or may
not remember a couple months ago, but the java update was completely
borked. Unfortunately I installed it before anybody complained.
/etc/alternatives was full of broken sym links, and it took me several
hours to manually fix them. I wish I'd read here that the java update
was broken - it would have saved me a lot of trouble.
Although I still got bit, at least with manual update selection one has
the chance of preventing such problems. You've been here long enough to
know it's not the first bad update either. I'm sure every distribution
has them now and again - I'm not picking on SUSE developers and
packagers here.
In this case it DOES imply some knowledge.
Knowledge of the result perhaps, not necessarily the cause.
And do you have ANY idea as to why this is? Probably not. And that is
Not at a technical level. At a very superficial level I think it is due
ot the merging of the red carpet mechanism with the historical mechanism
in YaST/YOU.
where you can mingle in the discussion. There is a reason that this is
happening. Perhaps that reasonm is completely uninteresting for you and
you might want them to drop it.
You hit the nail on the head. I want it to 'just work'. I don't think
that's unreasonable.
OTOH if they hear nothing and get no feedback, they know that they are
on the right track and will continue that way.
Yeah, kind of a catch-22 isn't it.
To me speed is absolutely irrelevant as I already pointed out. Other
things are much mre important to me. Things that were not there in 8 or
in others.
Sure - we all have different needs and expectations. I'm all for new
features and programs as well. Otherwise we'd all still be on 8.
Great idea. So what did the developers make of this idea?
Beats me.
Again, might well be possible but _I_ do have not problem with it. And
there is, again, no reason to keep repeating that here. Tell that to the
developers on either Bugzilla or the mailinglist. Ask them perhaps first
if they are working on it already and where you can find information on
what they are doing.
As Rajko mentioned on messages further down the thread, they're aware of
it and working on it. You might not have a problem with it. That's not
a reason that those of us here that do shouldn't mention it.
As a matter of fact, last night I reported the timidity problem on
Bugzilla.
Great. What is the bugnumber? Just curious.
https://bugzilla.novell.com/show_bug.cgi?id=353816
To me that procedure was so long ago, I do not rememebr anymore. What I
can rememebr it was not that different from what I have done on other
sites.
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 went
to the trouble because I want to see timidity fixed. If the developers
really want feedback from the great unwashed masses it has to be simple
and convenient. Sort of like what Dell did with their ideastorm. They
got lots of feedback really fast.
Yes. Perhaps they can reproduce it or have a way of getting reports. The
worst that can happen is that they say: sorry we can not reproduce it,
we will close it as WORKSFORME.
I have reported bugs that were closed because they found nothing wrong.
I have reported enhancements that took 2 versions to be implemented
(because it was not realy importand) and I have reported things that
were implemented and resolved almost right away.
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.
S'later...
....Kevin
--
Kevin Miller
http://www.alaska.net/~atftb
Juneau, Alaska
Registered Linux User No: 307357
.
- Follow-Ups:
- Re: Repository 'openSUSE-10.3-Updates' is invalid
- From: houghi
- 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
- Repository 'openSUSE-10.3-Updates' is invalid
- Prev by Date: 10.3 hangs after suspend - update
- Next by Date: Can't get kernel updates to install
- Previous by thread: Re: Repository 'openSUSE-10.3-Updates' is invalid
- Next by thread: Re: Repository 'openSUSE-10.3-Updates' is invalid
- Index(es):
Relevant Pages
|