riscv/planning
11
1
Fork 0
Code Issues 28 Pull requests Projects Releases Packages Wiki Activity Actions

Bootstrap Fedora ELN on riscv64 #32

New issue
Open
opened 2026-09-17 15:50:43 +00:00 by kashyapc · 2 comments
kashyapc commented 2026-09-17 15:50:43 +00:00
Owner
Copy link

There is some interest in bootstrapping Fedora ELN (Enterprise Linux Next) so that Fedora downstream distros can have a view into how packages will behave with their specific config flags, macros, etc.

We discussed this on a community call with a few ELN and a few Fedora RISC-V maintainers. Bootstrapping a new architecture on ELN hasn't happened before, so there are some details that need to be worked out.

Some potential steps:

  • Figure out the of builder capacity required (K3s?)
  • Create ELN tags in RISC-V Koji
  • Fedora Message Bus events for RISC-V Koji -- @kevin is looking at this
  • Figure out ELN automation that doesn't require Bodhi for merging side tags -- Yaakov
  • Check if any packages that are part of ELN content set are patched in RISC-V 'dist-git', but aren't upstreamed yet
  • David talked about "pause flag" (FIXME)
  • Investigate Pungi -- we have a ticket about it here: #15

This is an incomplete list, @davidlt, @abologna and others, please feel free to fill in, correct, amend.

There is some interest in bootstrapping Fedora ELN (Enterprise Linux Next) so that Fedora downstream distros can have a view into how packages will behave with their specific config flags, macros, etc. We discussed this on a community call with a few ELN and a few Fedora RISC-V maintainers. Bootstrapping a new architecture on ELN hasn't happened before, so there are some details that need to be worked out. Some potential steps: - Figure out the of builder capacity required (K3s?) - Create ELN tags in RISC-V Koji - Fedora Message Bus events for RISC-V Koji -- @kevin is looking at this - Figure out ELN automation that doesn't require Bodhi for merging side tags -- Yaakov - Check if any packages that are part of ELN content set are patched in RISC-V 'dist-git', but aren't upstreamed yet - David talked about "pause flag" (FIXME) - Investigate Pungi -- we have a ticket about it here: https://forge.fedoraproject.org/riscv/planning/issues/15 This is an incomplete list, @davidlt, @abologna and others, please feel free to fill in, correct, amend.
yselkowitz commented 2026-09-17 16:00:18 +00:00
Copy link

I'm filling out my action items in https://github.com/fedora-eln/eln/issues/622

I'm filling out my action items in https://github.com/fedora-eln/eln/issues/622
kashyapc commented 2026-10-08 15:11:02 +00:00
Author
Owner
Copy link

Some more notes from a follow-up meeting on this:

  • Get the RISC-V specific patches merged in the set of packages listed in this ELN ticket: cmake,java-25-openjdk, kernel, llvm, luajit, mozjs140, nodejs26, toolbox. (@hrw is working on some of these)

  • We haven't had a successful GCC build on K3 in months. Tracking the investigation here: #36

  • Figure out Koji configuration

  • David noted that we have to make sure that not all related tasks of a package build go to K3 -- this needs Koji "hub" policy tweaking

  • Create Koji "channel" (a group of builders) for RVA23 hardware

  • Reach out to K3 machine maintainers in Fedora RISC-V build pool and request to enable side tags

  • Criteria for ELN: if any ELN packages has a patch we're carrying for it, it should be merged in Rawhide (modulo temporary and unavoidable exceptions?). This is necessary to automate builds.) ELN content set: https://tiny.distro.builders/view-all-source-package-name-list--view-eln.txt

Some more notes from a follow-up meeting on this: - Get the RISC-V specific patches merged in the set of packages listed in this [ELN ticket](https://github.com/fedora-eln/eln/issues/632): cmake,java-25-openjdk, kernel, llvm, luajit, mozjs140, nodejs26, toolbox. (@hrw is working on some of these) - We haven't had a successful GCC build on K3 in months. Tracking the investigation here: https://forge.fedoraproject.org/riscv/planning/issues/36 - Figure out Koji configuration - David noted that we have to make sure that not _all_ related tasks of a package build go to K3 -- this needs Koji "hub" policy tweaking - Create Koji "channel" (a group of builders) for RVA23 hardware - Reach out to K3 machine maintainers in Fedora RISC-V build pool and request to enable side tags - Criteria for ELN: if any ELN packages has a patch we're carrying for it, it should be merged in Rawhide (modulo temporary and unavoidable exceptions?). This is necessary to automate builds.) ELN content set: https://tiny.distro.builders/view-all-source-package-name-list--view-eln.txt
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
riscv/planning#32
No description provided.