i have just install openSUSE 12.3 and remove repo of it, add new on openSUSE website instruct
to try openSUSE Tumbleweed but when i check version
it still show that 12.3
That’s correct. Tumbleweed doesn’t have its own version number. In the end it is just a current openSUSE version with some additional updates/upgrades (from the Tumbleweed repo).
Regarding your repo list:
Your Packman repo is for 12.3. Change that to the Tumbleweed version. [noparse]http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Tumbleweed/[/noparse]
The same goes for the libdvdcss repo, but there you could just keep the 12.3 version. It only contains libdvdcss anyway and I don’t know if there is a Tumbleweed version of it.
Remove the VideoLAN repo (#5)! It is not compatible with Packman, having both can lead to problems. Anything that’s in there is available from Packman anyway.
And you can also remove those standard 12.3 repos (#7, #13, #14, #15, #16).
Repos #1, #2 and #3 can be removed as well, since they are duplicates (according to their names I guess you used zypper with wrong arguments there… ).
Of course, to really use Tumbleweed you have to upgrade your system with “zypper dup”. Have you done that already?
In the future, when newer OpenSuSE versions become available, how would I go about upgrading to them? I installed OpenSuSE 12.3 64 bit, but I removed the standard software repositories and I added the Tumbleweed repositories and I did a zypper ref, zypper up, and zypper dup. So, when OpenSuSE 13.1 64 bit is released, how would I go about upgrading? How would I check to ensure that I upgraded to the latest version? lsb_release -a? Thanks.
The TW repo will empty, and the “Current” repos, if you used those (see wiki), will auto swtch to point to the 13.1 standard repos. You will need to zypper dup to rebase on 13.1. When the TW repo starts filling, upgrade as usual (zypper dup). Unless Greg changes it…
If you have a similar repo list like in the first post here (with the openSUSE-Current repos instead of openSUSE-12.3) you won’t have to do anything special to upgrade.
Those openSUSE-Current repos will be switched to point to 13.1 some time after the release.
The next “zypper dup” will upgrade your system to 13.1 then.
How would I check to ensure that I upgraded to the latest version? lsb_release -a? Thanks.
On 2013-10-09 19:36, wellywu wrote:
>
> In the future, when newer OpenSuSE versions become available, how would
> I go about upgrading to them? I installed OpenSuSE 12.3 64 bit, but I
> removed the standard software repositories and I added the Tumbleweed
> repositories and I did a zypper ref, zypper up, and zypper dup. So, when
> OpenSuSE 13.1 64 bit is released, how would I go about upgrading? How
> would I check to ensure that I upgraded to the latest version?
> lsb_release -a? Thanks.
If you installed the documented way (keeping the “current” repo plus
tumbleweed repos), and update only via “zypper dup”, as documented, you
need doing nothing.
The current repos point to 12.3 at the moment. In a month or so they
will point to 13.1, and the tumbleweed repos will be emptied: the next
zypper dup takes you to 13.1+T automatically.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
OpenSuSE 13.1 64 bit will be released on November 19th, 2013 correct? So, all I have to do is just wait until that date and do my regular updates like zypper ref and zypper up. On that date, I do a zypper ref and zypper dup. Is this correct?
I just installed OpenSuSE 12.1 64 bit and changed it to Tumbleweed yesterday. I haven’t used OpenSuSE since 12.1 64 bit a while ago. I’ve been using Ubuntu 12.04.3 64 bit for most of the time.
Not quite. Based on previous, that “next zypper dup” takes you to 13.1, with possibly a lot of downgraded packages. The “+T” bit can take several weeks to a month before it fills with new stuff, depending on the maintainer’s workload and testing results.
Tumbleweed was meant to achieve a rolling release version of openSUSE, not as a way to get updates. On one of my testing installs I followed the documented way. As soon as the TW repo empties, a zypper dup brought me to 12.3, when TW got filled I needed a --from TW to get it rolling again.
As for TW’s role in the future: on G+ Greg suggested dropping Factory as the base for new released versions in favour of TW would be a good option. I don’t know if that has had any follow-up, it at least hasn’t for 13.1. Creating a new released version would in that option be freezing TW at some point, optimize where possible, brand, build, release.
Tumbleweed is rock stable, package availability has grown (more and more packagers build not just for the released versions, but also TW, using the buildservice that’s easy)
Factory is not stable at times, but it wouldn’t require some freezing in there.
Re. the above, less would have to be done to create a new openSUSE release.
Re. the above, a rolling release would become a real rolling release. These days LTS and rolling release are items IMHO a modern distro should provide.
Again, all this IMHO.
Sometimes it just takes a while for the community to get used to the idea that things won’t stay the same forever.
Yes, I agree that would be a good place for openSUSE to be with both LTS and real rolling release, and I could make use of both. That just leaves a middle sector of users who like a stable yearly release plus a light workload wrt updates. The idea being that for them there would also be a standard release based on a “frozen” version of Tumbleweed, if I understood you correctly.
That sounds like a horrible idea to me, this would basically cripple submission of new features and packages, as it would also slow down the whole process…
But that is just me, speaking as a Factory user & contributor
I was hoping for a reply like yours, @sumski. Could you explain how this would do the above? I can imagine difficulties, and slowdowns, but I can see advantages too. Just interested.
On 2013-10-09 20:16, wellywu wrote:
>
> OpenSuSE 13.1 64 bit will be released on November 19th, 2013 correct?
> So, all I have to do is just wait until that date and do my regular
> updates like zypper ref and zypper up. On that date, I do a zypper ref
> and zypper dup. Is this correct?
The documented way and recommended by the developer is use “zypper dup”
always. A “zypper ref” is redundant - unless you have specific reasons.
> I just installed OpenSuSE 12.1 64 bit and changed it to Tumbleweed
> yesterday. I haven’t used OpenSuSE since 12.1 64 bit a while ago. I’ve
> been using Ubuntu 12.04.3 64 bit for most of the time.
The “current repo” that you have to use points to 12.3, not 12.1.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On 2013-10-09 20:16, consused wrote:
>
> robin_listas;2590232 Wrote:
>> In a month or so they
>> will point to 13.1, and the tumbleweed repos will be emptied: the next
>> zypper dup takes you to 13.1+T automatically.
> Not quite. Based on previous, that “next zypper dup” takes you to 13.1,
> with possibly a lot of downgraded packages. The “+T” bit can take
> several weeks to a month before it fills with new stuff, depending on
> the maintainer’s workload and testing results.
“T=0”, so it is still “13.1+T”, so “13.1+T=13.1”
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Ah, so you claim T is a variable, but “13.1+T = 13.2 where T=1”. That doesn’t work. If only 0 works then T is a redundant constant amounting to nothing!
Therefore, within context, T is the initial of Tumbleweed, on the balance of probability. Case dismissed :P.
> workload wrt updates. The idea being that for them there would also be a
> standard release based on a “frozen” version of Tumbleweed, if I
> understood you correctly.
I certainly prefer a “stable” release, in the sense of few updates.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
).