On Thu, Dec 09, 2010 at 05:50:30PM +0100, Adrian Schröter wrote:
On Thursday 09 December 2010 08:15:14 Greg KH wrote:
On Thu, Dec 09, 2010 at 12:13:31PM +0100, Michael Schroeder wrote:
Anything I can do to the repo to keep this from happening?
Either configure that the vendor is equivalent to opensuse or use 'zypper dup'.
Hm, how could I get my repo to have the same id as the opensuse vendor? Or is that something that I shouldn't be trying to do?
When you consider Tumbleweed as save update repository (just larger than the usual default Update repo) using the openSUSE vendor should be fine.
If you consider Tumbleweed more something like in the middle of 11.3 and Factory, not really 100% safe for your grandma, you should not use the same vendor. Otherwise the user will not get notificated about a switch of a package and he has no chance to stay on the stable side.
Good point.
This where I still have no clear picture of tumbleweed atm, I thought it is the first (the safe update path), but it seems to me atm it isn't.
It's a completly unsafe test at the moment which might break your machine :) But we are working through the issues, give us time to figure it out. Hopefully by the time 11.4 is out we will have a handle on it. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org