-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Universal Blue Yum / DNF Repo #579
Comments
im willing to maintain the infra |
This comment was marked as off-topic.
This comment was marked as off-topic.
While a yum repo could be nice, We have an additional possibility. Using scratch containers as a cache layer. We already do this with akmods and now have one for sync. Depending on how we do tagging we could cache things appropriately and refer to them by a convenient name. |
Hi, @noelmiller. I'm helping the Main Repos team manage their backlog and am marking this issue as stale. Your issue highlights the challenges of managing package dependencies across multiple repositories, which is affecting the build process. You suggested two potential solutions: creating a dedicated repository or collaborating with Fyra Labs. In the comments, bigpod98 offered to maintain the infrastructure, while geoffreysmith pointed out issues with version locking in rpm-ostree, and m2Giles proposed using scratch containers for better management. Could you please let us know if this issue is still relevant to the latest version of the Main Repos repository? If it is, feel free to comment here to keep the discussion alive. Otherwise, you can close the issue yourself, or it will be automatically closed in 7 days. Thank you! |
Problem
Currently, we are pulling packages in from several different repositories and have minimal control on when packages are published, which can create skew in our build process.
Current Repos we are pulling in from:
Potential Solutions
Pros
Cons
Pros
Cons
Blocker
This a blocker for the following:
Feedback
I am looking for help and feedback on what we would like to do moving forward.
Main points of contention are:
Discord Thread
https://discord.com/channels/1072614816579063828/1240355645199486976
The text was updated successfully, but these errors were encountered: