Another one… not a lucky time for me when it comes to upgrading my machines.
Now it is my laptop… while doing a ‘zypper dup’ I get this (translated from italian):
2 Problems:
Problem: lxc-2.0.3-1.2.x86_64 needs /sbin/setcap, but it is not possible to fulfill this request
**Problem: This request could damage your system!**
Problem: lxc-2.0.3-1.2.x86_64 needs /sbin/setcap, but it is not possible to fulfill this request
deleted provider: libcap-progs-2.22-14.101.x86_64
Solution 1: keep obsolete libcap-progs-2.22-14.101.x86_64
Solution 2: uninstall lxc-2.0.3-1.2.x86_64
Solution 3: break lxc-2.0.3-1.2.x86_64 by ignoring some of its dependencies
I am particularly worried about the sentence I put in bold.
cristiano@xmper8q3:~> zypper se -s libcap-progs
Caricamento dati del repository in corso...
Lettura dei pacchetti installati in corso...
S | Nome | Tipo | Versione | Arch. | Repository
--+------------------------+-----------+-------------+--------+-----------------------
i | libcap-progs | pacchetto | 2.22-14.101 | x86_64 | (Pacchetti di sistema)
v | libcap-progs | pacchetto | 2.25-1.1 | x86_64 | repo-oss
v | libcap-progs | pacchetto | 2.25-1.1 | i586 | repo-oss
v | libcap-progs | pacchetto | 2.25-1.1 | x86_64 | openSUSE:Tumbleweed
v | libcap-progs | pacchetto | 2.25-1.1 | i586 | openSUSE:Tumbleweed
| libcap-progs-debuginfo | pacchetto | 2.25-1.1 | x86_64 | repo-debug
| libcap-progs-debuginfo | pacchetto | 2.25-1.1 | i586 | repo-debug
What would be the best way to proceed? I am already getting this conflict since a few days.
If I do a ‘zypper up’ instead, it seems I’m not getting this problem.
you seam to have an older version of libcap-progs installed, the current TW is 2.25 https://software.opensuse.org/package/libcap-progs
maybe you have have an extra repo causing this issue, post your repo list
that’s not that bad, as TW is a rolling distribution the install disk can only cause problems so remove it and throw the disk away (if it’s a DVD)
you seam to have wolfi’s kf5 repo, the conflicting package seams to be from the DVD, also the debug repo is enabled there is no real reason for this disable it
just a few thoughts
in TW updates are done with zypper dup and that can pull packages from different repositories you should use repo priorities, with the exception of packman all your repo’s have the same default priority (you have 17 repositories with the same priority), you should set packman to 90, the update oss repo (#7) to 91, wolfi’s (#4) to 92, the TW oss repo (#6) to 93 and you can leave the rest alone
On the mailinglists it was suggested not to mess with the priorities, but rather use
zypper --dup --no-allow-vendor-change
The result is that, once you’ve ‘dupped --from …’ and a new TW is released ( that’s what happens when TW gets updated ), packages won’t change vendor, i.e. not come from another repo than already defined, even when a higher build version is available.
But, having this many 3rd party repos active is not a good idea.
BTW, if you need a certain package, you can request it to be added to TW.
I_A, I think you are misreading my repo list (I know, it’s very large and so reading it is difficult).
First of all, I have various disabled repositories: you seem to have missed that. E.g. the dvd repo is disabled, Wolfi’s repo is disabled, repo #14 is the dvd repo (and hence it is disabled). Also repo #1 is disabled.
I know, I should clean up my repo list removing all the disabled repos.
Also, it is not true that all my repos have the same priority: repo #1 has priority 100, and repo #12 (packman) has priority 98.
BTW, all this is irrelevant because I posted the wrong repo list!! lol!
Fact is, I was working at my desktop PC and was connected to the laptop via SSH, so I got confused and posted my desktop PC list instead of that of my laptop.
Here is the correct list (I have removed the URI column so that it should be more readable):
# | Alias | Nome | Abilitato | Controllo GPG | Aggiornamento | Priorità | Tipo |
---+-------------------------------------+-----------------------------------------------------+-----------+---------------+---------------+----------+--------+
1 | Insync | Insync | Sì | (r ) Sì | Sì | 99 | rpm-md |
2 | http-download.opensuse.org-f8bcb618 | home:colomboem | Sì | (r ) Sì | Sì | 100 | rpm-md |
3 | http-download.opensuse.org-f973a818 | openSUSE:Tumbleweed | Sì | (r ) Sì | Sì | 100 | rpm-md |
4 | packman | packman | Sì | (r ) Sì | Sì | 98 | rpm-md |
5 | repo-debug | repo-debug | Sì | (r ) Sì | Sì | 99 | yast2 |
6 | repo-non-oss | repo-non-oss | Sì | (r ) Sì | Sì | 99 | yast2 |
7 | repo-oss | repo-oss | Sì | (r ) Sì | Sì | 99 | yast2 |
8 | repo-update | repo-update | Sì | (r ) Sì | Sì | 99 | rpm-md |
9 | telred-opensuse-leap | TEL.RED software repository for OpenSUSE Linux leap | Sì | (r ) Sì | Sì | 99 | rpm-md |
10 | vivaldi | vivaldi | Sì | ( p) Sì | Sì | 99 | rpm-md |
11 | vivaldi-beta | vivaldi-beta | Sì | ( p) Sì | Sì | 99 | rpm-md |
I don’t think so: those are repositories dedicated to single software projects.
9 is the repositories for the “Sky” messenger, which is a Microsoft Lync compatible messenger.
2 and 3 are repositories for a zero-config multi-platform file transfer tool called “Dukto”.
There is no other software on those repos.
BTW, to check your theory, I disabled 2, 3 and 9 and then reduped, but that made no difference.
where the -d option is explicitly to add the URLs (which you should have seen when you checked the validity/security of what you are asked to do in the man page of zypper).
Then you do NOT show the command you used (the best thing is to show the prompt, the command, the output and the next prompt copies/pasted in one sweep from the terminnal window in beteen the CODE tags, this will increase the trust people have in your reports), so we have to guess if you did what was asked. And then you admit you falsified the output by removing the information that I_A asked for.
There are people that leave a thread alone for less.
I.e. setcap has been moved to /usr/sbin/, but your installed lxc apparently explicitly requires /sbin/setcap.
You may try “Solution 3: break lxc-2.0.3-1.2.x86_64 by ignoring some of its dependencies”. I don’t know what lxc requires /sbin/setcap for, but if it doesn’t explicitly run it via /sbin/setcap, everything should work fine.
OTOH, the worst thing that can happen is that lxc won’t work anymore, this definitely will not “damage” the rest of your system.
And you probably should file a bug report against lxc.
hcvv, I am sorry. It was certainly not my intention to falsify anything or to scare away people from this thread.
My intention was to give the readers a better view of my repo list, since I_A missed a lot of information in my previous post which reported the complete list, which I thought was due to the severe mangling of the list due to the wrapping.
Also, the -d option adds other pieces of information besides the URL (e.g. the priority); I would not have though the URL was a critical piece of information.
Anyway, here is the complete output (I have re-enabled the 2, 3 and 9 repos):
cristiano@xmper8q3:~> zypper lr -d
# | Alias | Nome | Abilitato | Controllo GPG | Aggiornamento | Priorità | Tipo | URI | Servizio
---+-------------------------------------+-----------------------------------------------------+-----------+---------------+---------------+----------+--------+--------------------------------------------------------------------------------+---------
1 | Insync | Insync | Sì | (r ) Sì | Sì | 99 | rpm-md | http://yum.insynchq.com/fedora/21/ |
2 | http-download.opensuse.org-f8bcb618 | home:colomboem | Sì | (r ) Sì | Sì | 100 | rpm-md | http://download.opensuse.org/repositories/home:/colomboem/openSUSE_Tumbleweed/ |
3 | http-download.opensuse.org-f973a818 | openSUSE:Tumbleweed | Sì | (r ) Sì | Sì | 100 | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |
4 | packman | packman | Sì | (r ) Sì | Sì | 98 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
5 | repo-debug | repo-debug | Sì | (r ) Sì | Sì | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/debug |
6 | repo-non-oss | repo-non-oss | Sì | (r ) Sì | Sì | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss |
7 | repo-oss | repo-oss | Sì | (r ) Sì | Sì | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss |
8 | repo-update | repo-update | Sì | (r ) Sì | Sì | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
9 | telred-opensuse-leap | TEL.RED software repository for OpenSUSE Linux leap | Sì | (r ) Sì | Sì | 99 | rpm-md | https://tel.red/repos/opensuse/leap |
10 | vivaldi | vivaldi | Sì | ( p) Sì | Sì | 99 | rpm-md | http://repo.vivaldi.com/archive/rpm/x86_64 |
11 | vivaldi-beta | vivaldi-beta | Sì | ( p) Sì | Sì | 99 | rpm-md | http://repo.vivaldi.com/archive/rpm/x86_64 |
Wolfi, thank you VERY much!!
This is the definitive answer to my problem.
I am currently choosing option 1 (maintaining the obsolete libcap-progs), until the bug is fixed.
No hard feelings. And I have no doubt that your intentions were to make things better. But I thought I better warned you to not do what you are asked for without a good explanation (e.g. because of security). You should never forget that you have a problem you can not solve. The reason that you can not solve it can be manifold. Lack of knowledge, walking the wrong path to a solution. All these are very human and we all suffer from it. Asking others is because you hope that others have more knowledge or do not walk the wrong path. But that means that those others may ask for information you may think is unimportant or useless or even have never thought about. When you stick to that you force others into your way of thinking. The result: no solution.
BTW those wraps in the long lines of the repos list vanish as you make your window wide enough. Perfectly readable to me (and I hope a lot of others).
And of course the URLs are important. They are the only real definition of the repo. All other things are local names/aliases/numbering that can differ from system to system.
A little bonus point for you. When you post here in the English part of the forums, showing Italian computer texts is generaly no problem. I the repo listing, we know what columns to expect. But a nicety is to use a command in this way
LANG=C zypper lr -d
Often when you want to show a command with gives longer error messages, this helps for non Italian speakers.
