On 9/22/19 3:40 PM, Miro Hrončok wrote:
On 22. 09. 19 14:37, Till Hofmann wrote:
Hi all,
So I've just been notified that tolua++ has been retired, which is a
dependency of one of my packages (fawkes). BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1736911
I've closed this bug because it "was already retired", not because of
that bug.
The package was actually retired more than a month ago in here:
https://bugzilla.redhat.com/show_bug.cgi?id=1676145#c12
Based on this rule:
"7. A week before the mass branching, any packages which still have open
FTBFS bugs from the previous release will be retired."
I see, so the package was already FTBFS in F30. So the F31 FTBFS was
actually a duplicate. It would have helped if it was marked as such, but
I understand that's easier said than done.
To put it differently, the guidelines were completely ignored. The
package was retired 6 days after the initial FTBFS bug, without any
announcement.
No, they were not ignored at all.
The comment "your package has not been built successfully in 31.
Action is required from you" isn't helping either, as the package has
long been retired at that time.
Yes, that's why I closed the bugzilla. See
https://pagure.io/releng/issue/8478
So can we please make sure that guidelines apply to everybody, also
and especially to scripts?
They do.
You're right, as this was FTBFS in F30 already, it's all good.
So the guidelines allow package retirement without any announcement on
devel. That's certainly unexpected, at least to me. I also don't think
this is a good idea, because maintainers of packages that depend on the
retired package are still clueless until it's too late. Or do they get a
separate notification?
I still find it somewhat inconsistent that basically every rule in the
FTBFS guidelines is about notifying people, but (7) allows retirement
without any prequisites other than being FTBFS for 2 releases -- no
announcement, no orphaning.
Kind regards,
Till
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
