Bug 822814

Summary: ruby-ncurses uses deprecated symbol (macro) STR2CSTR
Product: [Fedora] Fedora Reporter: Roman Rakus <rrakus>
Component: ruby-ncursesAssignee: Šimon Lukašík <slukasik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jesusr, slukasik, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 18:07:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Use StringValuePtr instead of STR2CSTR none

Description Roman Rakus 2012-05-18 09:07:37 UTC 
Description of problem:
I'm using an app which is using ruby-ncurses, however in F17 it's not working - decribed in summary

Version-Release number of selected component (if applicable):
ruby-ncurses-1.3.1-3.fc17.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
ruby: symbol lookup error: /usr/lib64/ruby/vendor_ruby/ncurses_bin.so: undefined symbol: STR2CSTR

Expected results:


Additional info:
see http://ruby.11.n6.nabble.com/1-9-2-breaks-ncurses-STR2CSTR-pls-help-td3133059.html
Comment 1 Roman Rakus 2012-05-31 09:12:56 UTC 
Created attachment 587994 [details]
Use StringValuePtr instead of STR2CSTR

This patch will use StringValuePtr. The package compiles clearly, however using it shows out regression: it is reacting on arrows on the keyboard, but it is not reacting on any other keys.
Comment 2 Jesus M. Rodriguez 2013-02-28 16:37:29 UTC 
Where do we stand with this bug? It's currently affecting my package: tpp

https://bugzilla.redhat.com/show_bug.cgi?id=906799
Comment 3 Šimon Lukašík 2013-03-14 10:05:09 UTC 
This issue shall be fixed in upstream commit 3bde2dc28de756a140a536c856dea66f2d8f733f
Comment 4 Šimon Lukašík 2013-03-17 18:16:55 UTC 
Patched version hits the f19 and rawhide branches.

Given the regression described by Roman, I am not convinced
about pushing this patch to the released versions of Fedora.
Could you please test your dependent applications first?
Comment 5 Fedora End Of Life 2013-07-04 06:31:45 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2013-08-01 18:07:10 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.