Mailinglist Archive: opensuse-bugs (10806 mails)

< Previous Next >
[Bug 548089] Qt sw_single hides vendor change updates
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 20 Oct 2009 09:08:43 -0600
  • Message-id: <20091020150844.01D94245513@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=548089

User sven.burmeister@xxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=548089#c11


Sven Burmeister <sven.burmeister@xxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |sven.burmeister@xxxxxxx




--- Comment #11 from Sven Burmeister <sven.burmeister@xxxxxxx> 2009-10-20
09:08:42 MDT ---
As mentioned here: https://bugzilla.novell.com/show_bug.cgi?id=538308#c5

this does not work as expected. If a user only wants to install/update single
packages from a repo, he selects those single packages and YaST sorts out the
deps.

If a user however wants to update all packages, he expects YaST to do exactly
that.

If one selects an obs repo in YaST and picks "all packages in this list" and
then "update if newer version available" that adds up to:

1. use the selected repo -> vendor change
2. apply whatever is chosen to all packages in the repo
3. update if a newer version is provided

3. does not read: update if a newer version is provided but no vendor change
needed.

As long as YaSt does not obey what the user selected from the menus, there is
either a bug in YaST because it does the wrong thing or because the menu items
do not mediate what they do.

Further, while this feature might be useful for repo x, it is not for repo y.
Even more so, it might be useful for repo x and person y, yet repo x and person
z does want to update all packages. There is no one size fits all for all repo
+ user combinations.

Thus whatever the default is, the user should be able to change the setting
within YaST to his needs.

--
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.

< Previous Next >
References