Skip to content
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.

Sign up for GitHub

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

Jump to bottom

clobber-registry: fix panic when no winner can be found #554

Closed
wolfv opened this issue Mar 5, 2024 · 0 comments · Fixed by #556
Closed

clobber-registry: fix panic when no winner can be found #554

wolfv opened this issue Mar 5, 2024 · 0 comments · Fixed by #556

Comments

@wolfv
Copy link
Contributor

wolfv commented Mar 5, 2024

When all clobbering packages are removed at once, no winner can be found. We currently use an expect there, but we should just ignore this situation (all files are already removed so nothing left to do for the unclobbering).

I have a fix ready for this,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: removal of multiple packages that clobber each other wolfv/rattler
1 participant
@wolfv