On Sunday 05 November 2006 11:24, John Andersen wrote:
On Saturday 04 November 2006 23:15, Anders Johansson wrote:
<sigh> How is one to know that it is only a bug?
One files a bug, saying it shouldn't work this way, and one is then told whether it is intentional or not.
Yeah, like that might work.....
1)Wait till distro does something stupid (dump YOU or rug/zmd) 2)File Bug report asking for YOU back 3) ......silence
This has been discussed. The old Online Update was broken too, in that it lacked a lot of functionality. Going back to it was never going to be an option Bug reports were filed against the new updater (since it too was broken) and they were dealt with. In 10.2, things are much better, between zypper and opensuse-updater you will never see the "Waking up ZMD" message again, things are actually fast, while still providing the same benefits of the new rpm-md based system But that YaST Online Update was dropped was announced publically. Filing a bug report to get an announced change reverted is not going to do much, when the stated focus is on getting the new system working. Something that is in the distro that looks like it's broken, on the other hand, is a valid bug report. In Basil's case there were two options. Either the hardware info really had to be sent (in which case it would be a bug to see the checkbox at all) or the checkbox should be de-selectable. In either case, a valid bug Incidentally, a long while ago something similar happened. SuSE (as it was then) started using ACPI 'for real', causing many systems - including my own - to fail miserably, unless obscure boot parameters were used. The statement then was something to the effect of it has to be done, otherwise we'll never get ACPI working properly