Arch Linux

Please read this before reporting a bug:

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

REPEAT: Do NOT report bugs for outdated packages!

FS#23408 - [ruby] should no longer conflict with rubygems

Attached to Project: Arch Linux
Opened by Peter Lewis (petelewis) - Wednesday, 23 March 2011, 19:56 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 10 April 2011, 19:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No


The ruby package in [extra] conflicts with "rubygems", since it replaced the old rubygems package. However, now everyone should have moved past this and the only rubygems package in existence is in the AUR (rubygems1.8). It would be nice if ruby could no longer conflict with "rubygems" so that rubygems1.8 can "provide" rubygems and then gem packages can depend on "rubygems" and be satisfied by either ruby or ruby1.8+rubygems1.8.

Note that ruby can/should still provide "rubygems", that isn't a problem.

This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 10 April 2011, 19:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in trunk