On Thu, 9 Dec 2010, Cristian Morales Vega wrote:
2010/12/8 Greg KH
: I have it populated with only 3 packages at the moment, and it's building against 11.3.
I added the repo to zypper, but when trying to do an update on a package that I know is newer, I get the following error from zypper: There is an update candidate for 'git', but it is from a different vendor. Use 'zypper install git-1.7.3.2-43.1.i586' to install this candidate.
Now I don't really want to have to have every user do this by hand for each package that gets added to tumbleweed, so how do I get this to be automatically overridden due to the fact that the 'git' package really is newer, and it should be installed.
Note, when running 'zypper dup' it says that there is nothing to do, I only get the above message when explicitly asking that git be installed, eventhough git is installed.
Anything I can do to the repo to keep this from happening?
I didn't follow all the Tumbleweed thing. There will not be installation medias? People is supposed to install openSUSE "normal" version X and from there pass to Tumbleweed?
Yes, I think the install needs proper testing so is best left to a release. OTOH I saw tumbleweed as something that would track factory sources (with a delay) and does not build against any other repository. When factory approaches a openSUSE release tumbleweed would naturally sync itself to that release. Thus, do you really want to keep a tumbleweed for each openSUSE release? That wouldn't be exactly like a rolling release but more like a backports repository. So - I really want a Debian testing equivalent for openSUSE (ok, I want a unstable equivalent, but then people might say Factory does provide that). Richard.