Bug 13240 - file "ruby.pc" contains invalid "ruby_version" variable
Summary: file "ruby.pc" contains invalid "ruby_version" variable
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-04-20 11:28 CEST by François Andriot
Modified: 2014-11-29 22:06 CET (History)
0 users

See Also:
Source RPM: ruby-2.0.0.p247-8.mga4.src.rpm
CVE:
Status comment:


Attachments

Description François Andriot 2014-04-20 11:28:20 CEST
Description of problem:
The development file "ruby.pc" lacks the the "ruby_version" value.
This causes FTBFS for 3rd party programs that needs this variable to check the ruby version using the pkg-config command.

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

How reproducible:
Check file "/usr/lib64/pkgconfig/ruby.pc" and look at line "ruby_version=".
You'll notice there is no value at all.

Steps to Reproduce:
1. Type command "pkg-config ruby --modversion"
2. See there is not output.
3. Manually modify file "/usr/lib64/pkgconfig/ruby.pc" and set "ruby_version=2.0.0"
4. Type command "pkg-config ruby --modversion"
5. See there is output "2.0.0"



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-04-21 18:11:50 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => pterjan

Comment 1 Pascal Terjan 2014-04-21 19:00:40 CEST
This is probably due to building with--with-ruby-version=

It seems Fedora has a workaround:
http://pkgs.fedoraproject.org/cgit/ruby.git/tree/ruby.spec#n453
Comment 2 Pascal Terjan 2014-04-21 19:23:45 CEST
Fix verified in cauldron:

[pterjan@chopin ruby]$ pkg-config ruby --modversion
2.0.0
Comment 3 Pascal Terjan 2014-04-21 19:25:39 CEST
I have committed the fix in the 4 branch, not sure if this is worth an update or if we can wait for next security one.
Comment 4 Pascal Terjan 2014-11-29 22:06:41 CET
Some updates have already been released, containing the fix

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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