On Fri, Apr 01, 2011 at 12:22:16PM -0400, Greg Freemyer wrote:
All,
Is there a simple way security updates can be tested to install cleanly on a Tumbleweed system?
Can we make that part of the process somehow?
No, that's not up to the security or maintance people, that's up to the tumbleweed developers.
== details
I just tried to do a YOU, but I get a conflict that a typical user should not have to face just because they're using Tumbleweed:
What's a "YOU"?
=== #### YaST2 conflicts list - generated 2011-04-01 11:29:43 ####
patch:python-virtualbox-4219.noarch conflicts with virtualbox-qt.x86_64 < 4.0.4-1.6.1 provided by virtualbox-qt-4.0.4-1.2.x86_64
What is causing this conflict? What is "python-virtualbox"? Does it not come from the main virtualbox repo? If not, it looks like just adding it to tumbleweed would resolve the issue, right?
[ ] Following actions will be done: install virtualbox-qt-4.0.4-1.6.1.x86_64 (with vendor change) obs://build.opensuse.org/openSUSE:Tumbleweed --> openSUSE install virtualbox-4.0.4-1.6.1.x86_64 (with vendor change) obs://build.opensuse.org/openSUSE:Tumbleweed --> openSUSE [ ] do not install patch:python-virtualbox-4219.noarch
#### YaST2 conflicts list END ### ==========
If I revert virtualbox-qt to the OSS version, it will break due to a kernel incompatibility I'm pretty sure.
Because I know that, I can choose not to install the patch:python-virtualbox-4219.noarch.
For me it's not that big an issue, but it is not knowledge a typical user has.
Why not? What's the "typical" tumbleweed user? :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org