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

[email protected]: a decompress error #731

Closed
jfastnacht opened this issue Jan 14, 2020 · 4 comments
Closed

[email protected]: a decompress error #731

jfastnacht opened this issue Jan 14, 2020 · 4 comments

Comments

@jfastnacht
Copy link
Contributor

Looks like the extract_dir makes the installation of puppet-bolt (https://github.com/ScoopInstaller/Main/blob/master/bucket/puppet-bolt.json) fail:

Installing 'puppet-bolt' (1.45.0) [64bit]
Loading puppet-bolt-1.45.0-x64.msi from cache
Checking hash of puppet-bolt-1.45.0-x64.msi ... ok.
Extracting puppet-bolt-1.45.0-x64.msi ... ERROR Exit code was 1603!
Failed to extract files from C:\Users\j.fastnacht\scoop\apps\puppet-bolt\1.45.0\puppet-bolt-1.45.0-x64.msi.
Log file:
~\scoop\apps\puppet-bolt\1.45.0\msi.log

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Main/issues/new?title=puppet-bolt%401.45.0%3a+decompress+error

When I remove extract_dir and adjust bin back to the full path it's working flawlessly. I could either remove the attribute and change back the bin directory or fix the problem with the file extraction, but right now I have no clue what the problem is.

The temporary folder created by scoop when installing is:

[...]\scoop\apps\puppet-bolt\1.45.0_tmp\SourceDir\Puppet Labs\Bolt

Right now it's configured to: "extract_dir": "Puppet Labs\\Bolt",

Any recommendations on how to fix it except for rolling back?

@Ash258
Copy link
Contributor

Ash258 commented Jan 14, 2020

What does ~\scoop\apps\puppet-bolt\1.45.0\msi.log contain?

No issue with/without lessmsi.

image

https://support.microsoft.com/en-us/help/834484/you-receive-an-error-1603-a-fatal-error-occurred-during-installation

Most probable cause

Windows Installer is attempting to install an app that is already installed on your PC.

@jfastnacht
Copy link
Contributor Author

jfastnacht commented Jan 14, 2020

Interesting, it seems that the path is too long:

=== Logging started: 14.01.2020 13:05:05 ===
Error 1304. Error writing to file: C:\Users\j.fastnacht\scoop\apps\puppet-bolt\1.45.0_tmp\SourceDir\Puppet Labs\Bolt\lib\ruby\gems\2.5.0\gems\puppet-6.11.0\spec\fixtures\unit\pops\loaders\loaders\dependent_modules_with_metadata\modules\user\lib\puppet\functions\user\ruby_calling_puppet_init.rb. Verify that you have access to that directory.
=== Logging stopped: 14.01.2020 13:05:59 ===

It's 261 characters, which exceeds the MAX_LENGTH by 1 and I guess that it results in the application not being able to create the file ruby_calling_puppet_init.rb in the sub-directory.

Edit: I'm running Scoop on Windows 8.1 Pro.

@Ash258
Copy link
Contributor

Ash258 commented Jan 14, 2020

scoop checkup should get you info how to enable long path

@jfastnacht
Copy link
Contributor Author

jfastnacht commented Jan 14, 2020

The problem seems to be Windows 8.1, since LongPathsEnabled is, as far as I could figure out, available since Windows 10 (v160), not Win 8.1. I'm reopening this on https://github.com/lukesampson/scoop , since it's a problem with Scoop itself, not the Main bucket.

Edit: There's an open issue (ScoopInstaller/Scoop#2204) regarding this problem already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants