quality/rmdepcheck
5
0
Fork 1
Code Issues 9 Pull requests 1 Projects Releases Packages Activity Actions

Make ELN testing possible as desired by ELN team #37

New issue
Closed
opened 2026-04-29 19:52:14 +00:00 by adamwill · 5 comments
adamwill commented 2026-04-29 19:52:14 +00:00
Owner
Copy link

See ci/tickets#555 (comment) . We have an awkward situation with ELN.

In ELN, some packages are buildroot-only - they only appear in the buildroot, not in the composed variants. @yselkowitz does not want us to report repoclosure issues in buildroot-only packages, so he does not want us simply using the buildroot as the base repo as we previously were.

So we did quality/os-autoinst-distri-fedora#533 , but I think that was not sophisticated enough. We just switched to using the variant repos from the latest ELN compose as the base repos. But buildroot-only packages may depend on other buildroot-only packages. So for installability purposes - i.e. when checking the repoclosure of the repo containing the packages under test - we should have the buildroot repo available to the solver. But we need to achieve that without checking the repoclosure of the buildroot repo in the "repoclosure" phase, where we try to detect new dependency issues in the base repos caused by the packages under test.

One way to do this would be to allow specifying "non-checked base repos" or something - they get "modified", and are available to the solver, but we do not run repoclosure checks on them.

Another way would be to allow separating the "repoclosure" and "installability" phases somehow so you could specify different base repos for each.

See https://forge.fedoraproject.org/ci/tickets/issues/555#issuecomment-677112 . We have an awkward situation with ELN. In ELN, some packages are buildroot-only - they only appear in the buildroot, not in the composed variants. @yselkowitz does not want us to report repoclosure issues in buildroot-only packages, so he does not want us simply using the buildroot as the base repo as we previously were. So we did https://forge.fedoraproject.org/quality/os-autoinst-distri-fedora/pulls/533 , but I think that was not sophisticated enough. We just switched to using the variant repos from the latest ELN compose as the base repos. But buildroot-only packages may depend on other buildroot-only packages. So for *installability* purposes - i.e. when checking the repoclosure of the *repo containing the packages under test* - we should have the buildroot repo available to the solver. But we need to achieve that *without* checking the repoclosure of the buildroot repo in the "repoclosure" phase, where we try to detect new dependency issues *in the base repos* caused by the packages under test. One way to do this would be to allow specifying "non-checked base repos" or something - they get "modified", and are available to the solver, but we do not run repoclosure checks on them. Another way would be to allow separating the "repoclosure" and "installability" phases somehow so you could specify different base repos for each.
adamwill added this to the Sprint 8 project 2026-04-29 23:17:09 +00:00
adamwill commented 2026-04-29 23:17:31 +00:00
Author
Owner
Copy link

Adding to current sprint as I want to clear this up while it's in my head, after I noticed the problem.

Adding to current sprint as I want to clear this up while it's in my head, after I noticed the problem.
adamwill changed title from Allow separate base repos for 'repoclosure' and 'installability' checks, and/or allow disabling repoclosure check of some base repos to Make ELN testing possible as desired by ELN team 2026-05-01 16:22:08 +00:00
adamwill commented 2026-05-02 07:25:35 +00:00
Author
Owner
Copy link

This got more complicated after some discussion with yselkowitz, bumping points.

This got more complicated after some discussion with yselkowitz, bumping points.
adamwill modified the project from Sprint 8 to Sprint 9 2026-05-05 15:23:11 +00:00
adamwill commented 2026-05-09 01:23:48 +00:00
Author
Owner
Copy link

Progress: the refactor is basically done, but need to make tox happy, including adding tests for the EL 'wrapper' (which is no longer a wrapper, so maybe I should rename it too...)

Progress: the refactor is basically done, but need to make tox happy, including adding tests for the EL 'wrapper' (which is no longer a wrapper, so maybe I should rename it too...)
adamwill commented 2026-05-12 01:03:20 +00:00
Author
Owner
Copy link

Tox is now happy with everything except the missing test coverage, so I'll figure out how to cover this new bit, then merge.

Tox is now happy with everything *except* the missing test coverage, so I'll figure out how to cover this new bit, then merge.
adamwill commented 2026-05-19 06:55:58 +00:00
Author
Owner
Copy link

This is merged as of Friday. Yay.

This is merged as of Friday. Yay.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
eln-wrapper
alternate-base
nonchecked-base
el9-fix-adam
el9-fix-cursor
ai-code-review-test
binary-test
verbose
1.1.0
1.0.2
1.0.1
1.0.0
Labels
Clear labels
  
ai-review-please
Request AI review for a pull request

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
 This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 9
Assignees
Clear assignees
No assignees
adamwill
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#539 Adjust rmdepcheck to use EL wrapper when it's ready
quality/os-autoinst-distri-fedora
Reference
quality/rmdepcheck#37
No description provided.