You are not logged in.
I did like it was told in newsletter for April 3, 2008. But now I have:
[root@silverhawk ~]# pacman -Qs rubygems
local/rubygems 1.0.1-1
A package management framework for the Ruby programming language
[root@silverhawk ~]# gem --version
1.1.0
Will it break something when upgrading rubygems from pacman? If so, how can I undo the manual upgrade?
Thank you
Offline
Today I saw it breaks the package manager!
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
...
Offline
Workaround in http://bugs.archlinux.org/task/10117
Offline
Offline
What happened is quite natural, if you understand how does pacman work.
1. Pacman remembers which files were installed with which package.
2. If you 'gem --update system', the pacman's list of files belonging to rubygems package is no longer accurate, since files from old version have been removed and files from the new version have been introduced into the filesystem.
3. When the new rubygems pacman package comes out, of course it will contain files, which are already in the filesystem (by manual update), and so pacman will complain that some files that it's about to copy over are already there.
All in all, I think the workaround is unnecessarily complicated. You don't need to archive the conflicting files, just overwrite them (they are the same anyway) -> pacman -Sf rubygems.
EDIT: By the way, this happens every time you update something manually, without waiting for a pacman package to appear. If you *really* need to update, just use ABS, bump up the version number, and makepkg a new package.
@kensai: If you could squeeze a note about this to the news, it would be excellent; although I don't think there are too many people affected by this, so maybe this thread is enough.
Last edited by bender02 (2008-04-08 15:21:50)
Offline
@kensai: If you could squeeze a note about this to the news, it would be excellent; although I don't think there are too many people affected by this, so maybe this thread is enough.
Yeah, I'll add the link to this thread. Thanks.
Offline