Hi Richard,

> A quick note that you may be seeing pull requests for riscv64 changes
> against your packages, like these examples:
>
> https://src.fedoraproject.org/rpms/ghc/pull-request/7
> https://src.fedoraproject.org/rpms/zlib-ng/pull-request/11
> https://src.fedoraproject.org/rpms/gdal/pull-request/21
>
> For many years we have been building Fedora for the RISC-V
> architecture on a separate build system at
> http://fedora.riscv.rocks/koji/ , and maintaining downstream patches
> against dist-git in http://fedora.riscv.rocks:3000/rpms/
> (Most of this work was done by David Abdurachmanov, not me.)

I'm very happy to see these start to land, let me know if you need any
assistance.

> I'm trying to get as much of this stuff back into Fedora dist-git,
> although only (hopefully!) where it doesn't break ordinary builds and
> isn't intrusive.  Obviously I may get this wrong sometimes so feel
> free to make comments if you disagree with changes.
>
> Some time, with any luck soon, we will be creating a new Koji instance
> with FAS authentication which will allow anyone to optionally build
> their packages on RISC-V builders.  And then later in the year we may
> be in a position with the availability of new hardware to discuss
> adding RISC-V as a regular architecture.  (We're not there yet as
> current hardware is far too slow to force it on Fedora developers.)

Will this instance run with koji-shadow to properly mirror the builds
with all the appropriate NVR dependencies to properly mirror Fedora
primary builds?

Peter
--
_______________________________________________
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