RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2144873 - epel8-next annobin needs to be rebuilt
Summary: epel8-next annobin needs to be rebuilt
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: annobin
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Johnny Hughes
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-22 15:44 UTC by Germano Massullo
Modified: 2023-07-18 14:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-28 17:09:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-140209 0 None None None 2022-11-22 17:34:25 UTC

Description Germano Massullo 2022-11-22 15:44:49 UTC
keepassxc build on epel8-next is failing
https://koji.fedoraproject.org/koji/taskinfo?taskID=94420875
due annobin not being rebuilt after gcc change

https://koji.mbox.centos.org/koji/buildinfo?buildID=22974
https://koji.mbox.centos.org/koji/buildinfo?buildID=22442
latest annobin build is older than gcc build

Comment 1 Nick Clifton 2022-11-22 16:01:14 UTC
(In reply to Germano Massullo from comment #0)
> keepassxc build on epel8-next is failing
> https://koji.fedoraproject.org/koji/taskinfo?taskID=94420875
> due annobin not being rebuilt after gcc change
 
How do I trigger a new build of annobin for epel8-next ?

Comment 2 Florian Weimer 2022-11-22 16:06:18 UTC
(In reply to Nick Clifton from comment #1)
> (In reply to Germano Massullo from comment #0)
> > keepassxc build on epel8-next is failing
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=94420875
> > due annobin not being rebuilt after gcc change
>  
> How do I trigger a new build of annobin for epel8-next ?

You don't. We need to fix whatever annobin/gcc sync issues we still have. Have we already backported the automated sync to 8? If yes and there are still issues, it must be due to bug 2124562.

Comment 3 Germano Massullo 2022-11-22 16:15:06 UTC
(In reply to Nick Clifton from comment #1)
> (In reply to Germano Massullo from comment #0)
> > keepassxc build on epel8-next is failing
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=94420875
> > due annobin not being rebuilt after gcc change
>  
> How do I trigger a new build of annobin for epel8-next ?

I should have reported it against CentOS Stream 8, I selected epel8 by mystake

Comment 4 Germano Massullo 2022-11-22 16:19:48 UTC
(In reply to Germano Massullo from comment #3)
> (In reply to Nick Clifton from comment #1)
> > (In reply to Germano Massullo from comment #0)
> > > keepassxc build on epel8-next is failing
> > > https://koji.fedoraproject.org/koji/taskinfo?taskID=94420875
> > > due annobin not being rebuilt after gcc change
> >  
> > How do I trigger a new build of annobin for epel8-next ?
> 
> I should have reported it against CentOS Stream 8, I selected epel8 by
> mystake


I cannot reassign the ticket the CentOS Stream 8:
============
 You tried to change the Assignee field from nickcATredhat.com to mcermakATredhat.com, but only the assignee of the bug, or a user with the required permissions may change that field. 
============

Comment 5 Nick Clifton 2022-11-23 12:03:03 UTC
(In reply to Germano Massullo from comment #4)
 
> I cannot reassign the ticket the CentOS Stream 8:
> ============
>  You tried to change the Assignee field from nickcATredhat.com to
> mcermakATredhat.com,  

Ok, I have changed the assignee.

Comment 6 Johnny Hughes 2022-11-23 15:46:11 UTC
OK .. I have incremented annobin and created a new build for CentOS 8 Stream:

https://koji.mbox.centos.org/koji/taskinfo?taskID=392857

It will be rolled into the next compose.

Comment 7 Johnny Hughes 2022-11-23 16:18:21 UTC
This is not the first time we have had this issue .. working on a test to add to the t_functional test suite to check this before c8-stream compose releases.

Comment 8 Nick Clifton 2022-11-28 17:09:31 UTC
rebuild has completed.  no more need for this bz.


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