Learn more about these different git repos.
Other Git URLs
Looking at some recently retired packages due to FTBFS, I must say that the commit message is completely useless. For example the commit message [1] is "rubygem-rspec-longrun fails to build from source: https://bugzilla.redhat.com/show_bug.cgi?id=1675952" It contains "rubygem-rspec-longrun", but this is useless, because I know into what repository I am looking. OTOH, it does not mentions that the package was retired.
So my proposal for the commit message is "Retired FTBFS: https://bugzilla.redhat.com/show_bug.cgi?id=1675952".
And actually if the commit details contained some brief description of the policy + link, it would be even better.
Anytime soon.
When we don't retire packages.
The "retired" status of the package is not obvious from the Pagure UI, so the state of the package is not obvious on the first look.
@churchyard PTAL
What about:
Retired, fails to build: https://bugzilla.redhat.com/show_bug.cgi?id=1675952
I'd like to avoid the FTBFS acronym, because it is a tribal knowledge.
Sure, why not. Although with proper explanation in commit message, I would not be afraid of FTBFS :blush:
For reference, the message is hardcoded in https://pagure.io/releng/blob/master/f/scripts/retire-ftbfs-packages.sh
I am not sure where this script is now?
Gone.
https://pagure.io/releng/c/069946f135b950b05183db7dcb2ea2702db1a259?branch=main
The amount of packages I retire for FTBFS is close to zero, I do that manually.
Metadata Update from @churchyard: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.