-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug] innounp (and hence scoop) doesn't support inno setup 6.3 #6157
Comments
looks like this should have been fixed with #6028 but that doesn't seem to be the case? > scoop uninstall -p main/innounp
Uninstalling 'innounp' (0.50).
Removing shim 'innounp.shim'.
Unlinking ~\scoop\apps\innounp\current
Removing persisted data.
'innounp' was uninstalled.
> scoop install milnak/knobkraftorm
WARN Purging previous failed installation of knobkraftorm.
ERROR 'knobkraftorm' isn't installed correctly.
Removing older version (2.4.0).
'knobkraftorm' was uninstalled.
Installing 'innounp' (0.50) [64bit] from 'Main' bucket
Loading innounp050.rar from cache
Checking hash of innounp050.rar ... ok.
Extracting innounp050.rar ... done.
Linking ~\scoop\apps\innounp\current => ~\scoop\apps\innounp\0.50
Creating shim for 'innounp'.
'innounp' (0.50) was installed successfully! |
The mitigation given in other bugs is "scoop install versions/innounp-unicode" which seems to fix the problem, but is unideal. Why not just set innounp-unicode to the default? |
For now, manifest authors can force this as needed, e.g. |
While this may be a temporary, as a possible dependency of Scoop Core, |
Bug Report
Current Behavior
install milnak/knobkraftorm
will fail because the exe uses innosetup 6.3
Expected Behavior
Should extract
Possible Solution
Use innounpacker which supports later innosetup versions. I have a manifest for this here
The text was updated successfully, but these errors were encountered: