Hello,

Am Samstag, 4. November 2006 18:18 schrieb Christoph Thiel:
> while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals),
> I thought it might be a good idea to ask for some help regarding bug
> prioritization.

My candidates:

https://bugzilla.novell.com/show_bug.cgi?id=216485
opensuse-updater shows error message in tooltip
zypp-checkpatches-wrapper does not get the suid-root bit if running with 
permissions.secure. This makes opensuse-updater unuseable.
Please reconsider the settings for permissions.secure (or remove zmd 
when running with permissions.secure - I consider its broken permission 
concept more critical ;-)

https://bugzilla.novell.com/show_bug.cgi?id=148105
no error message when RPM database is missing
YaST silently switches to "new installation" mode if I start in upgrade 
mode with the RPM database not available. There should be an error 
message that informs the user about the switch to "new installation" 
mode and the reason for it.
Probably easy to fix (add the error message), and can avoid some 
problems.

https://bugzilla.novell.com/show_bug.cgi?id=166881
solver should provide "dont delete $otherpackage" as possible conflict 
solution.
This one could avoid several conflict messages. However, I'm not sure if 
it should be done at this late stage of development :-/

https://bugzilla.novell.com/show_bug.cgi?id=171082
YaST2 AppArmor report module should use radio buttons instead of 
checkboxes for archived reports
"Just" an enhancement, but a usability problem and probably easy to fix.

I also vote for fixing all bugs that have a patch attached already.


Regards,

Christian Boltz
-- 
Wünschenswert wäre es auch, wenn Umfragen vor jeder Bundestagswahl,
ob die Erst- oder die Zweitstimme die wichtigere sei, wenigstens
soviele richtige Ergebnisse zeitigten, als würde man die gleiche
Anzahl Schimpansen befragen. ;)  [Bernd Brodesser in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to