On 04/30/2015 06:48 PM, Wolfgang Rosenauer wrote:
Am 30.04.2015 um 10:30 schrieb Marcus Meissner:
On Thu, Apr 30, 2015 at 10:18:14AM +0200, Torsten Gruner wrote:
I think so, too.
Another solution might be to mark the affected packageswith this kind of changes. And each packet has to be assessed whether a jump to the next version without consequence for the function. Can several versions are skipped? And zypper has to handle this. This is a nice feature but a dream only.
What do you mean with affected packages?
We try to push out only "stable" and working tumbleweed snapshots and that seems to be working quite well already.
My Laptop is running Tumbleweed and I have so far not have had a single troublesome status.
Since I'm afraid of putting TW on a production machine I decided to try it in VirtualBox for quite some time (I reported issues earlier) and I can only say that still every other TW update will leave my VirtualBox TW installation unusable. Usually no X coming up anymore. My confidence in TW as a working horse is really quite low while I had actually some hopes in it.
Well, but TW is not really intended to run on a "production" server. TW is targeted at developers that want the latest of X and do not mind getting the latest of Y in the process. On a personal note I run TW on my laptop as it gets frequently rebooted anyway, but do not rnu TW on my desktop as I hate rebboting that machine. Simply it takes me 1/2 hour to get all my workspaces and terminals and and and back to the state before the reboot. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org