-------- Original Message --------
Subject: [opensuse-factory] Warning: don’t zypper up in X
Date: Wed, 04 Jun 2014 06:10:43 +0200
From: Stephan Kulow <...@suse.de>
To: opensuse-factory <opensuse-factory@opensuse.org>
Hi,
I’m not sure if it’s a bug or a feature, but updating to current Factory
restarts X. This wouldn’t be a problem in itself, but unfortunately
zypper updates libzypp, then restarts X and by then it has forgotten to
update zypper itself. So once you’re back in X, there is no zypper to
work with - because:
zypper: error while loading shared libraries: libzypp.so.1419: cannot
open shared object file
You can work around it by doing “zypper up zypper” first, or call zypper
from text console.
I find it hard to decipher exactly the scenario they’re talking about.
It’s definitely not an issue once you’re already updated to 13.2, In a brand new 13.2, I see no problems running “zypper up”
So I think the thread is warning about upgrading from something (probably 13.1) to 13.2 by either zypper up or zypper dup (either is possible possibly because at this very early stage of 13.2, it is nearly the same as 13.1).
Upgrading at this time involves a quirk when zypper itself is updated, so a workaround is recommended, which is to update zypper separately before updating everything else, ie.
Change the repositories, then
zypper up zypper
before running
zypper dup
If I misunderstand what is being described, open for correction.
> I find it hard to decipher exactly the scenario they’re talking about.
>
> It’s definitely not an issue once you’re already updated to 13.2, In a
> brand new 13.2, I see no problems running “zypper up”
Sorry to have to contradict you but it is definitely a problem with
13.2. I’ve had this happen when updating 13.2-m0 on two machines but
the fix Stephan provided has fixed the problem.
Another trouble is that every update I perform (via YaST) results in
me being logged off after after updates have been downloaded. I then
have to log back on for installation to occur. I have seen this problem
mentioned elsewhere but have yet to check bugzilla.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.13.1; AMD Phenom II X2 550 Processor;
Kernel: 3.15.0-rc7; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
Cool.
Sounds like a very specific set of conditions that hopefully should not apply normally.
And, as long as anyone has either installed or updated past that date already should not worry.
It does seem like a good idea to open a virtual console (say, with CTRL-ALT-F1), login there as root, and run the “zypper dup” or “zypper up” from there. That way, even if the desktop is restarted, the update continues.
On 2014-06-07 22:56, tsu2 wrote:
>
> nrickert;2647894 Wrote:
>> Actually, it is a warning about going from 13.2 at the level of the
>> 20140528 factory snapshot to 13.2 at the level of the 20140602 factory
>> snapshot.
>
> Cool.
> Sounds like a very specific set of conditions that hopefully should not
> apply normally.
It applies to anyone that is closely following Factory, that is, 13.2.
And factory, aka beta, must always be updated by doing “zypper dup”, not
“zypper patch” nor “zypper up”. That’s the /official/ method, same as
for Tumbleweed.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-06-07 23:56, nrickert wrote:
>
> It does seem like a good idea to open a virtual console (say, with
> CTRL-ALT-F1), login there as root, and run the “zypper dup” or “zypper
> up” from there. That way, even if the desktop is restarted, the update
> continues.
Absolutely.
Otherwise, use tmux or screen.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)