http://bugzilla.novell.com/show_bug.cgi?id=551662 User rpmcruz@alunos.dcc.fc.up.pt added comment http://bugzilla.novell.com/show_bug.cgi?id=551662#c1 --- Comment #1 from Ricardo Cruz 2009-10-31 12:09:45 MDT --- 3. List all -debuginfo and -debugsource packages that have installed associates. (see yast2-qt menu) 4. Allow the conflict solver to be manually temporarily suspended. (see yast2-qt menu) I haven't see references of users using this, but we should definitively implement this, if for no other reason than it's so easy to code. I am polluting this bug report with this one (since I don't think yast2-qt features it), but... 5. Have a list-box context-menu so that the user can enable columns such as "size". In particular, some properties are useful for sorting; use case: "sort the installed 'games' by size so I can remove the biggest offenders". 6. Not sure if yast2-qt makes use of this yet (I'm sure it will), libzypp now supports source packages. We should add a button so the user can install the respective source of a given package. Atri, I agree that we should promote as much feature parity with yast2-qt as possible, but this being a dysfunctional marriage, we'll always need some observant counselor such as yourself to keep the marriage afloat. ;) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551662 User rpmcruz@alunos.dcc.fc.up.pt added comment http://bugzilla.novell.com/show_bug.cgi?id=551662#c3 --- Comment #3 from Ricardo Cruz 2009-11-01 09:25:55 MST --- Sorry, but there is no way we can get this done for 11.2. Even if we ignore the lack of man-power, only crashes and data corruption may be fixed during this phase of the development cycle: http://en.opensuse.org/Roadmap/11.2 We already had to revert all fixes we've made since 11.1 (except for a potential crash) because we only managed to package yast2-gtk late in the cycle: bug 547075 (in particular UI changes that we couldn't easily dissociate from the rest of the work) I think we can pull off those features for the next opensuse major release though, and certainly I will keep post them to the Factory repository now that I was granted privileges to do so. By the way, I'm glad you liked my #5. I've other suggests under my sleeve, I'll share in a UI discussion I will try to promote over opensuse-gnome. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551662 User badshah400@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551662#c4 --- Comment #4 from Atri Bhattacharya 2009-11-01 09:35:03 MST --- I understand it is too late. Considering that the feature parity between the interfaces is strong though and that this was a feature request that was quite popular and closed as done so late into the cycle, will it not be possible to have #2 (orphaned packages) even as an online update? For 11.3 I hope the gtk interface goes several steps ahead of the qt interface. On my part, I can assure you that as soon as there are factory packages (or backports for 11.1, that would be cool) I will test them out and report my observations appropriately (either via this report or IRC). Thanks again. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551662 http://bugzilla.novell.com/show_bug.cgi?id=551662#c6 --- Comment #6 from Ricardo Cruz 2009-12-01 03:45:17 UTC --- What does #1 mean exactly? Is this the same as bug 541373? My understanding is that in yast2-qt when you would select a repository and then set a package for upgrade (or all in list), yast2-qt would ignore the fact that you have selected a repository and would upgrade the package from whatever repository featured the most recent version. This has been fixed on yast2-gtk since bug 386536. You should get a warning dialog if no upgrade exists in the server for a given package when multiple are selected. The warning let's you revoke or proceed with your changes. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=551662 http://bugzilla.novell.com/show_bug.cgi?id=551662#c8 --- Comment #8 from Ricardo Cruz 2010-02-13 07:10:18 UTC --- I added the "orphaned" packages support. Here's my comment about it though: http://groups.google.com/group/yast2-gtk/browse_thread/thread/02b43bd2dc1d3c... I thought that the new yast2-qt Orphaned packages filter was about showing packages (like libraries) that were rolled-in as dependencies for some user-installed package and could now be safely removed (since the package that the user installed had since been removed). It looks liked "Orphaned" is only a fancy name for packages that are now unmaintained. "unmaintained" or "discontinued" seem like more self-evident names, don't you think? Thomas? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.