https://bugzilla.novell.com/show_bug.cgi?id=373165 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=373165#c1 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ckornacker@novell.com, sh@novell.com, | |tgoettlicher@novell.com --- Comment #1 from Ján Kupec <jkupec@novell.com> 2008-03-28 14:32:04 MST --- (In reply to comment #0 from Elmar Stellnberger (AT/K))
It should be possible to execute certain basic control operations like zypper red pkg-source // refresh package source zypper mr -d pkg-source // disable package source zypper mr -e pkg-source // enable package source while y2base sw_single is running.
Implementing finer grained locking would allow for using zypper refresh while yast2 sw_single is running, but it would also need a notification mechanism to which yast would listen in order to reload the newly refreshed metadata (e.g. to show the up-to-date pattern content). While the locking is a good idea (and we currently work on it), i doubt the notification and handling of such events is worth doing.
Issuing these actions fromout of the installation sources selection in the left sidebar of 'y2base sw_single qt' would of course be more convenient.
This would be a feature request for the yast2 packager, but i think something like this is already done in the latest 11.0 Alpha3, Stefan?.
The OpenSuse-Upgrader should as well notify such a change automatically At the moment it does not even refresh its upgrade-list on modifications via the 'Add/Remove Update-Sources' button.
The list of repositories used by openSUSE Updater is another thing since the updater is supposed to run all the time, hence it would be nice if it used the most recent list of repos. But that's another bug/enhancement request worth another bugzilla entry (try to stick with one bug per bugzilla entry). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.