Thanks a lot, Greg for the reply, I was hoping for one from you. Just to get things clear: could you please write a small explanation on how things are going to be for those already running Tumbleweed/11.4 ?
On 26.10.2011 18:36, Winux2 wrote:
>
> mleun;2396547 Wrote:
>> Should’t there be a /update/current then, so one can even point update
>> to current - or is update not needed at all with tumbleweed?
>>
>> EDIT: And what about source? Shouldnt there be a /source/current?
>
> Good news… Tumbleweed will require its current users to make one
> manual change to the repositories upon the 12.1 release. After which,
> the openSUSE servers will automatically handle the required changes upon
> a new release, transparent to the users. Thanks to all for making it
> so!
>
> -Details here>- ‘openSUSE:Tumbleweed 12.1change - openSUSE’
> (http://en.opensuse.org/openSUSE:Tumbleweed_12.1change)
>
>
And just the other day Greg KH stated that pointing to “current” is (has
been long) the way to go and no other changes are unnecessary.
Except “update” repo. But this is a bug that should be reported.
I have mine like this:
| Alias | Name | Enabled |
Refresh
–±--------------------------±--------------------------±--------±-------
1 | Packman | Packman-Tumbleweed | Yes |
Yes
2 | Tumbleweed | Tumbleweed | Yes |
Yes
3 | Updates_for_openSUSE_11.4 | Updates for openSUSE 11.4 | Yes |
Yes
4 | openSUSE-11.4-Debug | openSUSE-11.4-Debug | No | No
5 | Non-Oss | openSUSE-CURRENT-Non-Oss | Yes |
Yes
6 | Oss | openSUSE-CURRENT-Oss | Yes |
Yes
Vahis
http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.7-default main host
openSUSE 12.1 RC 1 (x86_64) 3.1.0-rc9-1-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.7-45-desktop “Tumbleweed” in EeePC 900
Hmm… Since there’s no mention of the repos you posted here> Portal:Tumbleweed - openSUSE nor here>** openSUSE Forums - swerdna howto upgrade openSUSE 11.4 to Tumbleweed**, how would a reader/user know how to replace the base repos of 11.4 with the long used “current” repos?
For the 12.1-final release using “Tumbleweed” repo, should “current” repos still be used vs “stable” as stated here> openSUSE:Tumbleweed 12.1change - openSUSE which includes the “update” repo, unlike the “current” repo?
On 26.10.2011 20:16, Winux2 wrote:
>
> Vahis;2397602 Wrote:
>
> Hmm… Since there’s no mention of the repos you posted -here>-
> ‘Portal:Tumbleweed - openSUSE’
> (http://en.opensuse.org/Portal:Tumbleweed) -nor here>-* ‘openSUSE
> Forums - swerdna howto upgrade openSUSE 11.4 to Tumbleweed’
> (http://tinyurl.com/622bsev)*, how would a reader/user know how to
> replace the base repos of 11.4 with the long used “current” repos?
If you read this thread a little, you can find this:
"The Tumbleweed repo will stay in the same location, it will just be
based off of 12.1 instead of 11.4. So nothing needs to be changed
there at all, it’s up to me to handle the packages properly.
I’d recommend pointing your 11.4 repo to the “current” repo, so when
12.1 comes out, everything, including Tumbleweed, will update properly
with no problems.
Hope this helps,
greg k-h
That is from two days ago.
P.S. The author is the Thumbleweed creator and developer.
Vahis
http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.7-default main host
openSUSE 12.1 RC 1 (x86_64) 3.1.0-rc9-1-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.7-45-desktop “Tumbleweed” in EeePC 900
rotfl! Someone is paying attention!
Thanks for updating web page: openSUSE:Tumbleweed 12.1change - openSUSE by changing the wording in the repos from “stable” to “current”. And as I noted earlier, the “update” repo has changed and is now “current” (pun intended).
There you have it openSUSE “Tumbleweed” fans! Now we know where to find the answer, to the question of what repos (IP address included) to use. click here> openSUSE:Tumbleweed 12.1change - openSUSE
On 10/26/2011 09:06 PM, Winux2 wrote:
>
> (http://en.opensuse.org/openSUSE:Tumbleweed_12.1change)*
if i might make one small suggestion on that page: there is quite a
number of folks who run openSUSE today and will want to run Tumbleweed
as soon as they get the courage 
…but, some of them will not be
familiar with the ‘universal’ backslash code notation for “wrap here”
used in the command line instructions… (just like in Linux Journal
which most in the forums have never seen…but, sure do a good job of
raising the flag when something doesn’t work for them!)
there may be an elegant solution in wiki mark up, or just ignore it as
was done in folded lines in (for example)
http://en.opensuse.org/SDB:Skype which wrap or unwrap according to
brower window width…
ymmv
–
DD
openSUSE®, the “German Automobiles” of operating systems
some of them will not be
familiar with the ‘universal’ backslash code notation for “wrap here”
used in the command line instructions…
Well, it’s not only notation, it actually works as is on the command line 
Just added Tumbleweed repo (not thumbleweed) to an updated 12.1 RC2 in a testing system. Kernel now updated to 3.1.0-46.1 and stable.
Above 3
==Updates_for_openSUSE_11.4
is referred too.
Is it ok to substitute this for
==http://download.opensuse.org:80/update/openSUSE-current/
as its now available?
@keellambert
You can exchange these because they are the same (at this point in time):
==http://download.opensuse.org/distribution/11.4/repo/non-oss/ and ==http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/
==http://download.opensuse.org/distribution/11.4/repo/oss/ and ==http://download.opensuse.org/distribution/openSUSE-current/repo/oss/
==http://download.opensuse.org/update/11.4/ and ==http://download.opensuse.org/update/openSUSE-current/
I haven’t tried it with the port added, but it should be the same because :80 is the http default
(And provided you have Tumbleweed and Packman for Tumbleweed as well, you should be ready for a seamless transition to 12.1)
Thanks for the info and re-assurance.
On 08.11.2011 11:36, Winux2 wrote:
>
> Just added Tumbleweed repo (not thumbleweed) to an updated 12.1 RC2
And that is so wrong. Don’t do that.
> in a testing system. Kernel now updated to 3.1.0-46.1 and stable.
If you had “updated 12.1 RC2” you already had 3.1.0-1.1
and you downgraded it to 3.1.0-46.
You must use Current + Tumbleweed
Never Factory or RC + Tumbleweed.
But OTOH it’s your system you do what you like
Vahis
http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.7-default main host
openSUSE 12.1 (x86_64) 3.1.0-1.1-desktop in VirtualBox
openSUSE 11.4 (i586) 3.1.0-46-desktop “Tumbleweed” in EeePC 900
After 12.1RC was fully updated via “zypper dup” (no factory repos, just base 12.1 repos), Tumbleweed repo was added.
“Zypper up” was used and it updated mostly xfce and libreoffice packages and the kernel.
The upgrade worked and fixed a few errors and crashes. However, I’m not using “zypper dup” since it prompts for too many package downgrades and vendor changes to a working “test” system. So, “zypper up” only until after 12.1 final is released or “zypper dup” prompts for upgrades. And yes, I’m aware that “zypper dup” may downgrade packages to fix errors, but at this stage, it’s a no for me.
I’ve searched for kernel version info to no avail, so is zypper downgrading when it claims to be upgrading?
Which kernel-desktop is the upgrade:
Version:3.1.0-46.2 Build Time:Tue 08 Nov 2011 03:10:19 PM EST or Version:3.1.0-1.2.1 Build Time:Sat 05 Nov 2011 08:29:56 AM EDT?
On 10.11.2011 06:56, Winux2 wrote:
>
> Vahis;2401714 Wrote:
>> On 08.11.2011 11:36, Winux2 wrote:
>>>
>>> Just added Tumbleweed repo (not thumbleweed) to an updated 12.1
>> RC2
>>
>> And that is so wrong. Don’t do that.
>>
>>> in a testing system. Kernel now updated to 3.1.0-46.1 and stable.
>>
>> If you had “updated 12.1 RC2” you already had 3.1.0-1.1
>> and you downgraded it to 3.1.0-46.
>>
>> You must use Current + Tumbleweed
>>
>> Never Factory or RC + Tumbleweed.
>
> After 12.1RC was fully updated via “zypper dup” (no factory repos, just
> base 12.1 repos), Tumbleweed repo was added.
Don’t do that.
I quote my previous post again:
“You must use Current + Tumbleweed”
Or, still a day or two, 11.4 + Tumbleweed.
“Current” is the right one. Soon after 12.1 release Tumbleweed developer
will do necessary changes and your Tumbleweed will get updates from that
on towards 12.2, based on 12.1.
That day 12.1 is “Current”
Tumbleweed is always based on “Current release” which today is 11.4,
tomorrow it should be 12.1.
>
> I’ve searched for kernel version info to no avail, so is zypper
> downgrading when it claims to be upgrading?
You are mixing things. You are mixing versions.
Don’t do that. It’s a mess.
Once more: Current + Tumbleweed is right.
> Which kernel-desktop is the upgrade:
> Version:3.1.0-46.2 Build Time:Tue 08 Nov 2011 03:10:19 PM EST or
Tumbleweed has that.
> Version:3.1.0-1.2.1 Build Time:Sat 05 Nov 2011 08:29:56 AM EDT?
12.1 RC2 has that.
Vahis
http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host
openSUSE 12.1 (x86_64) 3.1.0-1.1-desktop in VirtualBox
openSUSE 11.4 (i586) 3.1.0-46-desktop “Tumbleweed” in EeePC 900
If it works, it’s just plain luck, because you’ve mixed repos that aren’t checked for compatibility. You only mix Tumbleweed with the current base repos, see here: HowTo Upgrade openSUSE 12.x to Tumbleweed
So, to be safe: now I’m on Tumbleweed, 11.4-based. I’m going to change my standard repos from 11.4 to current. Until 12.1 comes out there should be no change since current still points to 11.4; when 12.1 will be released (the same day? some days after?), current repos will point to 12.1. So by doing a zypper dup I’ll automatically change to 12.1-based Tumbleweed, no problems at all?
On 10.11.2011 18:56, Lorthirk wrote:
>
> So, to be safe: now I’m on Tumbleweed, 11.4-based. I’m going to change
> my standard repos from 11.4 to current. Until 12.1 comes out there
> should be no change since current still points to 11.4; when 12.1 will
> be released (the same day? some days after?), current repos will point
> to 12.1. So by doing a zypper dup I’ll automatically change to
> 12.1-based Tumbleweed, no problems at all?
>
>
That’s how it works.
If you now keep all your repos pointed to “Current” you will soon start
going towards 12.2.
Vahis
http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host
openSUSE 12.1 (x86_64) 3.1.0-1.1-desktop in VirtualBox
openSUSE 11.4 (i586) 3.1.0-46-desktop “Tumbleweed” in EeePC 900
Hello, I would like to ask a question.
I’ve been using tumbleweed for about 2-3 months. These are my current repositories:
suser@linux-xr5l:~> zypper lr
# | Alias | Name | Enabled | Refresh
--+----------------------------------+------------------+---------+--------
1 | Updates-for-openSUSE-11.4-11.4-0 | Updates | Yes | Yes
2 | openSuse_oss_ | openSuse oss | Yes | Yes
3 | pacman-tumbled | pacman-tumbled | Yes | Yes
4 | repo-non-oss | openSUSE-non-oss | Yes | Yes
5 | tumbleweed | tumbleweed | Yes | Yes
6 | wine | wine | Yes | Yes
suser@linux-xr5l:~>
I’ve normally updated my system using
zypper dup
However, 2-3 weeks ago while trying to update the system I was informed of various KDE dependency problems.
such as
[spoiler]
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
3 Problems:
Problem: kdebase4-runtime-4.6.5-4.7.x86_64 requires oxygen-icon-theme >= 4.6.5, but this requirement cannot be provided
Problem: k3b-codecs-2.0.2-8.pm.13.16.x86_64 requires kdebase4-runtime >= 4.6.5, but this requirement cannot be provided
Problem: kdebase4-runtime-4.6.5-4.7.x86_64 requires oxygen-icon-theme >= 4.6.5, but this requirement cannot be provided
Problem: kdebase4-runtime-4.6.5-4.7.x86_64 requires oxygen-icon-theme >= 4.6.5, but this requirement cannot be provided
deleted providers: oxygen-icon-theme-4.6.5-4.1.noarch
Solution 1: Following actions will be done:
keep obsolete oxygen-icon-theme-4.6.5-4.1.noarch
keep obsolete libqt4-4.7.4-21.1.x86_64
Solution 2: deinstallation of kde4-pacpl-plugins-4.0.5-1.pm.1.2.noarch
Solution 3: break kdebase4-runtime by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c)
[/spoiler]
and after I select a solution more and more problems keep appearing( I stopped counting after 12 ). I chose not to “zypper dup” and simply did a “zypper up” instead, thinking there was a problem with the tumbleweed repo and it’d be resolved whenever 12.1 was released. But, after reading this thread I think that might not be the case and there might be something else wrong with my system.
Could anyone enlighten me as to what is the problem and how to solve it ??
Thank you.
The problem is a fault in the package content of the Tumbleweed repos specifically unmatched dependencies. You could report it on the factory Mailing List and wait for a solution – or try for a workaround.
The problem can also occur when the installed packages’ repo is user removed from the system and not found in any of the active repos.
Another solution: Look in Yast for an update for the kdebase4-runtime package and others that are in error of finding missing dependent packages and install it/them.
I would also limit the use of “zypper dup” in favor of “zypper up”, which is my personal choice (to each their own).
I suggested viewing: 11. Software Repositories - Adding and Managing Package Repositories and SDB:Vendor change update - openSUSE