If anyone wishes to help or shed light on why my zypper dup does not see or install the new kernel - 3.6 series I believe - then please read backwards from where my helper caf4926 has advised me to start a new thread here.
On 10/09/2012 06:56 AM, folkpuddle wrote:
> http://tinyurl.com/9kunxel
>
> If anyone wishes to help or shed light on why my zypper dup does not
> see or install the new kernel - 3.6
sorry, i don’t wish to read back through 50+ posts to learn: what kernel
are you now running? the first line below a terminal will tell that and
what kernels do you now have installed will be told by the second?
uname -a
ls -h /boot | grep vm | grep gz
please copy paste both results back into code tags, as described here: http://goo.gl/i3wnr
Like already said here, running “zypper dup” just like that is not going to bring you to Tumbleweed. You have to tell zypper it has to make a “vendor change” to Tumbleweed, so in your case
su -c 'zypper dup --from tumbleweed'
if this makes you run into dependency conflcts, please post the output of the command above here, between CODE tags.
On 10/09/2012 02:16 PM, consused wrote:
>
> Why not?, I haven’t seen a problem with it.
sudo runs with the environment and path of the user who invokes sudo…
and YaST Software Management and Online Update both run with roots
environment/path, so it seems to me that zypper should be run by root,
with roots environment and path…
you may “get away with” running (zypper) installs with a users path
(because, i guess the rpms should know where to push stuff to), but you
should expect a failure if you run “make install” without roots
environment…
That’s a question that can’t be answerwd with a yes / no. What you do with a 'zypper dup --from repoX " is tell the system that you want installed packages to be the versions from repoX. This goes for currently installed packages, and since the Tumbleweed repo has just started being populated, you may need to do this more often. But, by the time the Tumbleweed has most of the packages you use installed a " zypper up " is fine.
If you’re new to this, I strongly suggest you use Yast’s softwaremanagement. The repo view mode allows you to see which packages live in which repo.
Just one more thing: I suddenly notice the “new user” in the thread title. You’re on your way now, but I wouldn’t suggest Tumbleweed to a new user. 'Latest and greatest" is not always the best way to go, if you’re just starting you’ll find a much larger crowd to support you when you stick to the distro’s version.
A couple of tips:
keep your number of repos limited to oss, non-oss, their update sisters and packman. That should keep you out of trouble
invest some time of your own to fix things instead of reinstalling.
be patient, the forums are run by volunteers that have daily jobs, families and do on, some things need specialist’s advice
The ‘new user’ refers to my status as new user of this iteration of openSUSE and Tumbleweed.
My use of ‘new user’ in the title might also explain why people were keen to explain how to use code tags - this is puzzling as the first post contained two (2) examples of the use of code tags.
Likewise it would not occur to me to use ‘sudo’ - but a presumed ‘new user’ might not know that e.g. a *buntu refugee
<<invest some time of your own to fix things instead of reinstalling.>> - with all dues respect three days of fiddling went nowhere in this instance. I could afford the bandwidth allowance this month,
it was no trouble to reinstall.
When you live in the Southern Hemisphere like I do the timezone factor teaches this linuxer to be patient - I am asleep when folks are replying!! and vice versa,
I updated two PCs to 12.2-Tumbleweed using ‘zypper dup’ (where both PCs had 12.1 Tumbleweed prior to the update). Both worked. Both were old PCs (one my Sandbox PC with an Athlon-1100 CPU and 2GB of RAM, and the other an old office laptop with 1.6GHz Intel CPU with 512MB RAM). Both updates took a long time ~2 hours in one case and ~2.5 hours in the other, and I have a very fast Internet connection. I had solve one dependency (different) in each case. The dependencies were different and not difficult to solve (each associated with a packman packaged multimedia app). The repositories I had in place were the openSUSE-current OSS, openSUSE-current Non-Oss, openSUSE-current update, the standard tumbleweed, and the Packman Tumbleweed.
I’m still not ready to update my main PC this way (I prefer the cleaning that comes with a re-install) but I confess to being impressed with the ease of doing a ‘zypper dup’. I can see it being the way of the future (for me) for updates.
You got the point; but as Knurpht said above: if your number of repos limited to oss, non-oss, their update sisters and packman, you can do it with zypper dup.
Anyway, using zypper dup --from tumbleweed is a safe way which leads you little trouble:P
But it’ll not fetch in updates from the other repos will it
I think you got misunderstand here. take gstreamer-0_10-plugins-good for example: it is in openSUSE Current oss，but in sometime there is a higher version in Packman，it will not update automatically util you execute zypper dup --from packman，is not it？
as you said dup means to get latest version in current repos，but dup --from tumbleweed is just a Friendly suggestion(Portal:Tumbleweed - openSUSE)
@caf
Fascinating as this debate about zypper dup and/or zypper dup --from tumbleweed, we must not lose sight of why I started the new thread.
As you know from spending all that virtual time with me yesterday zypper dup on a complete new patched install did not do the business as far as bringing in the new kernel.
While my zypper dup was failing your zypper dup was succeeding.
Neither of us knows why. It has never happened to me before. openSUSE12.1 for example was converted or translated to Tumbleweed by me earlier this year.
I started this new thread I was advised to try zypper dup --from tumbleweed and it was successful.
Now how can I argue with a result like that? I can’t and won’t.
