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.

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

Trying to upgrade a manually installed mod fails if it conflicts with another mod #4225

Open
JonnyOThan opened this issue Oct 6, 2024 · 4 comments
Labels
Core (ckan.dll) Issues affecting the core part of CKAN Relationships Issues affecting depends, recommends, etc.

Comments

@JonnyOThan
Copy link
Contributor

Repro:

  1. Install Deferred using CKAN
  2. Manually install RasterPropMonitor (any version)
  3. Hit Refresh in CKAN so that it auto-detects RPM
  4. Check the "upgrade" box for RPM and hit Apply

Result:

image

image

This may have something to do with the fact that RPM is incorrectly auto-detected; the DLL name is RasterPropMonitor but the module that contains the DLL is RasterPropMonitor-Core.

@JonnyOThan JonnyOThan added Bug Something is not working as intended Core (ckan.dll) Issues affecting the core part of CKAN labels Oct 6, 2024
@HebaruSan HebaruSan changed the title Trying to upgrade a manually installed mod can trigger false conflict errors Trying to upgrade a manually installed mod fails if it conflicts with another mod Oct 19, 2024
@HebaruSan
Copy link
Member

HebaruSan commented Oct 20, 2024

Hey @JonnyOThan, what happens if you swap steps 1 and 2? I.e., manually install RPM and then try to install Deferred?

@HebaruSan HebaruSan added Relationships Issues affecting depends, recommends, etc. and removed Bug Something is not working as intended labels Oct 20, 2024
@JonnyOThan
Copy link
Contributor Author

It won't let you install:
image
image

@HebaruSan
Copy link
Member

Thanks, that's what I thought; at the end of step 2, your registry is already in an "inconsistent" state that it's not supposed to be able to get to, since a conflict is sastisfied among the installed mods and DLLs. So what happens after that is kind of beside the point.

@JonnyOThan
Copy link
Contributor Author

The upgrade operation would have removed that conflict though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core (ckan.dll) Issues affecting the core part of CKAN Relationships Issues affecting depends, recommends, etc.
Projects
None yet
Development

No branches or pull requests

2 participants