On Mon, Aug 1, 2022 at 8:56 AM Miro Hrončok <mhron...@redhat.com> wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> will be retired from Fedora 37 approximately one week before branching (next 
> week).
>

The F37 schedule says the retirement occurs on the same day as branching:
https://fedorapeople.org/groups/schedule/f-37/f-37-all-tasks.html
and also, the title of this email says "in 1 week", which is the same
week as branching.

> Policy:
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
>
> The packages in rawhide were not successfully built at least since Fedora 35.
>
> This report is based on dist tags.
>
> Packages collected via:
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
>
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process, please let me
> know and we can work together to get a FESCo approval for that.
>
> If you see a package that can be rebuilt, please do so.
>
>           Package                       (co)maintainers
> ==================================================================
> tinygo                       go-sig, qulogic

It is not entirely correct that tinygo has "not successfully built at
least since Fedora 35." It has been rebuilt in stable branches
multiple times since then, and there are currently no FTBFS bugs open
for them. It *was* FTBFS in Rawhide though, and I have now fixed it.

--
Elliott
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to