Bug 26100 - Missing dependency on libsnappy
Summary: Missing dependency on libsnappy
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-18 15:13 CET by Olivier FAURAX
Modified: 2020-01-18 20:08 CET (History)
1 user (show)

See Also:
Source RPM: chromium-browser-stable-78.0.3904.108-1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Olivier FAURAX 2020-01-18 15:13:55 CET 
$ urpmi chromium-browser
    http://mirrors.mageia.org/api/mageia.7.x86_64.list: media/core/updates/chromium-browser-78.0.3904.108-1.mga7.x86_64.rpm
installation de chromium-browser-78.0.3904.108-1.mga7.x86_64.rpm depuis /var/cache/urpmi/rpms                                                                                                
Préparation...                   ############################################################
      1/1: chromium-browser      ############################################################
$ chromium-browser 
/usr/bin/chromium-browser: error while loading shared libraries: libsnappy.so.1: cannot open shared object file: No such file or directory
Comment 1 Olivier FAURAX 2020-01-18 15:17:03 CET 
It's strange, lib64snappy is installed!!!

$ rpm -ql lib64snappy1
/usr/lib/.build-id
/usr/lib/.build-id/b3
/usr/lib/.build-id/b3/a3cbc957117df5420bc19de47556e8706e8df1
/usr/lib64/libsnappy.so.1
/usr/lib64/libsnappy.so.1.1.7
/usr/share/doc/lib64snappy1
/usr/share/doc/lib64snappy1/AUTHORS
/usr/share/doc/lib64snappy1/COPYING
/usr/share/doc/lib64snappy1/NEWS
/usr/share/doc/lib64snappy1/README.md
Comment 2 Lewis Smith 2020-01-18 19:27:15 CET 
Re-doing the same thing, I found (see below):
1. chromium-browser requires chromium-browser-stable; which is correctly required by the former.
2. chromium-browser itself does *not* require lib64snappy1
3. chromium-browser-stable *does* require lib64snappy1; which is correctly required by just by the former.
---
 $ ls -l /usr/lib64/ | grep snappy
lrwxrwxrwx  1 root root          18 Hyd   1  2018 libsnappy.so.1 -> libsnappy.so.1.1.7*
-rwxr-xr-x  1 root root       39296 Hyd   1  2018 libsnappy.so.1.1.7*

 # urpmi chromium-browser
I fodloni dibyniaethau, gosodir y pecynnau canlynol:
  Pecyn                          Fersiwn      Rhifyn        Arch    
(cyfrwng "Core Updates")
  chromium-browser               78.0.3904.1> 1.mga7        x86_64  
  chromium-browser-stable        78.0.3904.1> 1.mga7        x86_64  
Parhau i osod 2 becyn? (Y/n) y
    $MIRRORLIST: media/core/updates/chromium-browser-stable-78.0.3904.108-1.mga7.x86_64.rpm
    $MIRRORLIST: media/core/updates/chromium-browser-78.0.3904.108-1.mga7.x86_64.rpm
      1/2: chromium-browser-stable
      2/2: chromium-browser      #############################################

 $ chromium-browser
*worked*, but with several unrelated errors.

 $ urpmq --requires chromium-browser | grep snappy
 $
 $ urpmq --requires chromium-browser-stable | grep snappy
chromium-browser-stable: libsnappy.so.1()(64bit)
 $ urpmq --requires chromium-browser | grep chromium
chromium-browser: chromium-browser-stable[== 73.0.3683.103-1.mga7]   [*n]
 $ urpmq --whatrequires chromium-browser-stable
chromium-browser
 $ urpmq --whatrequires lib64snappy1 | grep chromium
chromium-browser-stable
In fact several things require this lib.
 $ urpmq --whatrequires-recursive  lib64snappy1 | grep chromium
chromium-browser
chromium-browser-stable
 All this is consistent & correct.
---
Did you have chromium-browser-stable already (or is it) installed?
Please do:
 $ ls -l /usr/lib64/ | grep snappy
just to make sure libsnappy.so.1 is there (as listed early in this comment), although its host pkg lib64snappy is installed.

CC: (none) => lewyssmith
Source RPM: chromium-browser => chromium-browser-stable-78.0.3904.108-1.mga7.src.rpm

Comment 3 Olivier FAURAX 2020-01-18 20:08:00 CET 
Can't reproduce anymore :(

Resolution: (none) => INVALID
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.