Bug 1562170 - Upgrade path broken: file /usr/lib64/libgdbm_compat.so.4.0.0 from install of gdbm-libs-1:1.14.1-4.fc29.x86_64 conflicts with file from package gdbm-1:1.14-3.fc28.x86_64
Summary: Upgrade path broken: file /usr/lib64/libgdbm_compat.so.4.0.0 from install of ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdbm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Skalický
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 16:55 UTC by Richard W.M. Jones
Modified: 2018-06-06 11:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-06 11:57:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2018-03-29 16:55:09 UTC
Description of problem:

Upgrading from gdbm 1:1.14-3.fc28 to 1:1.14.1-4.fc29 is broken:

$ sudo dnf install gdbm-libs  --best --enablerepo=koji\*
Last metadata expiration check: 0:03:29 ago on Thu 29 Mar 2018 17:49:11 BST.
Dependencies resolved.
================================================================================
 Package           Arch           Version                 Repository       Size
================================================================================
Installing:
 gdbm-libs         x86_64         1:1.14.1-4.fc29         rawhide          57 k

Transaction Summary
================================================================================
Install  1 Package

Total size: 57 k
Installed size: 120 k
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] gdbm-libs-1.14.1-4.fc29.x86_64.rpm: Already downloaded               
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  file /usr/lib64/libgdbm_compat.so.4.0.0 from install of gdbm-libs-1:1.14.1-4.fc29.x86_64 conflicts with file from package gdbm-1:1.14-3.fc28.x86_64

Error Summary
-------------

Version-Release number of selected component (if applicable):

See above.

How reproducible:

100%

Comment 1 Richard W.M. Jones 2018-03-29 17:05:42 UTC
An extremely hairy and dangerous workaround for this bug is:

# dnf --setopt protected_packages= shell
> remove gdbm
> install gdbm
Package gdbm-1:1.14-3.fc28.x86_64 is already installed, skipping.
> run
================================================================================
 Package            Arch          Version                  Repository      Size
================================================================================
Upgrading:
 gdbm               x86_64        1:1.14.1-4.fc29          rawhide        121 k
 gdbm-devel         x86_64        1:1.14.1-4.fc29          rawhide         64 k
Installing dependencies:
 compat-gdbm        x86_64        1.14-5.fc28              rawhide         60 k
 gdbm-libs          x86_64        1:1.14.1-4.fc29          rawhide         57 k

Transaction Summary
================================================================================
Install  2 Packages
Upgrade  2 Packages

Total size: 302 k
Total download size: 245 k
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] gdbm-libs-1.14.1-4.fc29.x86_64.rpm: Already downloaded               
(2/4): compat-gdbm-1.14-5.fc28.x86_64.rpm       112 kB/s |  60 kB     00:00    
(3/4): gdbm-devel-1.14.1-4.fc29.x86_64.rpm      115 kB/s |  64 kB     00:00    
(4/4): gdbm-1.14.1-4.fc29.x86_64.rpm            214 kB/s | 121 kB     00:00    
--------------------------------------------------------------------------------
Total                                           138 kB/s | 245 kB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Installing       : gdbm-libs-1:1.14.1-4.fc29.x86_64                       1/6 
  Upgrading        : gdbm-1:1.14.1-4.fc29.x86_64                            2/6 
  Upgrading        : gdbm-devel-1:1.14.1-4.fc29.x86_64                      3/6 
  Running scriptlet: gdbm-devel-1:1.14.1-4.fc29.x86_64                      3/6 
  Installing       : compat-gdbm-1.14-5.fc28.x86_64                         4/6 
  Running scriptlet: compat-gdbm-1.14-5.fc28.x86_64                         4/6 
  Running scriptlet: gdbm-devel-1:1.14-3.fc28.x86_64                        5/6 
  Cleanup          : gdbm-devel-1:1.14-3.fc28.x86_64                        5/6 
  Cleanup          : gdbm-1:1.14-3.fc28.x86_64                              6/6 
  Running scriptlet: gdbm-1:1.14-3.fc28.x86_64                              6/6 
Running as unit: run-r58e3f99c55484fe08a17e440f04bf91c.service
Running as unit: run-rf9636d881986445ca19de42aded7a492.service
  Verifying        : gdbm-libs-1:1.14.1-4.fc29.x86_64                       1/6 
  Verifying        : compat-gdbm-1.14-5.fc28.x86_64                         2/6 
  Verifying        : gdbm-1:1.14.1-4.fc29.x86_64                            3/6 
  Verifying        : gdbm-devel-1:1.14.1-4.fc29.x86_64                      4/6 
  Verifying        : gdbm-devel-1:1.14-3.fc28.x86_64                        5/6 
  Verifying        : gdbm-1:1.14-3.fc28.x86_64                              6/6 

Installed:
  compat-gdbm.x86_64 1.14-5.fc28        gdbm-libs.x86_64 1:1.14.1-4.fc29       

Upgraded:
  gdbm.x86_64 1:1.14.1-4.fc29         gdbm-devel.x86_64 1:1.14.1-4.fc29        

> quit

Comment 2 Marek Skalický 2018-04-05 10:14:10 UTC
gdbm-1.14.1-4.fc28 was pushed to stable 4 days ago (https://bodhi.fedoraproject.org/updates/FEDORA-2018-02e145266f)

Could you try the upgrade with this new package?

Comment 3 Richard W.M. Jones 2018-04-11 10:42:45 UTC
I don't have this machine any longer.

Comment 4 Marek Skalický 2018-06-06 11:57:02 UTC
Update of gdbm from f28 to f29 is possible. So closing this bug.

Feel free to reopen it.


Note You need to log in before you can comment on or make changes to this bug.