On 2006/12/02 23:13 (GMT+0100) Andreas Hanke apparently typed: > Felix Miata schrieb:
>> The updater installed software that was already installed, a substantial >> unnecessary load on mirrors, and waste of my time waiting for the >> unnecessary download from an already slow mirror. > Now I finally got what it's about: You installed the -33 kernel and YaST > downloaded and installed the same kernel again. > The only way I can imagine this not being a bug is that the "rpm -i" has > been done while YaST was already running. That way YaST won't notice the > change because it reads the rpmdb on startup and doesn't lock it. It's possible I may have left YaST open while doing the manual kernel install the first time, but today I tried again without forgetting to reboot before updating. > You might want to file a bug about this. Of course you will attach the > logfiles. https://bugzilla.novell.com/show_bug.cgi?id=225674 >> It's disappointing to find so much reported weeks or months or close to >> a year ago in bugzilla that didn't get fixed before 10.2 "release" state >> was achieved. There's one in particular I reported against 10.0 (and >> reproduced on at least 4 entirely different systems using 10.0, 10.1 & >> factory) long before 10.1's first beta that remains unfixed now. I've >> lived with it on my 24/7 box nearly a year now. Likely that box will see >> 10.0 replaced with Mandriva 2007 soon in order that I can stop being >> constantly annoyed by it. > A general hint: Posting that to this list without the Bugzilla ID > doesn't really bring the community any further. Writing something like I already raised the issue on the mailing list and don't believe any more can be expected from the community, nor do I want to look like I'm bashing the assignee in a public forum. > "I'll switch to Mandriva" is very demotivating because it basically I'll switch means the severity of the annoyance is too high. The two distros are nearly equivalent in meeting my needs. Without this bug and one other I haven't even bothered to report, SUSE would remain my preference. I think two releases without a fix is justification for giving up. > means that the bug doesn't need to be fixed because the only user > annoyed by it doesn't use the product anyway. This is very > counter-productive. I'm not the only user observing the problem, as you can see reading the bug and reading the mailing list discussion about it. I imagine there must be users who are not bugzilla participants or mailing list subscribers who see it too, and may not even know what's going on. > You might, instead, try to be cooperative, i.e. show that you're still > interested in the bug being solved by moving it to the next product > and/or trying to fix it yourself and attaching a patch or a pointer into > the right direction. E.g. by looking at source packages of other > distributions where it works, finding out the difference and telling the > assignee about it. I'm not a programmer, so I won't be providing any patch. If the bug's assignee wants assistance, he needs to indicate so more than simply stating he is unable to reproduce. > Might be considered frustrating, but at some point every community > member has to learn that there are bugs which will never be fixed. This > is common to all open source projects. I just tried to find a 2 years > old, unfixed bug in Mandriva's Bugzilla and of course it was a piece of > cake finding one. Some bugs one can live with, others not. One can only scratch so many times before drawing blood. That's not healthy. > Btw. I know that it's about #141443 because it's the only one you have > reported against 10.0 that is still open. In that case it's really > unfortunate, but as long as an engineer is unable to reproduce it, it's > simply impossible to get it fixed. I have reproduced it on about 5 or 6 hardware systems using 10.0 and 10.1 and 10.2, which means 100% of about 10 different installs exhibit the problem. Others have reported reproducing it both in the bug and on the mailing list, so probably this has been reproduced and reported on well over a dozen different systems. I think that's enough to indicate an engineer with sufficient interest and time should be able to reproduce it somehow. I do as much as practical using several ttys. X is not my environment of choice, but necessary for graphics and normal web use. So, this bug hits me constantly. A year is just too much, and soon it will be a year. Switching from SUSE seems to be the only option I have to deal with it. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
