Yeah, do you think this is a dupe of #960? There, we keep the EOL info with the branches just like we do for rpms... we just need to teach MBS to respect that.

Given the original description, I think we need a mechanism to retire modules even before EOL. Of course that shouldn't be a common thing to do.

I'm just curious if there's been any consideration given to this RFE?

Even if the answer is "no", could we at least agree on what should be used as the indicator for an unused/obsolete module? I'd suggest using the dead.package file indicator as is done for EOL Fedora packages. It might also be good to allow a dead.module file to be used instead to satisfy those persnickety types. :smirk:

@ralph @psabata @langdon - Do you have any thoughts on the question I posed in my previous comment about selecting and standardizing on an indicator for unused/obsolete modules in dist-git?

dead.module sounds good to me.

@psabata only dead.module? Or would it be acceptable to also allow dead.package so the existing fedpkg retire ... command can be used as-is to clear out the dist-git branch?

Since we're changing things here, we could also change rpkg or not? :)

At the moment, only fedpkg has the retire option. Although, oddly enough, rpkg does have logic to detect the dead.package file to recognize retired packages. I'll look into moving that to rpkg and add handling for dead.module.

Closing this in favor of #1021.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/963

Please continue any further discussion there.