-
Notifications
You must be signed in to change notification settings - Fork 154
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
Conda package with an incorrect subdir makes repo unreadable. #529
Comments
Yes, we certainly should not return an error here. I think conda just ignores the package subdir in this case. Is that correct? |
I think the other way around, it would ignore the global subdir and use the package subdir. |
Yeah, that would make more sense. However the code in subdir_data.py contains
I think that this means it overwrites the subdir from the package. |
Oh, see issue #502 |
Just curious, what happens if they're (accidentally) not equal and the package subdir overrides the global subdir? In my situation, and others I believe, the package is actually in the wrong subdirectory, so it won't be possible to download it from the subdir indicated in the package either. |
It would be great if one way or another this would either skip the package and print an error, or overwrite the subdir for the package. Returning an error here ruins a lot of people's days until the remote repo can be fixed. The conda Personally, I would expect and want a warning and the mismatched packages skipped as that would force the mismatch to be noticed/fixed, but wouldn't disrupt users who are uninterested in the broken package. |
…e is a conflict This is what classic conda does, so we also need to do it. Fixes issue #529
I changed the code so that it overwrites the package subdir with the info subdir. |
I think this is the line in question:
libsolv/ext/repo_conda.c
Lines 314 to 319 in 5dc4f81
In my situation, I have a custom subdir
linux-64-foo
, but one broken package has the subdir listed aslinux-64
. This package makes the entire repo unreadable. I think instead of a hard error, this should be a warning so the repo can still be used.Also see mamba-org/mamba#2363
The text was updated successfully, but these errors were encountered: