Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
That doesn't make sense. Installing a dependency shouldn't ever mark the depending module as incompatible.
Cause
Scatterer's self-conflict relationship trips this check:
CKAN/Core/Registry/AvailableModule.cs
Lines 123 to 133 in 2119b58
... but only when it's installed, via this block:
CKAN/Core/Registry/AvailableModule.cs
Lines 99 to 102 in 2119b58
... passed from here:
CKAN/Core/Registry/Registry.cs
Lines 708 to 713 in 2119b58
... while checking dependencies for compatibility here:
CKAN/Core/Registry/Registry.cs
Lines 537 to 541 in 2119b58
Changes
Now when checking that conflicts are OK for an available module, we filter any copies of itself (i.e., with matching identifier) out of the list of potential conflicting modules. This prevents the Scatterer self conflict from breaking modules that depend on Scatterer.
We could try ignoring the self conflict relationships instead, but that would miss other modules that provide the conflicting identifier, which presumably would be part of why such conflicts would be set up in the first place.
Fixes #2719 (the part of it that can't be explained as expected behavior).