Re: A note about riscv64 changes
On Wed, 14 Feb 2024 12:29:00 + Peter Robinson wrote: > On Wed, 14 Feb 2024 at 12:07, David Abdurachmanov > wrote: > > > > On Wed, Feb 14, 2024 at 12:49 PM Dan Horák wrote: > > > > > > On Wed, 14 Feb 2024 10:42:52 + > > > "Richard W.M. Jones" wrote: > > > > > > > On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > > > > > 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? > > > > > > > > TBD. > > > > > > > > Koji-shadow specifically is unmaintained. Maybe we'll try to hack > > > > something together with scripts, or get koji-shadow working. > > > > > > on the other hand, it's still tags, targets, buildroots in koji ... > > > > > > I should be able dig out some koji-shadow know-how out of my memory if > > > needed. Those were wonderful years :-) > > > > Many years ago I tried using koji-shadow, but I didn't like what it > > was doing. Cooking something custom seemed easier at that point. These > > Yes, it was never a particularly nice process, but the advantage it > has was it made sure that a package build used the exact same packages > as on the mainline build so you could end up with identical builds and > that was very useful for bugs and build process problems. and with that technique it solves the soname bumps and the use of side tags very effectively, I would consider this the main benefit of koji-shadow Dan > > days we also have side tags, and thus some bootstrap operations happen > > there. Sadly those get removed relatively soonish after the tag gets > > merged. Sometimes before I get a chance to grab it. Otherwise I have a > > good picture of Fedora package land over so many years. > > > > Our "dist-git overlay" is relatively small these days. Should be <300 > > packages, and majority of it was used to bump NVR for rebuilds. > > > > Cheers, > > david > > > > > > > > Dan > > > -- > > > ___ > > > 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 > > -- > > ___ > > 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 > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to
Re: A note about riscv64 changes
On Wed, Feb 14, 2024 at 7:30 AM Peter Robinson wrote: > > On Wed, 14 Feb 2024 at 12:07, David Abdurachmanov > wrote: > > > > On Wed, Feb 14, 2024 at 12:49 PM Dan Horák wrote: > > > > > > On Wed, 14 Feb 2024 10:42:52 + > > > "Richard W.M. Jones" wrote: > > > > > > > On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > > > > > 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? > > > > > > > > TBD. > > > > > > > > Koji-shadow specifically is unmaintained. Maybe we'll try to hack > > > > something together with scripts, or get koji-shadow working. > > > > > > on the other hand, it's still tags, targets, buildroots in koji ... > > > > > > I should be able dig out some koji-shadow know-how out of my memory if > > > needed. Those were wonderful years :-) > > > > Many years ago I tried using koji-shadow, but I didn't like what it > > was doing. Cooking something custom seemed easier at that point. These > One tool to look into could be the one we use for automatically rebuilding Rawhide packages for Fedora ELN: https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distrobuildsync I'd be happy to work with you to extend it for RISC use (though probably not sooner than March, as we've got kind of a lot going on with the CentOS Stream 10 fork from ELN this week and next). -- ___ 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
Re: A note about riscv64 changes
On Wed, 14 Feb 2024 at 12:07, David Abdurachmanov wrote: > > On Wed, Feb 14, 2024 at 12:49 PM Dan Horák wrote: > > > > On Wed, 14 Feb 2024 10:42:52 + > > "Richard W.M. Jones" wrote: > > > > > On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > > > > 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? > > > > > > TBD. > > > > > > Koji-shadow specifically is unmaintained. Maybe we'll try to hack > > > something together with scripts, or get koji-shadow working. > > > > on the other hand, it's still tags, targets, buildroots in koji ... > > > > I should be able dig out some koji-shadow know-how out of my memory if > > needed. Those were wonderful years :-) > > Many years ago I tried using koji-shadow, but I didn't like what it > was doing. Cooking something custom seemed easier at that point. These Yes, it was never a particularly nice process, but the advantage it has was it made sure that a package build used the exact same packages as on the mainline build so you could end up with identical builds and that was very useful for bugs and build process problems. > days we also have side tags, and thus some bootstrap operations happen > there. Sadly those get removed relatively soonish after the tag gets > merged. Sometimes before I get a chance to grab it. Otherwise I have a > good picture of Fedora package land over so many years. > > Our "dist-git overlay" is relatively small these days. Should be <300 > packages, and majority of it was used to bump NVR for rebuilds. > > Cheers, > david > > > > > Dan > > -- > > ___ > > 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 > -- > ___ > 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 -- ___ 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
Re: A note about riscv64 changes
On Wed, Feb 14, 2024 at 12:49 PM Dan Horák wrote: > > On Wed, 14 Feb 2024 10:42:52 + > "Richard W.M. Jones" wrote: > > > On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > > > 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? > > > > TBD. > > > > Koji-shadow specifically is unmaintained. Maybe we'll try to hack > > something together with scripts, or get koji-shadow working. > > on the other hand, it's still tags, targets, buildroots in koji ... > > I should be able dig out some koji-shadow know-how out of my memory if > needed. Those were wonderful years :-) Many years ago I tried using koji-shadow, but I didn't like what it was doing. Cooking something custom seemed easier at that point. These days we also have side tags, and thus some bootstrap operations happen there. Sadly those get removed relatively soonish after the tag gets merged. Sometimes before I get a chance to grab it. Otherwise I have a good picture of Fedora package land over so many years. Our "dist-git overlay" is relatively small these days. Should be <300 packages, and majority of it was used to bump NVR for rebuilds. Cheers, david > > Dan > -- > ___ > 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 -- ___ 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
Re: A note about riscv64 changes
On Wed, 14 Feb 2024 10:42:52 + "Richard W.M. Jones" wrote: > On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > > 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? > > TBD. > > Koji-shadow specifically is unmaintained. Maybe we'll try to hack > something together with scripts, or get koji-shadow working. on the other hand, it's still tags, targets, buildroots in koji ... I should be able dig out some koji-shadow know-how out of my memory if needed. Those were wonderful years :-) Dan -- ___ 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
Re: A note about riscv64 changes
On Wed, Feb 14, 2024 at 10:27:53AM +, Peter Robinson wrote: > 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? TBD. Koji-shadow specifically is unmaintained. Maybe we'll try to hack something together with scripts, or get koji-shadow working. At the moment David rebuilds packages from regular Koji in fedora.riscv.rocks by hand, I think, or at least using some scripts that he has devised. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- ___ 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
Re: A note about riscv64 changes
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
