Vulkan was retired at https://pagure.io/releng/issue/6948
But rpm is still in repo. All other packages retired on same ticket are gone but that one is still there. What's the issue with this retirement? According git repo it was retired ok.
On Wed, Sep 20, 2017 at 10:03 AM, Tuomo Soini tis@foobar.fi wrote:
Vulkan was retired at https://pagure.io/releng/issue/6948
But rpm is still in repo. All other packages retired on same ticket are gone but that one is still there. What's the issue with this retirement? According git repo it was retired ok.
It's not reporting blocked in koji [1]
[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=23126
On Wed, Sep 20, 2017 at 10:17:12AM +0100, Peter Robinson wrote:
On Wed, Sep 20, 2017 at 10:03 AM, Tuomo Soini tis@foobar.fi wrote:
Vulkan was retired at https://pagure.io/releng/issue/6948
But rpm is still in repo. All other packages retired on same ticket are gone but that one is still there. What's the issue with this retirement? According git repo it was retired ok.
It's not reporting blocked in koji [1]
The workflow should be that pdc-updater[0] updates PDC after getting the fedmsg notification of the dead.package file, it does not seem to have updated PDC, though[1]. Therefore PDC needs to be updated with the right EOL dates. pdc-updater contains some kind of manual feature to check for dead.package files maybe it can also update (all) wrong PDC entries.
block_retired.py --branch epel7 vulkan [2]
should fix this, but it only works on a system with a kerberos keytab iirc.
Kind regards Till
[0] https://github.com/fedora-infra/pdc-updater
[1] https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch=epel...
[2] https://pagure.io/releng/blob/master/f/scripts/block_retired.py
epel-devel@lists.fedoraproject.org