Bug 1232255 - Broken rubygem-psych ?
Summary: Broken rubygem-psych ?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygems
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1256924 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-16 11:30 UTC by Răzvan Sandu
Modified: 2015-08-25 18:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-18 12:29:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Răzvan Sandu 2015-06-16 11:30:03 UTC
Hello,


Description of problem:

As of June 16th, 2015, package rubygem-psych seems to be broken in Fedora 22 for i686.

Trying to (re)install, I get:


[root@zeus ~]# dnf reinstall rubygems
Last metadata expiration check performed 0:06:43 ago on Tue Jun 16 14:18:57 2015.
Dependencies resolved.
================================================================================
 Package              Arch          Version                 Repository     Size
================================================================================
Installing:
 rubygem-psych        i686          2.0.8-40.fc22           fedora         85 k
Reinstalling:
 rubygems             noarch        2.4.5-40.fc22           fedora        265 k

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

Total download size: 351 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): rubygem-psych-2.0.8-40.fc22.i686.rpm      82 kB/s |  85 kB     00:01    
(2/2): rubygems-2.4.5-40.fc22.noarch.rpm        229 kB/s | 265 kB     00:01    
--------------------------------------------------------------------------------
Total                                           113 kB/s | 351 kB     00:03     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Installing  : rubygem-psych-2.0.8-40.fc22.i686                            1/3 
Error unpacking rpm package rubygem-psych-2.0.8-40.fc22.i686
error: unpacking of archive failed on file /usr/share/ruby/psych: cpio: rename
  Reinstalling: rubygems-2.4.5-40.fc22.noarch                               2/3 
error: rubygem-psych-2.0.8-40.fc22.i686: install failed
  Erasing     : rubygems-2.4.5-40.fc22.noarch                               3/3 
  Verifying   : rubygems-2.4.5-40.fc22.noarch                               1/3 
rubygem-psych-2.0.8-40.fc22.i686 was supposed to be installed but is not!
  Verifying   : rubygem-psych-2.0.8-40.fc22.i686                            2/3 
  Verifying   : rubygems-2.4.5-40.fc22.noarch                               3/3 

Reinstalled:
  rubygems.noarch 2.4.5-40.fc22                                                 

Installed:
  rubygem-psych.i686 2.0.8-40.fc22         



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

rubygem-psych.i686 2.0.8-40.fc22


Best regards,
Răzvan

Comment 1 Vít Ondruch 2015-06-17 11:15:15 UTC
I am wondering, how you got the system into this state in the first place. There is not possible to install rubygems without rubygem-psych, so how it comes, that your log states:

Installing:
 rubygem-psych        i686          2.0.8-40.fc22           fedora         85 k


And you might be interested to take a look at bug 988490

Comment 2 Răzvan Sandu 2015-06-18 12:29:16 UTC
Hello,

Initially, both rubygems and rubygem-psych were installed via yum. I've *manually* erased rubygem-psych via rpm, intentionally breaking dependencies, after the error occured.

Thank you for pointing me at bug 988490; now the present bug is solved just by removing that empty directory manually  and reinstalling both packages via dnf.

Răzvan

Comment 3 Paul DeStefano 2015-08-25 18:30:39 UTC
*** Bug 1256924 has been marked as a duplicate of this bug. ***


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