[FFe] FTBFS with glibc 2.32

Bug #1897895 reported by Lucas Kanashiro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ruby2.7 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

As reported by the latest Groovy archive rebuild made by doko, ruby2.7 FTBFS on all arches due to some changes in the new glibc. Take a look at the amd64 build log:

https://launchpadlibrarian.net/499859053/buildlog_ubuntu-groovy-amd64.ruby2.7_2.7.1-3build1_BUILDING.txt.gz

Two upstream patches need to be backported in order to fix the build failure, they are:

https://github.com/ruby/ruby/commit/a19228f878d
https://github.com/ruby/ruby/commit/72c02aa4b79

Those patches do not introduce new features nor change the feature set but since we are in Beta freeze and ruby2.7 is seeded in ubuntu-budgie: daily-live, these changes require approval before uploading them.

Related branches

description: updated
description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hey! Feel free to upload. Bugfixes do not require any FFe's, as uploads land in the Unapproved queue regardless for ubuntu-release members to review.

Changed in ruby2.7 (Ubuntu):
status: New → Triaged
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

According to sil2100 these changes do not require a FFe:

<sil2100> kanashiro: yeah, from what I see this doesn't need an FFe, just upload!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ruby2.7 - 2.7.1-3ubuntu1

---------------
ruby2.7 (2.7.1-3ubuntu1) groovy; urgency=medium

  * Backport upstream patches to fix FTBFS with glibc 2.32 (LP: #1897895)
    - d/p/0010-brace-the-fact-that-lchmod-2-can-EOPNOTSUPP.patch
    - d/p/0011-Moved-not-implemented-method-tests-Bug-16662.patch

 -- Lucas Kanashiro <email address hidden> Tue, 29 Sep 2020 16:07:54 -0300

Changed in ruby2.7 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.