Just a note on the printing of the repos, there is an option to print or export the repos using zypper.
zypper repos -e -
Should print the output to standard output a.k.a. stdout, note the trailing - is the key to that or if you like to save it to a file then replace the trailing - (dash) with a file name. see man zypper for more or better yet
PAGER='less +/--export' man zypper
That being said GNU(1) tail can do the same, well almost
Won’t help much in this case though, as zypper is broken…
You seem to live in the past.
Tumbleweed is its own full distribution since 2 years, not just an addon repo for “openSUSE Current” any more.
Remove these repos (they broke your system) and run “zypper dup” to fully switch to Tumbleweed again.
But let’s fix zypper first.
There you have it:
I have installed this versions for libmodman1 and libproxy1:
rpm -qi libmodman1 libproxy1
Name : libmodman1
Version : 2.0.1
Release : 18.3
Architecture: x86_64
Install Date: Sat 19 Nov 2016 01:27:22 PM BRST
Group : System/Libraries
Size : 31344
License : LGPL-2.1+
Signature : RSA/SHA256, Fri 07 Oct 2016 04:03:33 PM BRT, Key ID b88b2fd43dbdc284
Source RPM : libmodman-2.0.1-18.3.src.rpm
Build Date : Fri 07 Oct 2016 04:03:15 PM BRT
Build Host : cloud121
Relocations : (not relocatable)
Packager : http://bugs.opensuse.org
Vendor : openSUSE
Summary : A Module Management Library
Description :
The Module Loading library offers the choice to use prelinked libraries
from your application out of a pool.
Distribution: openSUSE Leap 42.2
This libmodman1 is for openSUSE Leap 42.2 (i.e. openSUSE Current), not Tumbleweed.
Install the one from the Tumbleweed repo, and zypper will hopefully work again.
As a test post the output of “zypper lr -d” then, and I’ll tell you exactly what else to do to fix your system.
If the rpm command gives errors, or zypper still doesn’t work, post them.
And also see the Tumbleweed Portal (in particulare the Installation instructions), to bring your knowledge about Tumbleweed up-to-date… https://en.opensuse.org/Portal:Tumbleweed
Afterwards, run “zypper dup” to switch all packages that you still may have from 42.2 to the Tumbleweed versions.
Feel free to ask if you have further questions.
I downloaded a earlier version of libmodman1 for Tumbleweed and then installed with rpm -Uvh --oldpackage
It’s not really an “earlier” version, it’s the latest one.
But the rebuild count is higher in 42.2 and that’s probably why you got the 42.2 version installed.
> Am Tue, 22 Nov 2016 22:26:01 GMT
> schrieb n1lux <n1lux@no-mx.forums.microfocus.com>:
>
> > -rw-r–r-- 1 root root 146 Oct 28 17:34 google-chrome.repo
> > -rw-r–r-- 1 root root 143 Nov 21 23:15 openSUSE Current non-OSS.repo
> > -rw-r–r-- 1 root root 135 Nov 21 23:15 openSUSE Current OSS.repo
> > -rw-r–r-- 1 root root 125 Nov 21 23:15 openSUSE Current updates.repo
> > -rw-r–r-- 1 root root 135 Nov 21 23:06 packman.repo
> > -rw-r–r-- 1 root root 130 Oct 28 18:09 Tumbleweed.repo
>
> Current and Tumbleweed together?
>
> “no further questions …”
>
> You should fix this horrible mess by choosing EITHER Tumbleweed OR Current
> (42.2 atm) for all repos exclusively and not mashing both together.
>
>
> AK
>
Damn, sent off the mail too early by accident.
After that (and have a look at the content of the packman repo also, again
EITHER 42.2 OR Tumbleweed) you should fix zypper first:
Take the output of
rpm -qa “zypp” “libproxy” “modman”
and manually (yes, manually) download the respective rpm packages from the
respective repos (either Leap 42.2 or Tumbleweed, depending on what you choose)
and install them manually via
rpm -Uvh --force the_respective_rpm_files.rpm
Don’t ignore any warnings/errors, if there are, you will have to
download missing dependencies manually until you can get zypper up and running
again.
If you get zypper running again and after having sanitized your repos, you
can run
zypper dist-upgrade
to hopefully also sanitize your system.
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Yes, you are right.
I was a bit tired already when I wrote this. :\
But luckily he used -Uvh anyway…
Well, I would have rather kept #6, that’s the “official” URL.
Though it doesn’t matter really, this one just redirects to the other one on the server-side.