Bug 2119676 - [RHEL9][FTBFS] tzdata-2022c-1.el9 FTBFS on Red Hat Enterprise Linux 9 - 9.1
Summary: [RHEL9][FTBFS] tzdata-2022c-1.el9 FTBFS on Red Hat Enterprise Linux 9 - 9.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: tzdata
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-19 06:54 UTC by OSCI Bakery Bot
Modified: 2023-07-18 14:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-19 15:28:35 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-131508 0 None None None 2022-08-19 07:00:11 UTC

Description OSCI Bakery Bot 2022-08-19 06:54:44 UTC
tzdata failed to build from source in Red Hat Enterprise Linux Red Hat Enterprise Linux 9 - 9.1.

It is now *your* responsibility to debug the issue and submit new build.
Please don't close this bug until the build failure will be fixed
and a successful build is done.

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=47211052

Please check the Brew build failure and handle it as any other Brew build failure of your package.
In case you think this was a temporary issue and rebuild should fix it,
you can initiate this rebuild by using:

~~~

$ rhpkg clone tzdata

$ rhpkg switch-branch rhel-9-main

$ rhpkg build --target rhel-9.1.0-candidate

~~~

For details on automatic synchronization of builds for Red Hat Enterprise Linux 9 - 9.1,
see the RHEL Developer Guide:

https://one.redhat.com/rhel-developer-guide/#con_distrobaker_assembly_build-tools-and-pipeline

This Bugzilla bug, as well as the Brew build, is generated by the https://docs.engineering.redhat.com/display/catalog/distrobaker.


Note You need to log in before you can comment on or make changes to this bug.