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#29435 - [rubyripper] can't be launched

Attached to Project: Community Packages
Opened by Maxime Anvari (icetwy) - Friday, 13 April 2012, 18:17 GMT
Last edited by Dave Reisner (falconindy) - Friday, 13 April 2012, 18:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Rubyripper can't be launched with ruby 1.9 (after the installation ruby-locale & ruby-gettext).

Additional info:
* package version(s): rubyripper 0.6.2-2
* config and/or log files etc. See the attached log file.


Steps to reproduce:

Install ruby 1.9
(Install ruby-locale & ruby-gettext)
Run Rubyripper from command line (rrip_gui)
Can't launch.
   log (3.2 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Friday, 13 April 2012, 18:57 GMT
Reason for closing:  Won't fix
Additional comments about closing:  ruby-gettext and ruby-locale conflict with this package. AUR packages are deleted.
Comment by Alexander F. Rødseth (xyproto) - Friday, 13 April 2012, 18:33 GMT
Confirmed. Works when ruby-locale and ruby-gettext are not installed, crashes when they are installed.

Output: http://ix.io/2iU
Comment by Dave Reisner (falconindy) - Friday, 13 April 2012, 18:36 GMT
Yes, this is why I moved ruby-locale and ruby-gettext to the AUR... they're ancient and have not been updated in a long time. They really have no use on an up to date Arch system.
Comment by Maxime Anvari (icetwy) - Friday, 13 April 2012, 18:43 GMT
Well, even when I remove ruby-locale & ruby-gettext, it doesn't work and outputs the same error.
Comment by Alexander F. Rødseth (xyproto) - Friday, 13 April 2012, 18:44 GMT
Ok. Add them to "conflicts" for convenience, then? Or just close as "won't fix"?

Loading...