Andreas Stieger changed bug 1226404
What Removed Added
Status NEW CONFIRMED
Assignee packagehub-bugs@suse.com dcermak@suse.com
CC   Andreas.Stieger@gmx.de

Comment # 1 on bug 1226404 from Andreas Stieger
$ zypper in --dry-run --download-only ruby2.5-rubygem-bcrypt_pbkdf
ruby2.5-rubygem-bcrypt_pbkdf-1.1
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 2 NEW packages are going to be installed:
  ruby2.5-rubygem-bcrypt_pbkdf ruby2.5-rubygem-bcrypt_pbkdf-1.1

2 new packages to install.
Overall download size: 0 B. Already cached: 128.7 KiB. Download only.

Backend:  classic_rpmtrans --dry-run --download-only
Continue? [y/n/v/...? shows all options] (y): y
In cache ruby2.5-rubygem-bcrypt_pbkdf-1.1-1.1.0-bp156.3.3.x86_64.rpm           
                    (1/2),  64.3 KiB
In cache ruby2.5-rubygem-bcrypt_pbkdf-1.1.0-bp156.3.3.x86_64.rpm               
                    (2/2),  64.3 KiB    
Checking for file conflicts:
....................................................................................[error]
Detected 1 file conflict:

File
/usr/lib64/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0/bcrypt_pbkdf-1.1.0/bcrypt_pbkdf_ext.so
  from install of
     ruby2.5-rubygem-bcrypt_pbkdf-1.1-1.1.0-bp156.3.3.x86_64 (Main Repository)
  conflicts with file from install of
     ruby2.5-rubygem-bcrypt_pbkdf-1.1.0-bp156.3.3.x86_64 (Main Repository)

File conflicts happen when two packages attempt to install files with the same
name but different contents. If you continue, conflicting files will be
replaced losing the previous content.
Continue? [yes/no] (no):


openSUSE:Backports:SLE-15-SP5:Update/rubygem-bcrypt_pbkdf
openSUSE:Backports:SLE-15-SP6:Update/rubygem-bcrypt_pbkdf
[...]
openSUSE:Backports:SLE-15-SP5:Update/rubygem-bcrypt_pbkdf-1.1
openSUSE:Backports:SLE-15-SP6:Update/rubygem-bcrypt_pbkdf-1.1

In general our packaging policies ask for an rpm conflict between packages with
overlapping files. But there may be a duplication of packages here?


You are receiving this mail because: