boxstarter
boxstarter copied to clipboard
chocolatey
chocolatey\chocolatey\chocolatey\.... temp download paths
2.9.2 - seeing packages getting downloaded into weird folders (and then failing).
C:\Users\dgardiner\AppData\Local\Temp\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey\chocolatey.squirrel-lock-0205C670A9D776F56D17A8FB985A520ADEE61F89: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
I have submitted https://github.com/chocolatey/choco/pull/1211 to fix this issue.
Just guessing, but could it be that config.CacheLocation.EndsWith("chocolatey") would be false if CacheLocation had a trailing slash/backslash?
see https://github.com/chocolatey/choco/pull/1232. I tested this build against boxstarter and the nested directories appear to be gone.
Ugg - sorry I missed this - and I looked at this one the other day and chuckled about
You can never have to much chocolatey!
https://github.com/chocolatey/choco/pull/1233 is the correct PR, just for reference.
nope not resolved yet, boxstarter 2.10.3 + choco 0.10.7 still have this problem
yes we had to revert to choco 0.10.5 which "rebroke" this but fixed larger problems.
but current (2.10.3) boxstarter installs choco 0.10.7, at least that's what the log says
boxstarter doesn't install chocolatey unless your script installs it. It just calls into a chocolatey dll.
oh maybe you are referring to the bootstrapper which does install the latest choco if it is not installed in order to install boxstarter. That would install 0.10.7 but it does not use it in boxstarter runs.
I thought I had seen this as well - should have linked the two. https://github.com/chocolatey/choco/pull/1233#issuecomment-318479205
Matt, any idea when a new version of Boxstarter will be released that will have a version of Chocolatey which addresses this issue? We are unable to use boxstarter with this issue in it. :(
Are there any known workarounds? Can i reset the cache path after each package install?
@mwrock Hello Matt, I am using the latest version of Boxstarter bootstrapper, that installs the latest version of Chocolatey. I am seeing this issue as well when i try to install a series of packages using the text file on Git gist. Is there an easy way to workaround this issue?
I worked around this issue by using an alternative cache location, instead of the user temp directory. Basically , for each choco install, i explicitly use an alternative cache location as follows: cinst 7zip --version 9.22 --source https://abc.com/ --cacheLocation "$env:SystemDrive\TCAgentSetupCache"
Hope this helps.
@Sebbl22 @ericrlarson
Thanks @kirannhegde. Your solution worked for me.
It seems, that the $env:temp Variable gets overwritten for the current PowerShell session, because I first tried cinst 7zip --cacheLocation "$env:temp\ChocoCache", wich also resulted in C:\Users\abc\AppData\Local\Temp\chocolatey\chocolatey\chocolatey\chocolatey after several installs.
cinst 7zip --cacheLocation "$env:userprofile\AppData\Local\ChocoCache" however worked just fine. Hint: The cache location must exist. I use the follwing command in my Boxstarter script: New-Item -Path "$env:userprofile\AppData\Local\ChocoCache" -ItemType directory -Force
This is still causing problems, and the workaround isn't working for me with the latest BoxStarter. Even though cacheLocation is being passed in, Chocolatey is still using %TEMP% which has the chocolatey\chocolatey\chocolatey problem :-(
Looks like if you apply --cache-location to every choco call in your BoxStarter script, you might be ok. That includes choco pin, and windows features
