FS#65373 - [swig] ruby 2.7 bindings bug.

Attached to Project: Arch Linux
Opened by bartus (bartus) - Tuesday, 04 February 2020, 14:56 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 March 2023, 21:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

There's no way to build `ruby=2.7` bindings with current version of swig :/
Upstream issue: https://github.com/swig/swig/issues/1689
There's some patches suggestion but no definitive solution yet.
Effected packages I'm aware of: AUR/yafaray.
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 23 March 2023, 21:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  swig 4.1.0-1
Comment by bartus (bartus) - Tuesday, 04 February 2020, 14:59 GMT
I'd like to dement previous statement, there's already a patch merged into upstream master.
Could we bring it to Arch without waiting for upstream release, since we ship `ruby=2.7`?
https://github.com/swig/swig/pull/1692
Comment by bartus (bartus) - Tuesday, 04 February 2020, 15:09 GMT
Additional effected pacakge: community/marisa
Comment by Michel (xantares) - Tuesday, 07 February 2023, 10:55 GMT
hello,

anything preventing to update to swig 4.1.1 and close this ?

I'm also waiting for all the fixes in 4.1
Comment by loqs (loqs) - Tuesday, 07 February 2023, 15:50 GMT
The following all fail to build with swig 4.1.1. (Have trivial patches)
ming [1] does not support python 3 so not really an upstream issue until that is addressed.
libteam [2]
libsigrok [3]

python-pymupdf fails check with swig.4.1.1

[1] https://github.com/libming/libming/issues/177
[2] https://github.com/jpirko/libteam/issues/73
[3] https://sigrok.org/bugzilla/show_bug.cgi?id=1827
Comment by Michel (xantares) - Thursday, 23 March 2023, 12:36 GMT
I guess this can be closed now as the package has been updated

Loading...