Zypper can't run update

English Install/Boot/Login
1

Hi all,

Zypper suddenly stoped updating system.
When I run “zypper ref” - works fine.
“zypper up”:


Loading repository data...
Reading installed packages...

Not sure what to do.

Some info about system:
Kernel: 3.19.1-2-desktop
Repos:

# | Alias          | Name           | Enabled | Refresh | URI                                                                                        
--+----------------+----------------+---------+---------+--------------------------------------------------------------------------------------------
1 | mozilla        | mozilla        | Yes     | No      | http://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/                     
2 | packman        | packman        | Yes     | No      | http://packman.inode.at/suse/openSUSE_Tumbleweed/                                          
3 | postgres       | postgres       | Yes     | No      | http://download.opensuse.org/repositories/server:/database:/postgresql/openSUSE_Tumbleweed/
4 | repo-non-oss   | repo-non-oss   | Yes     | No      | http://download.opensuse.org/tumbleweed/repo/non-oss                                       
5 | repo-oss       | repo-oss       | Yes     | No      | http://download.opensuse.org/tumbleweed/repo/oss                                           
6 | repo-update    | repo-update    | Yes     | No      | http://download.opensuse.org/update/tumbleweed/                                            
7 | virtualization | virtualization | Yes     | No      | http://download.opensuse.org/repositories/Virtualization/openSUSE_Tumbleweed/
2

hello,

zypper dup

with tumbleweed

cheers,

Hugh

3

Could you elaborate?
As far as I know, ‘zypper dup’ means dist-upgrade, what I’ve done when I switched from 13.2 to Thumbleweed.
I also want to know why zypper suddenly stopped execute ‘update’ command.

4

Yes, but you should use “zypper dup” to keep your Tumbleweed system updated, at least you should run it once in a while.

On Tumbleweed, every update is in fact a distribution upgrade…
Although most of the time “zypper up” should be ok too, but there are cases that it doesn’t handle. (in particular package downgrades that might happen).

I also want to know why zypper suddenly stopped execute ‘update’ command.

Well, seems to be a more common problem at the moment:
922352 – zypper segfault (should be fixed in Tumbleweed I suppose though, maybe the fix causes the problem?)
924007 – Unable to install plasma5-session
KDE Plasma 5 on openSUSE 13.2 - Install/Boot/Login - openSUSE Forums

Although all of those are reported for 13.2…

So try to run “zypper dup” to see whether this works. It might be possible that you get a zypper update that fixes your problem.
And/or try to disable all repos except the standard Tumbleweed one.

5

wolfi323, Thanks for the great explanation!
Thanks for the help guys.

6

Wow wolfi,

I will have to watch my confident replies. I hope I haven’t misled the original poster.
I had no idea it was OK to use zypper up in Tumbleweed.
Best wishes,

Hugh

7

You realize that he has third party repositories, right? And that using dup with enabled third party repositories could have rather unforseen effects?

And that it does not really address question of hanging zypper? :slight_smile:

Package downgrades in TW should now be just as rare and exceptional as broken update in regular releases. If this happens, this can be dealt with on as needed basis.

8

Yes, but he only has Packman, postgresql, and Virtualization (for which I actually see no need at all on Tumbleweed).
Shouldn’t cause problems with a “zypper dup”.
Although it might be advisable to give Packman a higher priority (lower priority number) to make sure it is preferred.

And actually the advise to use “zypper dup” came from folkpuddle.

And that it does not really address question of hanging zypper? :slight_smile:

There has been a zypper update that might fix his problem.

Package downgrades in TW should now be just as rare and exceptional as broken update in regular releases. If this happens, this can be dealt with on as needed basis.

Yes, but it can happen.

And that’s why I wrote:

Although most of the time “zypper up” should be ok too, but there are cases that it doesn’t handle.

9

Hey guys,
I’ve tried ‘zypper dup’


$ sudo zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

That’s it.
I just notices that ‘zypper up’ and ‘zypper dup’ return code 139. And there is no message about segmentation fault, just fails silently.
Internet says that code 139 is “signal 11 (SIGSEGV on Linux and most other UNIXes), also known as segmentation fault”


$ zypper --version
zypper 1.11.23

Interesting enough, zypper doesn’t respect ‘-v’ flag, only ‘–version’

Not sure if it zypper or not, but Yast Software Management fails as well.

10

On 03/28/2015 07:06 AM, arvidjaar wrote:
>
> wolfi323;2701639 Wrote:
>>
>> Although most of the time “zypper up” should be ok too, but there are
>> cases that it doesn’t handle. (in particular package downgrades that
>> might happen).
>>
>
> You realize that he has third party repositories, right? And that using
> dup with enabled third party repositories could have rather unforseen
> effects?

Repo priority’s should be able to handle this problem.

>
> And that it does not really address question of hanging zypper? :slight_smile:
>
> Package downgrades in TW should now be just as rare and exceptional as
> broken update in regular releases. If this happens, this can be dealt
> with on as needed basis.
>

Shoulda, coulda, woulda.

Ken

11

And I will personally see to it that he never troubles anyone on the forum again, Mr Wolfi.

Yours faithfully,

Mrs Dolcita Folkpuddle (folkpuddle’s mummy)

12

So there is a segmentation fault.

$ zypper --version
zypper 1.11.23

That’s the latest version.
But what version of libzypp and libsolv-tools do you have?

rpm -q libzypp libsolv-tools

The latest versions are libzypp-14.37.0 and libsolv-tools-0.6.9.

Interesting enough, zypper doesn’t respect ‘-v’ flag, only ‘–version’

It respects ‘-V’ (upper case). See the online help that you get when using ‘-v’… :wink:

Not sure if it zypper or not, but Yast Software Management fails as well.

Yes. YaST uses the same libraries for package management, i.e. libzypp and libsolv-tools.
YaST and zypper are just different frontends.

Maybe to remove libzypp’s caches:

sudo rm -r /var/cache/zypp

If that doesn’t help and you have the latest versions of libzypp and libsolv-tools as well, you should probably file a bug report.

13

Hm?
He didn’t “trouble” anyone…:wink:

And his reply was not really wrong either.

14

I’m just a newbie and maybe I’m missing something, but all of your your repos are set to NOT refresh. If you set them to refresh you would get the new versions of your programs and actually be able to update. I always use zypper dup for updating and I’ve never had problems. My repos are also set to refresh. zypper dup works for a standard install too.

15

I have the latest versions

$ rpm -q libzypp libsolv-tools
libzypp-14.37.0-1.1.x86_64
libsolv-tools-0.6.9-1.1.x86_64

Removing cache didn’t work.

But, I disabled packman repo and zypper was able to run update.

16 

The following 29 NEW packages are going to be installed:
  **amarok apper choqok digikam digikam-doc** hdjmod-kmp-desktop-1.28_k3.19.2_1-20.37 ipset-kmp-desktop-6.24_k3.19.2_1-1.20 **kaffeine **
  kernel-desktop-3.19.2-1.1 libixion-0_10-0 liblirc0 liblirc_driver0 libmicrohttpd10 libpoppler51 libunwind lirc-config lirc-core python3-bottle 
  python3-coverage python3-cups python3-nose python3-py python3-pycurl python3-PyYAML python3-requests python3-simplejson 
  virtualbox-guest-kmp-desktop-4.3.26_k3.19.2_1-1.1 virtualbox-host-kmp-desktop-4.3.26_k3.19.2_1-1.1 xen-kmp-desktop-4.5.0_03_k3.19.2_1-2.3

wtf?

17

Well, it probably told you before that those applications get removed.
That’s a glitch in zypper’s handling of applications vs. packages. (a new feature introduced in 13.2).
Or did you uninstall them? “zypper dup” will install recommended packages again. You should lock them (“Taboo - Never install” in YaST), or remove the patterns that recommend them, or use zypper’s “–no-recommends” option.

Anyway, if you can still reproduce the crash when enabling Packman again, you should file a bug report IMHO.

18

Oops, I somehow overlooked this one:

You are quite correct.
I wouldn’t recommend at all to have refresh disabled for all repos, in particular on Tumbleweed.

You won’t see any updates, and you won’t even be able to install packages most of the time, since the versions in your cache most likely are not available any more.

So you’d basically have to run “zypper ref” every time before using YaST/zypper to manually refresh the repos. But if you call it manually all the time anyway, you can just as well enable the automatic refresh… :wink:

19

No, it hasn’t told me that. I don’t have those applications in my system. I uninstall them. I also enabled an option in Yast called ‘Ignore recommended packages for already installed packages’. I run ‘zypper dup’ it suggested to install those unwanted packages/applications.
I’ve tried to run ‘zypper up’, and again, it suggested to install them.
It’s quite a surprise, and precisely is a weird feature.

You should lock them (“Taboo - Never install” in YaST), or remove the patterns that recommend them, or use zypper’s “–no-recommends” option.

That’s what I already did. But it’s really really not cool to go manually through each package and mark them or to use the zypper option every time.
I’m just curious, who is making decisions about new features should be included in opensuse? Do they ask(listen to) community?

Anyway, if you can still reproduce the crash when enabling Packman again, you should file a bug report IMHO.

I run update for other repos, enabled packman, run update again and the problem has gone. Maybe it was a glitch.

So you’d basically have to run “zypper ref” every time before using YaST/zypper to manually refresh the repos. But if you call it manually all the time anyway, you can just as well enable the automatic refresh… :wink:

I disabled autorefresh in purpose :wink:
I found that a bit annoying to sit and wait for repos have been refreshed if I only need to see info about some package. Or when I open ‘Software management’ in Yast. I prefer run ‘zypper ref’ manually before an update or if I need to install something.
Also I have a script which checks and shows a number of packages should be updated. It runs ‘zypper ref’ before a check.

Thank you guys for help. :slight_smile:

20

Then it’s of course clear why zypper lists them as NEW packages to install: because you haven’t installed them, so they are NEW.

I also enabled an option in Yast called ‘Ignore recommended packages for already installed packages’. I run ‘zypper dup’ it suggested to install those unwanted packages/applications.
I’ve tried to run ‘zypper up’, and again, it suggested to install them.
It’s quite a surprise, and precisely is a weird feature.

Why is it a surprise that an option in YaST doesn’t have effect for zypper?
Set “solver.onlyRequires=true” or use the “–no-recommends” option, or uninstall the patterns that recommend those packages, as I already told you.

That’s what I already did. But it’s really really not cool to go manually through each package and mark them or to use the zypper option every time.
I’m just curious, who is making decisions about new features should be included in opensuse? Do they ask(listen to) community?

I already told you how to prevent the installation of recommended packages.

But otherwise recommended packages are to be installed by default. This is on purpose, and also what RPM’s documentation says:

So installing a package containing Recommends: foo should cause the dependency solver to also select a package that is named foo or that Provides: foo, assuming one exists and its selection does not lead to unresolvable dependencies.

( http://www.rpm.org/wiki/PackagerDocs/Dependencies )

And if they weren’t installed by default we’d get a lot of bug reports because applications don’t work or have missing features.

In earlier versions packages you uninstalled manually, were soft locked and never installed automatically again. But this caused other problems and unexpected behaviour (e.g. when installing the nvidia driver), and was removed therefore.

I disabled autorefresh in purpose :wink:
I found that a bit annoying to sit and wait for repos have been refreshed if I only need to see info about some package.

There’s the “–no-refresh” option in zypper.

But in the end it’s your decisions of course.