Bug 1923526

Summary:	rubygem-ruby-vips: FTBFS in Fedora rawhide/f34
Product:	[Fedora] Fedora	Reporter:	Fedora Release Engineering <releng>
Component:	rubygem-ruby-vips	Assignee:	Mamoru TASAKA <mtasaka>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	mtasaka, pvalena
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-ruby-vips-2.0.17-4.fc36	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-25 14:30:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1917540
Bug Blocks:	1868278

Description Fedora Release Engineering 2021-02-01 17:03:18 UTC

rubygem-ruby-vips failed to build from source in Fedora rawhide/f34

https://koji.fedoraproject.org/koji/taskinfo?taskID=60912183


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
Please fix rubygem-ruby-vips at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
rubygem-ruby-vips will be orphaned. Before branching of Fedora 35,
rubygem-ruby-vips will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Ben Cotton 2021-02-09 15:55:39 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Fedora Release Engineering 2021-02-14 04:26:26 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 3 Fedora Release Engineering 2021-02-14 04:26:26 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 4 Mamoru TASAKA 2021-03-02 10:40:31 UTC

Basically, the needed patch is https://github.com/libvips/ruby-vips/commit/e0203e9ed8be27ed195b4c5b0ca87c35daff36cc , for lib/vips/object.rb (only).
To make the above patch be applied cleanly, https://github.com/libvips/ruby-vips/commit/2ecd377375ef7f0fa182253a1b06980b2a9b358d (for lib/vips/object.rb only) is needed.

The trouble is: after applying the above 2 changes (for lib/vips/object.rb), test suite passes on x86_64, however it segfaults on other architecture: looking like always on ppc64le, randomly on i686:

https://koji.fedoraproject.org/koji/taskinfo?taskID=62918778
https://koji.fedoraproject.org/koji/taskinfo?taskID=62924315

I guess this is due to some bugs on vips side (but just a guess).

Comment 5 Mamoru TASAKA 2021-08-14 03:01:57 UTC

(In reply to Mamoru TASAKA from comment #4)
> Basically, the needed patch is
> https://github.com/libvips/ruby-vips/commit/
> e0203e9ed8be27ed195b4c5b0ca87c35daff36cc , for lib/vips/object.rb (only).
> To make the above patch be applied cleanly,
> https://github.com/libvips/ruby-vips/commit/
> 2ecd377375ef7f0fa182253a1b06980b2a9b358d (for lib/vips/object.rb only) is
> needed.
> 
> The trouble is: after applying the above 2 changes (for lib/vips/object.rb),
> test suite passes on x86_64, however it segfaults on other architecture:
> looking like always on ppc64le, randomly on i686:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=62918778
> https://koji.fedoraproject.org/koji/taskinfo?taskID=62924315
> 
> I guess this is due to some bugs on vips side (but just a guess).

Again, after applying the above two patches, rebuild rubygem-ruby-vips segfaults only on ppc64le,
and looks like vips is segfaulting (only on ppc64le) and it seems it is due to 
bug 1917540  .

Comment 6 Mamoru TASAKA 2021-08-25 14:30:36 UTC

Fixed in rubygem-ruby-vips-2.0.17-4.fc36