#167 all branches are shown as "active" since PDC retirement
Closed: Fixed by amedvede. Opened by decathorpe.

for example:
https://src.fedoraproject.org/rpms/rust-sequoia-sq/branches?branchname=rawhide

Either the data about active branches needs to switch to a different data source, or the distinction could just be dropped from the UI.


Taking a look.

It's because the script looking for a dead.package file on branches so since there is no any dead.package files it shows that all branches are active

Possible - but until a few weeks ago, even branches that did not have dead.package showed as "Inacitve" if they were associated with EOL Fedora or EPEL releases. So checking for dead.package can't be the only thing that happens here.

@decathorpe This was before decommission of PDC, so the information was probably taken from it.

Yes - that's what this ticket is about (see issue title)? :laughing:

Maybe it would be good to create the dead.package file for all already EOLed branches.

Why? ... replacing the call to PDC with one to bodhi should be easy enough

From what I saw, there's a bug in https://pagure.io/pagure/blob/master/f/pagure/themes/srcfpo/templates/repo_branches.html which checks only for dead.package. If a condition of active releases is added, that should be fixed.

I mean inactive releases. That under Inactive there will be all releases that are EOL + active ones with a dead.package. Would that be correct?

Why? ... replacing the call to PDC with one to bodhi should be easy enough

Oh, I thought that every application is now checking for dead.package in the branch. If there is an easier way to get the info from Bodhi I'm for it.

No, for non-EOL branches, you need to check for dead.package.

But the list of EOL branches you can get from bodhi now that PDC is gone.

I mean inactive releases. That under Inactive there will be all releases that are EOL + active ones with a dead.package. Would that be correct?

Yup, that's exactly what we want.

Metadata Update from @zlopez:
- Issue assigned to amedvede

Fix in PR https://pagure.io/pagure/pull-request/5505

PR is merged now, so when pagure will have new release and I ensure that deployed changes are working as expected, I will close this ticket

It will take some time, the changes will be in next pagure release, so this ticket will be closed until future issues)

Metadata Update from @amedvede:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata