Master PDF: RPM file conflict

English Applications
#1

This has not happened to me before so Im stuck. I have a license for Master PDF which like the adobe product allows creation and editing of secure PDF docs.
Following my switch from leap to tumbleweed i have not been able to install it. I have downloaded the latest version and got this:

file /usr/share from install of master-pdf-editor-5.8.20-1.x86_64 conflicts with file from package filesystem-84.87-3.1.x86_64

It this something I can fix in Tumbleweed or is this an issue for the vendor to fix?

Thanks in advance

#2

Sounds to me like a vendor fix may be needed to account for the usr/merge filesystem changes around 6 months ago in TW. When was that master-pdf-editor rpm released?

#3

Nothing to fix in Tumbleweed.

**erlangen:~ #** zypper install https://code-industry.net/public/master-pdf-editor-5.8.20-qt5.x86_64.rpm 
Loading repository data... 
Reading installed packages... 
Resolving package dependencies... 

The following NEW package is going to be installed:
  master-pdf-editor 

1 new package to install. 
Overall download size: 12.2 MiB. Already cached: 0 B. After the operation, additional 53.9 MiB will be used. 
**Continue? [y/n/v/...? shows all options] (y): **
Retrieving package master-pdf-editor-5.8.20-1.x86_64                                                                                                                                                                                       (1/1),  12.2 MiB ( 53.9 MiB unpacked) 
master-pdf-editor-5.8.20-qt5.x86_64.rpm: 
    Package is not signed!

master-pdf-editor-5.8.20-1.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned]
**Abort, retry, ignore? [a/r/i] (a): **i 

Checking for file conflicts: .............................................................................................................................................................................................................................................[done] 
(1/1) Installing: master-pdf-editor-5.8.20-1.x86_64 ......................................................................................................................................................................................................................[done] 
**erlangen:~ #**
#4

Well thats interesting. I just copied and pasted the same command and it worked for me too. Are you able to explain why it would not install from the downloaded file using:

sean@SUSEpc:~> sudo rpm --install master-pdf-editor-5.8.20-qt5.x86_64.rpm 
[sudo] password for root:  
        file /usr/share from install of master-pdf-editor-5.8.20-1.x86_64 conflicts with file from package filesystem-84.87-3.1.x86_64

It makes no sense to me…

#5

I have no idea. However zypper installs readily:

**erlangen:~ #** zypper install /home/karl/Downloads/master-pdf-editor-5.8.20-qt5.x86_64.rpm                  
Loading repository data... 
Reading installed packages... 
Resolving package dependencies... 

The following NEW package is going to be installed:
  master-pdf-editor 

1 new package to install. 
Overall download size: 12.2 MiB. Already cached: 0 B. After the operation, additional 53.9 MiB will be used. 
**Continue? [y/n/v/...? shows all options] (y): **
Retrieving package master-pdf-editor-5.8.20-1.x86_64                                                                                                                                                                                       (1/1),  12.2 MiB ( 53.9 MiB unpacked) 
master-pdf-editor-5.8.20-qt5.x86_64.rpm: 
    Package is not signed!

master-pdf-editor-5.8.20-1.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned]
**Abort, retry, ignore? [a/r/i] (a): **i 

Checking for file conflicts: .............................................................................................................................................................................................................................................[done] 
(1/1) Installing: master-pdf-editor-5.8.20-1.x86_64 ......................................................................................................................................................................................................................[done] 
**erlangen:~ #**
#6

I presume packagers of master-pdf-editor are goofing and should fix their packages:

**erlangen:~ #** rpm -V filesystem 
.........    /usr/share (replaced) 
**erlangen:~ #**
#7

I assume that rpm does only (try to) do what it is asked for. And it fails because of the situation.

zypper does check the whole situation and acts accordingly, it will e.g. install extra packages when they are dependencies, or offer you to choose a solution as in this case.

IMHO it is always better on an openSUSE system to install an rpm using zypper. It will also take a note that something is installed, etc.

#8

RPM is correct here.

zypper does check the whole situation and acts accordingly, it will e.g. install extra packages when they are dependencies

It has nothing to do with dependencies. zypper does equivalent of “rpm --nodeps --force --noscripts” and evaluates dependencies and conflicts itself. In this case filesystem package has /usr/share with modes 0555 (r-xr-xr-x) while master-pdf package has /usr/share with modes -755 (rwxr-xr-x). So forcing installation makes this directory writable.

RPM allows directories “shared” between packages as long as their attributes are identical. Here attributes are different so RPM quite correctly refuses to install (without forcing installation). Zypper pretends to know better than RPM but does not implement this check.