[opensuse-factory] Expected usage of Tumbleweed?
Hi folks, I had added Tumbleweed to my repo list waaaay back in the 11.3 days (can you *remember* those days!!? ;) .... and continued with it when I upgraded to 11.4. And certainly it works: if I zypper dup --from Tumbleweed, the latest shiny TW packages find their way into my system. 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. But are the openSUSE BuildService repos more cutting edge than TW as well? What about the 11.4 Upgrades repo (/update/11.4) ? I guess my question boils down to this: Having added TW as a repo, are there other repos that I should make sure are deactivated, and from here forward, merely do zypper dup's from the TW repo? What's the generally anticipated usage pattern of a sysadmin who has hooked themselves into Tumbleweed? Many thanks for your thoughts, Ken -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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.
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.
I guess my question boils down to this: Having added TW as a repo, are there other repos that I should make sure are deactivated, and from here forward, merely do zypper dup's from the TW repo?
All other repos should be removed, unless you explicitly want to pull from them _instead_ of tumbleweed or anywhere else.
What's the generally anticipated usage pattern of a sysadmin who has hooked themselves into Tumbleweed?
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 :) Hope this helps, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
On Sun, Apr 10, 2011 at 12:31:41PM -0700, Ken Savage wrote:
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.
Well, that's pretty obvious then, right? :)
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.
Exactly.
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?
Sorry, no, the "11.4 repos that got installed on your system" is a good way to summarize all 4 of them.
... and then you simply "zypper dup" (as opposed to --from Tumbleweed) against that very restricted set of repos?
That works for me.
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..."
Well, Main is fine. I have no idea about Contrib as that should be pulled into Factory and then Tumbleweed if you really want the packages and use them. Packman you are always on your own as I can't support that at all, and I don't know what VLC is. And all of this is always "unsupported" on one level or another, in the end, it's just supported the best that we can on an individual level. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/11/2011 05:40 AM, Greg KH wrote:
On Sun, Apr 10, 2011 at 12:31:41PM -0700, Ken Savage wrote:
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.
Well, that's pretty obvious then, right? :)
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.
Exactly.
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?
Sorry, no, the "11.4 repos that got installed on your system" is a good way to summarize all 4 of them.
... and then you simply "zypper dup" (as opposed to --from Tumbleweed) against that very restricted set of repos?
That works for me.
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..."
Well, Main is fine. I have no idea about Contrib as that should be pulled into Factory and then Tumbleweed if you really want the packages and use them. Packman you are always on your own as I can't support that at all, and I don't know what VLC is.
And all of this is always "unsupported" on one level or another, in the end, it's just supported the best that we can on an individual level.
thanks,
greg k-h
VLC is a well-adopted media player. I see it multi-referenced in the support forums and use it almost exclusively myself. Mine stopped working (no sound but video is fine) when I upgraded from 11.4 to Tumbleweed. VLC's silence is the only problem I've had with Tumbleweed (apart from my own confusion with repos which this thread has now cleared up -- thanks). My VLC comes originally from 11.4 Packman and it's the same as the VLC RPM in Tumbleweed_Packman, and it fell silent when I did "zypper dup --from Tumbleweed". Thanks, John -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Apr 11, 2011 at 08:22:55AM +1000, John Andrews (swerdna) wrote:
"... 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..."
Well, Main is fine. I have no idea about Contrib as that should be pulled into Factory and then Tumbleweed if you really want the packages and use them. Packman you are always on your own as I can't support that at all, and I don't know what VLC is.
And all of this is always "unsupported" on one level or another, in the end, it's just supported the best that we can on an individual level.
thanks,
greg k-h
VLC is a well-adopted media player. I see it multi-referenced in the support forums and use it almost exclusively myself. Mine stopped working (no sound but video is fine) when I upgraded from 11.4 to Tumbleweed. VLC's silence is the only problem I've had with Tumbleweed (apart from my own confusion with repos which this thread has now cleared up -- thanks).
I know of VLC the program, I didn't realize it was also referred to as a whole repo, as it was done so above.
My VLC comes originally from 11.4 Packman and it's the same as the VLC RPM in Tumbleweed_Packman, and it fell silent when I did "zypper dup --from Tumbleweed".
We updated a number of multimedia libraries in Tumbleweed this week, so perhaps that caused the problem? Maybe VLC needs to rebuild now, as it probably will if the Packman dependancy chain is set up correctly, and that will resolve your issue. If not, please let the developers know. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2011/4/11 Greg KH
On Mon, Apr 11, 2011 at 08:22:55AM +1000, John Andrews (swerdna) wrote:
"... 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..."
Well, Main is fine. I have no idea about Contrib as that should be pulled into Factory and then Tumbleweed if you really want the packages and use them. Packman you are always on your own as I can't support that at all, and I don't know what VLC is.
And all of this is always "unsupported" on one level or another, in the end, it's just supported the best that we can on an individual level.
thanks,
greg k-h
VLC is a well-adopted media player. I see it multi-referenced in the support forums and use it almost exclusively myself. Mine stopped working (no sound but video is fine) when I upgraded from 11.4 to Tumbleweed. VLC's silence is the only problem I've had with Tumbleweed (apart from my own confusion with repos which this thread has now cleared up -- thanks).
I know of VLC the program, I didn't realize it was also referred to as a whole repo, as it was done so above.
http://download.videolan.org/pub/pub/videolan/vlc/SuSE/
My VLC comes originally from 11.4 Packman and it's the same as the VLC RPM in Tumbleweed_Packman, and it fell silent when I did "zypper dup --from Tumbleweed".
We updated a number of multimedia libraries in Tumbleweed this week, so perhaps that caused the problem? Maybe VLC needs to rebuild now, as it probably will if the Packman dependancy chain is set up correctly, and that will resolve your issue. If not, please let the developers know.
The build server is building against the latest libraries, but it's not being published (from http://packman.inode.at/suse/openSUSE_Tumbleweed/repodata/, it was updated on March 17th) because some kind of bug. So you can expect any kind of problem using those packages... No idea about when it will be fixed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/11/2011 12:22 PM, Greg KH wrote:
On Mon, Apr 11, 2011 at 08:22:55AM +1000, John Andrews (swerdna) wrote:
"... 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..."
Well, Main is fine. I have no idea about Contrib as that should be pulled into Factory and then Tumbleweed if you really want the packages and use them. Packman you are always on your own as I can't support that at all, and I don't know what VLC is.
And all of this is always "unsupported" on one level or another, in the end, it's just supported the best that we can on an individual level.
thanks,
greg k-h
VLC is a well-adopted media player. I see it multi-referenced in the support forums and use it almost exclusively myself. Mine stopped working (no sound but video is fine) when I upgraded from 11.4 to Tumbleweed. VLC's silence is the only problem I've had with Tumbleweed (apart from my own confusion with repos which this thread has now cleared up -- thanks).
I know of VLC the program, I didn't realize it was also referred to as a whole repo, as it was done so above.
My VLC comes originally from 11.4 Packman and it's the same as the VLC RPM in Tumbleweed_Packman, and it fell silent when I did "zypper dup --from Tumbleweed".
We updated a number of multimedia libraries in Tumbleweed this week, so perhaps that caused the problem? Maybe VLC needs to rebuild now, as it probably will if the Packman dependancy chain is set up correctly, and that will resolve your issue. If not, please let the developers know.
thanks,
greg k-h
Thanks for the clues. So I re-looked and switched thus: gstreamer and its buddies <=> Packman All of Tumbleweed taglib <=> Tumbleweed libtag-extras1 <=> Packman All of Tumbleweed And that gave VLC its audio back. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Cristian Morales Vega -
Greg KH -
John Andrews (swerdna) -
Ken Savage