https://pagure.io/dusty/failed-composes/issue/133
which runs down to:
2018-04-05 18:15:37 [ERROR ] Compose run failed: RPM(s) not found for sigs: ['0608b895']. Check log for details. Unsigned packages: nmh-1.7.1-4.el6
Unsigned content from EPEL seem to leak out every couple of weeks
Please do not close this bug for a couple months, so I have a target locale at which to compile future observations
This bug is invalid. Do note that if there is unsigned content, the entire compose will fail, and none of the unsigned builds leak.
Metadata Update from @puiterwijk: - Issue close_status updated to: Cant Fix - Issue status updated to: Closed (was: Open)
hmmm ...
... wonder how to self assign this -- I probably need some right added.
Oh mighty granters of rights, please so endow me
Alternatively, please make me the Assignee
Metadata Update from @herrold: - Issue status updated to: Open (was: Closed)
This is the wrong place to file these kinds of bugs, this is a releng issue: https://pagure.io/releng/. And when these happen, the person on push duty should be fixing this, and as said, no unsigned things leak out of the build system to users.
Can you show when an unsigned package has actually leaked out?
There are multiple things in releng which basically fail the compose which is what the original ticket is alluding to: an unsigned package was seen in koji, the compose failed to happen, and without a compose nothing was pushed as it is an all or nothing.
If this has happened recently, it means that something else has happened in the entire tree process which needs to be addressed.
Metadata Update from @smooge: - Issue status updated to: Open (was: Closed)
Metadata Update from @smooge: - Issue assigned to smooge
please re-close as tracked elsewhere
as Reporter, I do not see the needed 'button'
Metadata Update from @herrold: - Issue close_status updated to: Fixed
found the close button down a level, so closed it
Login to comment on this ticket.