Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10117 - gem update --system breaks pacman

Attached to Project: Community Packages
Opened by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 14:09 GMT
Last edited by DaNiMoTh (DaNiMoTh) - Thursday, 10 April 2008, 10:31 GMT
Task Type Bug Report
Category
Status Closed
Assigned To DaNiMoTh (DaNiMoTh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After gem update --system, pacman can't update rubygem

Additional info:
* package version(s)
rubygems-1.1.0-1
* config and/or log files etc.
Targets: rubygems-1.1.0-1

Total Download Size: 0.00 MB
Total Installed Size: 3.60 MB

Proceed with installation? [Y/n] Y
checking package integrity...
(1/1) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000002.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000003.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000004.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000005.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000006.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000007.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000008.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000009.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000010.html exists in filesystem
rubygems: /usr/lib/ruby/gems/1.8/doc/rubygems-1.1.0/rdoc/classes/Gem.src/M000011.html exists in filesystem
...

Steps to reproduce:
if rubygems < 1.1.0
gem update --system
pacman -Syu rubygems
This task depends upon

Closed by  DaNiMoTh (DaNiMoTh)
Thursday, 10 April 2008, 10:31 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see last comment.
Comment by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 14:19 GMT
Workaround:
1. backup: tar cjf gems.bak.tar.bz2 `bzcat rubygems.conflicting.files.bz2 | xargs`
2. rm -f `bzcat rubygems.conflicting.files.bz2 | xargs`
3. pacman -Su rubygems
Comment by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 14:21 GMT
list of conflicting files reported by pacman
   rubygems.conflicting.files.bz2 (4.3 KiB)
Comment by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 14:22 GMT
P.S. I did gem update --system because I read 'Newsletter for April 3, 2008'
Comment by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 18:53 GMT
bender02 suggests a better idea in http://bbs.archlinux.org/viewtopic.php?pid=353043 :
pacman -Sf rubygems
Comment by Carlos Eduardo (cems) - Tuesday, 08 April 2008, 18:56 GMT
I think it's not a bug. It was my fault to manually update rubygems and conflicting files should be expected. Sorry.

Loading...