On 04/10/2011 11:47 AM, Greg KH wrote:
On Sun, Apr 10, 2011 at 10:23:02AM -0700, Ken Savage wrote:
What I'm wondering about is the discrepancy I see in the list of packages that will be upgraded when I issue a plain "zypper dup" compared to the TW-based list of packages. Fair enough that my Packman and VLC repos might have some newer files than what has managed to be CONFIRMED to be working in TW.
I don't understand, what do you mean by "discrepancy" here? Please show examples.
Because I have other repos accessible, it's clear that when I restrict myself to a dup from TW, it will not be looking at the same range of versions as with a dup against the full list. This is the discrepancy I am referring to.
But are the openSUSE BuildService repos more cutting edge than TW as well? What about the 11.4 Upgrades repo (/update/11.4) ?
It depends on the package.
And therein lay the main reason I get the bigger list when I dup against all repos containing a variety of BuildService items.
All other repos should be removed, unless you explicitly want to pull from them _instead_ of tumbleweed or anywhere else.
Don't have any other repos other than Tumbleweed and the base 11.4 update repos. That's what I'm supporting, anything else you do you do so on your own :)
ie: Not even the 11.4 Main repository? ... and then you simply "zypper dup" (as opposed to --from Tumbleweed) against that very restricted set of repos? I think that caveat should be posted to the Tumbleweed portal page. As it stands, it says to add the repo, and zypper dup --from it. I think it would be a good call to add something along the lines of "... other repositories such as those on openSUSE BuildService list, the Main, Contrib, VLC and Packman should be disabled to avoid package conflicts or unsupported system configurations..." Ken -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org