Is it ready or still empty?
I keep on looking in the tumbleweed forum for announcement but I haven’t seen one
I am asking because I can see post for new tumbleweed installs and I am waiting to
update mine also.
There’s a kernel (3.8.6) waiting for you.
Isn’t it the same as the one in 12.2 tumbleweed?
I have to check because since the empty announcement I haven’t updated my tumbleweed
It was announced in the mailing lists:
[opensuse-factory] Tumbleweed is back!](http://lists.opensuse.org/opensuse-factory/2013-04/msg00188.html)
It was announced in this forum’s sticky, right above this thread (the time of posting) 
Uhum. Thanks I better visit the forum frequently, 
I am updating now while writing this in my tumbleweed. I will post what happens next.
Done the update, only problem I had was I forgot to install the broadcom driver so I have to download it manually and
install it and use the nvidia proprietary driver and now I am back and writing from tumbleweed.
Is there any way to check if my tumbleweed setup is working? I ran zypper update and I feel like I’m not getting the new packages.
Thanks
On 04/16/2013 09:16 PM, tamas305 wrote:
> zypper update
where did you learn to use ‘zypper update’ with Tumbleweed?
have you read this one page how-to?
http://en.opensuse.org/Tumbleweed
–
dd
I misunderstood what that meant. So what it is saying is that it updates in the background without notifying me? Is there any way to confirm successful updating?
Sigh!
# zypper refresh
# zypper dup
and you will see what, if anything, is happening.
On 04/16/2013 09:56 PM, tamas305 wrote:
> I misunderstood what that meant.
imo, if you do not understand that one page you should not be running
Tumbleweed…
Tumbleweed is not well suited to people with little or no experience
with openSUSE…
i’d suggest you stick with openSUSE 12.3 for a while…like until
13.1 comes out…at least.
ymmv
Once you’ve made the vendor change to TW, a ‘zypper update’ is completely normal and functoning like that, no matter whether the vendor change is done through Yast or through cli.
Yes, isn’t hindsight wonderful.
It’s even possible to maintain Tw using YaST Software Management (and Online Update). I did that successfully with my 12.1 based Tw for good reason at the time, but I wouldn’t recommend it to a “newcomer”.
Agree on both counts.
I updated with YaST Software Management to Tumbleweed (12.3) in the Laptop of the LUG (Linux User Group) that I belong to, where Tumbleweed has been installed since 12.1 (and updated from 12.1-tumbleweed -> 12.2-tumbleweed and now to 12.3 baseline plus Tumbleweed). The LUG laptop is an old beast (~1.5 GHz CPU with 512MB RAM and some ancient AMD graphic hardware), running LXDE. I don’t think I would have the confidence to update (nor recommend to anyone else to update) without the knowledge that I have today. … I did have to make a few choices as to versions of apps to use , or downgrade, during the install.
On 04/16/2013 11:16 PM, Knurpht wrote:
>
> Once you’ve made the vendor change to TW, a ‘zypper update’ is
> completely normal and functoning like that, no matter whether the vendor
> change is done through Yast or through cli.
having never used Tumbleweed all i know is what i read, as written by
the Tumbleweed originator and maintainer on
http://en.opensuse.org/Tumbleweed where i find three uses of the
phrase “zypper dup” and no instances of “zypper update”…
and, i saw the word ‘only’ in this section from that page:
----------------quote-------------------------------------
The only supported method of repo use for Tumbleweed is to have only
the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo
active. For that situation a simple
sudo zypper dup
will update your packages, and if any packages are ever reverted from
Tumbleweed zypper dup will also handle that.
Despite it being unsupported, if you do choose to have other repos
enabled, this command is safer:
sudo zypper dup --from Tumbleweed
---------------end quote-----------------------------------
if Greg needs to re-word what he supports someone should mention it
to him…
–
dd
That was my read, also. I have not used Tumbleweed until 12.3, so I’m new at it.
I booted my Tumbleweed box.
I check Yast online update, to see what it said. It listed the same updates that I recently applied to a standard (non-TW) 12.3 system. I aborted that.
I then did “zypper update”. That gave me many updates, including the ones shown in the Yast online update. Most of the updates from “zypper update” were from Packman repos.
I then did “zypper dup” to see if anything was missed by the “zypper update”:
The following NEW packages are going to be installed:
kernel-default-devel kernel-desktop kernel-desktop-devel kernel-devel
kernel-xen-devel
The following packages are going to be upgraded:
libcdio14 libiso9660-8
The following packages are going to change vendor:
libcdio14 openSUSE -> http://packman.links2linux.de
libiso9660-8 openSUSE -> http://packman.links2linux.de
The switch to packman (last few lines) is probably no big deal. However, the “zypper update” failed to do the kernel update (from 3.8.6-2.1 to 3.8.6-2.2). Looking at the “versions” tab of Yast Software Management, it looks as if that was some sort of vendor change from “@System” to “openSUSE-Tumbleweed”, though both versions came from the Tumbleweed repo.
My interpretation - it is best to stick to “zypper dup”. (But I’ll change my mind if the new kernel doesn’t boot).
On 04/17/2013 04:26 PM, nrickert wrote:
> the “zypper update” failed to do the kernel update (from
> 3.8.6-2.1 to 3.8.6-2.2). Looking at the “versions” tab of Yast Software
> Management, it looks as if that was some sort of vendor change from
> “@System” to “openSUSE-Tumbleweed”, though both versions came from the
> Tumbleweed repo.
>
> My interpretation - it is best to stick to “zypper dup”. (But I’ll
> change my mind if the new kernel doesn’t boot).
Greg has just (two or three hours ago) made a statement which i think
explains why ‘zypper update’ had a problem with 3.8.6-2.1 to
3.8.6-2.2 update–you can read it here:
http://lists.opensuse.org/opensuse/2013-04/msg00755.html
note he is not writing about Tumbleweed, but rather the actions taken
by “zypper update” when multiple repos contain the same package and
version, but differing release numbers…
but as said, i’m just trying to read and understand…to me it looks
like Greg both said “zypper dup” and knew what he was talking about.
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
Well yes. I see no point in using zypper update, when zypper dup is available and advised. What would be the advantage?
The only point for using YaST is that you can manually make/force/control/stage the update(s) if a situation warrants that intervention, otherwise the dist-upgrade is easier and provides for a dummy run.