[Bug]: Unable to revert to current stable mod version if using bleeding edge development version.

[byt3c]

Is there an existing issue for this?

• I have checked the existing issues for an existing issue. I even actually looked at the ones that are pinned to the top!

Operating System

windows10

CKAN Version

1.36.1.25226

Games

KSP 1

Game Version

1.12.5.3190

Did you make any manual changes to your game folder (i.e., not via CKAN)?

none

Describe the bug

When certain mods are getting update especially around community resource pack there is unsatisfied dependency error.

Checking other game instances for possible duplicate installed files...
Inconsistencies were found:
* Unsatisfied dependency CommunityResourcePack needed for: CryoTanks 1.6.7
* Unsatisfied dependency CommunityResourcePack needed for: CryoEngines 1:2.0.8
* Unsatisfied dependency CommunityResourcePack needed for: NearFuturePropulsion 1.3.6
* Unsatisfied dependency CommunityResourcePack needed for: RealFuels 1:v15.12.0.0
Your game folder has been returned to its original state.
Error during installation!
If the above message indicates a download error, please try again. Otherwise, please open an issue for us to investigate.
If you suspect a metadata problem: https://github.com/KSP-CKAN/NetKAN/issues/new/choose
If you suspect a bug in the client: https://github.com/KSP-CKAN/CKAN/issues/new/choose

The problem is that the mod is already in its newest version (in this example v112.0.2-bleeding-edge.1) and v112.0.1 is the stable release.

CKAN is not recognizing that the mod is already installed, moreover when forcing downgrade either by policy or manually selecting mod to install, CKAN reinstalls the bleeding edge one despite claiming it reverted the version.

Steps to reproduce

registry.json

install bleeding edge of community resource pack, try to revert

or

Install bleeding edge community resource pack and update dependent mods (from RP1 for example)

Relevant log output

Checking other game instances for possible duplicate installed files...
Inconsistencies were found:
* Unsatisfied dependency CommunityResourcePack needed for: CryoTanks 1.6.7
* Unsatisfied dependency CommunityResourcePack needed for: CryoEngines 1:2.0.8
* Unsatisfied dependency CommunityResourcePack needed for: NearFuturePropulsion 1.3.6
* Unsatisfied dependency CommunityResourcePack needed for: RealFuels 1:v15.12.0.0
Your game folder has been returned to its original state.
Error during installation!
If the above message indicates a download error, please try again. Otherwise, please open an issue for us to investigate.
If you suspect a metadata problem: https://github.com/KSP-CKAN/NetKAN/issues/new/choose
If you suspect a bug in the client: https://github.com/KSP-CKAN/CKAN/issues/new/choose

[HebaruSan]

Finally found #4398, which was where we fixed the disabled Apply button that was the original complaint on Discord related to this.

[byt3c]

any way of recognizing bleeding edge as fulfilling the dependency or enabling downgrade from common version menu ? or i'm missing something and it works as intended?

[HebaruSan]

@byt3c, please share the registry.json file from the CKAN folder in your game folder. That would allow me to investigate in order to begin answering questions like that.

[byt3c]

registry.json

[HebaruSan]

Thanks @byt3c!

... OK, using that file to borrow your setup, I'm still able to switch versions of CommunityResourcePack to and from the prerelease without any issues. Maybe you're doing something differently from how I'm doing it? Please share click-by-click, key-by-key details of exactly how you end up getting to the point of seeing that error message. I need to be able to reproduce what you're seeing in order to investigate it.

[byt3c]

Let me wait for next update (i'll switch the community resource pack to bleeding edge) and once issue reappears i'll post exact path. The problem occurs if you have bleeding edbe community resource pack installed, AND there are other mods to update that depend on it like the list i posted earlier. Then auto update fails unless you manually switch to older stable version.

While having this error, simply selecting checkbox during group update or deselecting all updates and selecting reinstall from popup menu after selecting older version also results in mod not being updated.

[HebaruSan]

The problem occurs if you have bleeding edbe community resource pack installed, AND there are other mods to update that depend on it like the list i posted earlier

Oh, OK. I can set up that test case by installing older versions of those mods. Was it specifically these that were to be updated?

• CryoTanks
• CryoEngines
• NearFuturePropulsion
• RealFuels

[byt3c]

You can try those one release earlier. If needed we can meet somewhere on discord so I can either guide you through to reproduce it or i'll try to do it when you will tell me what to do to get to my earlier state

[HebaruSan]

Hmm, I just tried that (start with your registry.json data, revert to older versions of those four mods, change CRP to the prerelease version, upgrade the four reverted mods), and still everything is working fine!

Something's still not the same in what we're doing, either in the setup or the steps. Maybe you could record a video of how you get the error to appear?

[byt3c]

This is how it looked before update, i'll wait for next mods to update and will then engage with testing.

[HebaruSan]

@byt3c, sounds good. In the meantime I'll close this issue so it doesn't stay open forever. We'll re-open it when we have more info from you. Thanks!