I’m new to using OBS / software.opensuse.org so perhaps this is normal…
I need a package:[FONT=arial]**libmediainfo.so.0()(64bit) **. I found it available for Leap 15.2 here and downloaded the .ymp . When I try to install it from the YMP (using Yast 1-click) it sets up the new repo and then fails to install the package.
What am I missing here?
[/FONT]
zypper se -s --provides libmediainfo.so.0
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Typ | Version | Arch | Repository
---+---------------------+-------+-----------------+--------+-----------
i+ | libmediainfo0 | Paket | 18.03-lp152.3.7 | x86_64 | OSS
| libmediainfo0-32bit | Paket | 18.03-lp152.3.7 | x86_64 | OSS
Please do not install packages from outside the repos until you know, what you are doing…
What package need the lib?
Show:
zypper lr -d
If you are using a working 15.2 system you just need to install via:
su -
Password:
zypper in libmediainfo0
since the package is in the default OSS repo.
If you are not using Leap 15.2, refrain from installing that package in an alien system.
Please provide the information asked for by @Sauerland if you need more help.
@Sauerland - it’s a third party app, Mega. Also, I’ve been on linux for 15 years but am still very rough around the edges when it comes to linux packaging, OBS, and the SUSE ecosystem. In this case, I was trying to install an “official package” from software.opensuse.org for my distro. My understanding is that this is as secure as the packages from OSS but perhaps not as tested or stable. Is that accurate?
@OrsoBruno - I used "rpm -i"and that failed with two dependencies: [FONT=georgia]libmediainfo.so.0()(64bit) and libzen.so.0()(64bit). At that point, I searched for the missing packages and found the first on software.opensuse.org. Is there a better command for installing RPMs that resolves dependencies better? Once I manually installed libmediainfo0 with zypper, I was able to rpm -i the app.
There seems to be a disconnect between the names of the package listed on software.opensuse.org (without the trailing 0) and the package in OSS. Yast 1-Click can’t resolve it, rpm -i can’t resolve it, and I couldn’t resolve it. If anyone can educate me on how or why, I’d love to understand this.
Thank you both
[/FONT]
My understanding is that this is as secure as the packages from OSS but perhaps not as tested or stable. Is that accurate?
The packages from OSS are official and tested and if something going wrong you can add a bugreport and it will be patched.
Once a package is delivered with an openSUSE version (i.e. Leap 15.2), the version of the package will not change/updated. Only bugfixes and backports.
The other packages are semiofficial and mostly “factory” packages for testing to get for the next distribution or they are newer versions as delivered with openSUSE.
Also a bugreport will help, but mostly it will take a longrt time to patch it.
There are also /home Repos.
Here evrybody can build packages for themselve without any guarantee of working/updating.
Some will do that but there are many Repos that have not be updated for years and packages are broken.
So for me:
less repos are often more…
less errors, a working linux etc.
it’s a third party app, Mega
Is that an app (megasync) for syncing cloud store?
[FONT=georgia]
The “official” and best tool to manage packages on openSUSE is zypper, or YaST2-Software which is a graphical interface to the same libzypp library.
Here is what an experienced openSUSE user would have done:
LT_B:~ # zypper search --provides libmediainfo
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+---------------------+--------------------------------------------------------------------+--------
| libmediainfo-devel | Include files and libraries for development | package
| libmediainfo0 | Supplies technical and tag information about a video or audio file | package
| libmediainfo0-32bit | Supplies technical and tag information about a video or audio file | package
LT_B:~ # zypper in libmediainfo0
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
libmediainfo0 libzen0
2 new packages to install.
Overall download size: 2.1 MiB. Already cached: 0 B. After the operation, additional 7.3 MiB will be used.
Continue? [y/n/v/...? shows all options] (y):
zypper is a powerful tool but with its many options it may look confusing to those coming from other distros. You can look up details with:
man zypper
or ask in the forums if you need help. Not every option combination is available in YaST2-Software, but every common task can be done easily by the casual user there.
The “rpm” tool is not specific to openSUSE and “sees” only packages already installed in the system (those in the rpm database) or explicitly included in the command-line list of supplied rpm files, so it can check whether dependencies are already satisfied by system or command line packages but cannot search through configured repositories for a package that provides a specific capability, so no wonder that it failed for you.
There seems to be a disconnect between the names of the package listed on software.opensuse.org (without the trailing 0) and the package in OSS. Yast 1-Click can’t resolve it, rpm -i can’t resolve it, and I couldn’t resolve it. If anyone can educate me on how or why, I’d love to understand this.
[/FONT]
You met with an unlucky case.
“libmediainfo” just provides the source code package (libmediainfo-18.03-lp152.3.7.src.rpm) that cannot provide the capability you need, which is provided by the libmediainfo0 binary package.
You can check that by clicking the “Grab binary packages directly” button in this page.
AND that source package is not even found by the .ymp file which points to http://download.opensuse.org/distribution/leap/15.2/repo/oss/ (the binary repo) instead of the source repo which is at https://download.opensuse.org/**source**/distribution/leap/15.2/repo/oss/**src**/
You were unlucky enough to need a package which provides the source and the binary under different names, which is not uncommon for system libraries BTW.
Great info! Really appreciate the explanation as it helps me understand the environment / tools and how I got lost.
@Sauerland - yes, that’s the app. Thanks for the breakdown on reliability in OBS, etc.