Tumbleweed is now empty for 12.2 update

English Install/Boot/Login
1

As part of the Tumbleweed lifecycle, with the 12.2 release of openSUSE,
the openSUSE:Tumbleweed repo is now empty so that you can start out with
a “clean” 12.2 release.

It will stay that way for a few weeks for things to settle down with
12.2, and then will start to add packages back to it (new kernel, KDE
4.9, etc.) as time permits.

So, if you wish to stay at 12.1 with Tumbleweed right now, I recommend
NOT updating your system until you feel comfortable moving to 12.2.

If anyone has any questions, please let me know.

thanks,

greg k-h

2

I guess it will take some time before the packages actually disappear?

3

On Wed, 05 Sep 2012 17:06:03 +0000, sunscape wrote:

> I guess it will take some time before the packages actually disappear?

No, they are now gone, it took about an hour after I posted the original
message.

greg k-h

4

I have 12.1 TW version. So, when I want 12.2 TW but I do not want to make a clean instalation 12.2 version firstly (from DVD), I should wait several weeks until 12.2 TW repos are ready, then change my repos to 12.2 TW and run “zypper dup”. Is it correct?

5

Well, as TW is empty now you will end up in a 12.2. installation until new packages arrive (see first post in this thread). Once you changed your repos to ‘current’ and added the new update-repo for non-oss, a zypper dup should update you to whatever is there. So my current understanding. It will take you back to the 3.4 kernel and some other stuff.
I currently run 12.1 TW + KDE 4.9, and not sure what to do.

6

I tried updated tumbleweed 12.1 from 12.2 repository oss non-oss. The update collapsed and system became inoperable. I have nothing else than to run the update to 12.2 from dvd.

7

The safest way is to download a new version and make a DVD. If something fails, you can make a clean install or try upgrade. Better - but more complex solution is to make a backup of a root partition firstly. I am going to make a DVD and wait for TW repos to see, if it is possible to use TW as “continual” upgrade of opensuse. That was reason why I started to use TW.

8

Hi!
I think it was a bad idea to delete all the packages from the Tumbleweed repo without the notification of users. In my case, the upgrade was a big problem, with the crash of my system.

9

On Sun, 09 Sep 2012 13:36:02 +0000, andranique wrote:

> Hi!
> I think it was a bad idea to delete all the packages from the Tumbleweed
> repo without the notification of users. In my case, the upgrade was a
> big problem, with the crash of my system.

I did notify the users, you see it in this thread.

And what crashed, when you did an upgrade to 12.2? That was
“interesting”, and unexpected, but recoverable, and something that
happened with the 12.2 upgrade, and had nothing to do with the packages
being removed from the Tumbleweed repo at all (hint, you would have had
the same crash even if the packages were in there, as the problem was an
upgrade issue from a Tumbleweed package to the 12.2 package.)

But, all is now good that your system is finished updating to 12.2, right?

thanks,

greg k-h

10

I did notify the users, you see it in this thread.

Thanks a lot. From this moment I will use only English Forum of openSUSE:-)

And what crashed, when you did an upgrade to 12.2?

But, all is now good that your system is finished updating to 12.2, right?

First of all, when I did the upgrade from # zypper dup, my system crashed at the end of the process with this message: “Oh no! Something has gone wrong…etc.” And I couldn’t do anything to save the process. And I had to use the DVD 12.1 to recover the system.

Secondly, I upgraded the system from 12.1 to 12.2 from #zypper dup. And I noticed that my Gnome extensions had disappeared from the Gnome panel and there were no extensions in the “Advanced settings” (although the extensions are added, but there were none in the settings).

Thirdly, GRUB 2 is empty. There is no system.

…and many other minor problems.

11

Here are my repos:

| Псевдоним | Имя | Включён | Обновление

—±-------------------------------------±-------------------------------------±--------±----------
1 | Banshee | Banshee | Да | Да
2 | Education | Education | Да | Да
3 | Games | Games | Да | Да
4 | Google | Google | Да | Да
5 | Lazy_Kent | Lazy_Kent | Да | Да
6 | LibreOffice | LibreOffice | Да | Да
7 | Packman | Packman | Да | Да
8 | Science | Science | Да | Да
9 | Security | Security | Да | Да
10 | Tumbleweed_1 | Tumbleweed | Да | Да
11 | VirtualBox | VirtualBox | Да | Да
12 | google-earth | google-earth | Да | Да
13 | home:simontol:gnome-shell-extensions | home:simontol:gnome-shell-extensions | Да | Да
14 | openSUSE_Current_OSS | openSUSE Current OSS | Да | Да
15 | openSUSE_Current_non-OSS | openSUSE Current non-OSS | Да | Да
16 | openSUSE_Current_updates | openSUSE Current updates | Да | Да

12

Looks like you have a mixture of repo’s that should not be used together. It’s no wonder your update failed. That extensions repo you list is for Factory? I guess… since there is nothing for 12.2.

On another note, I’ve never expected an update in any linux distro to go smoothly. You should just backup your data and install from scratch.

13

On Sun, 09 Sep 2012 18:16:02 +0000, andranique wrote:

>> And what crashed, when you did an upgrade to 12.2?
>> But, all is now good that your system is finished updating to 12.2,
>> right?
>
> First of all, when I did the upgrade from # zypper dup, my system
> crashed at the end of the process with this message: “Oh no! Something
> has gone wrong…etc.” And I couldn’t do anything to save the process.
> And I had to use the DVD 12.1 to recover the system.

You weren’t dropped into a text console login, and could continue the
update? That is what happened to me on one of my boxes (the other one
had no problems at all.)

> Secondly, I upgraded the system from 12.1 to 12.2 from #zypper dup. And
> I noticed that my Gnome extensions had disappeared from the Gnome panel
> and there were no extensions in the “Advanced settings” (although the
> extensions are added, but there were none in the settings).

That’s a GNOME upgrade issue, not a Tumbleweed one.

> Thirdly, GRUB 2 is empty. There is no system.

What do you mean? Grub 1 should still be installed, that is what happens
when you do a ‘zypper dup’ update, grub2 isn’t installed that way for
some reason (again, not a Tumbleweed issue at all, that is why Tumbleweed
is “empty” for right now, so that people can’t blame any of these issues
on it…)

> …and many other minor problems.

Like what?

As you point out, you have lots of other repos enabled, because of that,
I really don’t know what happened, or what to suggest, sorry. Mixing
repos can be dangerous if you don’t know what you are doing, and is not
something I recommend doing at all.

good luck,

greg k-h

14

How many time take to reload the tumbleweed repos?, days, weeks, months?, first time with opensuse.

15

On 09/11/2012 01:56 PM, Steemx wrote:
>
> How many time take to reload the tumbleweed repos?, days, weeks,
> months?, first time with opensuse.
>
>

It’s operational now.

If you attach the Tumbleweed repos properly, you can consider yourself a
Tumbleweed user right now.

It happens once in each release cycle that the openSUSE release becomes
coincident with Tumbleweed. Right now the two are coincident.

As more packages are added into the Tumbleweed repos, they are of course
in advance of 12.2, and consequently Tumbleweed will slowly advance away
from 12.2.

So you can start now.

–
Regards
swerdna

16

I’m sorry for a stupid question. Greg k-h wrote, that the TW repos would be empty for several weeks. It means that I can run “zypper dup” now? No problems?

17

Looks like you have a mixture of repo’s that should not be used together. It’s no wonder your update failed. That extensions repo you list is for Factory?

All of those repos are forTumbleweed

18

You weren’t dropped into a text console login, and could continue the update?

If you mean update froom the root, I did that from it.

19

You updated from an empty repository or one populated with packages not entirely compatible with the “current” repositories, and with repositories enabled for Tumbleweed. This would obviously lead to a failure.

20

I updated from current oss
on-oss\update repos from # zypper dup. All of tumbleweed repos were disabled.