Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1975106 - perl: FTBFS with glibc 2.34: Installed (but unpackaged) file(s) found: /usr/lib64/perl5/features-time64.ph
Summary: perl: FTBFS with glibc 2.34: Installed (but unpackaged) file(s) found: /usr/l...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: perl
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Jitka Plesnikova
QA Contact: Martin Kyral
URL: https://koji.fedoraproject.org/koji/t...
Whiteboard:
Depends On: 1972637
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-23 06:51 UTC by Florian Weimer
Modified: 2023-07-13 02:09 UTC (History)
4 users (show)

Fixed In Version: perl-5.32.1-477.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1972637
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Florian Weimer 2021-06-23 06:51:51 UTC 
This issue will start impacting perl in Red Hat Enterprise Linux 9 once we switch to glibc 2.34.

You can test a fix before glibc 2.34 is merged using this command:

koji -p stream build --scratch c9s-build-side-102-stack-gate git+https://gitlab.com/redhat/centos-stream/rpms/perl#origin/c9s

+++ This bug was initially created as a clone of Bug #1972637 +++

All perls fail to build Fedora 35 with glibc-devel-2.33.9000-18.fc35:

Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/test/rpmbuild/BUILDROOT/perl-5.34.0-479.fc35.x86_64
error: Installed (but unpackaged) file(s) found:
   /usr/lib64/perl5/features-time64.ph


RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/lib64/perl5/features-time64.ph

Tested with glibc-devel-2.33.9000-18.fc35 and and perl-bootstrap:5.32 <https://koji.fedoraproject.org/koji/taskinfo?taskID=70221595>.

Perl build script generates *.ph files from system header files and packages the *.ph files. The latest glibc apparently added a new header file. You need to update "%files ph" section.

Also please port this fix to f33 branch to make perl:5.32 buildable (and make sure not to break building f33 perl in Fedoras < 35).

--- Additional comment from Petr Pisar on 2021-06-16 13:14:19 CEST ---

(In reply to Petr Pisar from comment #0)
> Tested with glibc-devel-2.33.9000-18.fc35 and and perl-bootstrap:5.32
> <https://koji.fedoraproject.org/koji/taskinfo?taskID=70221595>.
> 
Tested with glibc-devel-2.33.9000-18.fc35 and perl-5.34.0-478.fc35 and perl-bootstrap:5.32.

--- Additional comment from Fedora Update System on 2021-06-17 03:30:00 CEST ---

FEDORA-2021-be944825aa has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-be944825aa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-be944825aa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

--- Additional comment from Fedora Update System on 2021-06-17 03:52:48 CEST ---

FEDORA-2021-2eadd2c263 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2eadd2c263`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2eadd2c263

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

--- Additional comment from Fedora Update System on 2021-06-19 03:08:56 CEST ---

FEDORA-2021-be944825aa has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.