On Fri, 2018-05-25 at 15:46 +0000, Zbigniew Jędrzejewski-Szmek wrote:
> Fedora package maintainers,
> 
> FESCo approved an updated policy for packages which fail to build from
> source during mass rebuilds (FTBFS) [1].
> 
> The updated policy is still at 
> https://fedoraproject.org/wiki/Fails_to_build_from_source.
> 
> Highlights:
> 
> - packages which FTBFS are subject to orphaning if there is no
>   maintainer acknowledgement within 8 weeks
> 
> - packages which FTBFS in two consecutive mass rebuilds will be
>   retired soon after the second mass rebuild
> 
> The implementation of this policy hinges on improving the releng
> scripts used to create and manage FTBFS bugs. There is approximately
> two months until the next use of those scripts, so I'm hopeful we'll
> get them working.
> 
> If your package wasn't successfully built for F28, please fix that!

As per the following bug report I did a scratch build for f29 and it passed 
successfully. What shall
I do with the FTBFS bug now?

https://bugzilla.redhat.com/show_bug.cgi?id=1606379

> [1] https://pagure.io/fesco/issue/1890
> [2] https://pagure.io/fesco/issue/1877#comment-509161
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/P3KFTJMDNO42POS5N3Z4UXDNPFGAQH73/
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CGYEZZMQ7G62WRBVWNT74A3EMGBGJFP6/

Reply via email to