-
Notifications
You must be signed in to change notification settings - Fork 1k
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
"Failed to modify resources" error #488
Comments
I'm hitting the same issue when trying to specify a network share as a release directory. Am continuing investigation but if anyone has ideas they are welcome |
What happens when you run that command yourself? |
Works fine =/ |
@JakeGinnivan Are you sure? Like, you checked the exit code? I suspect rcedit.exe is not exactly a paragon of software design when it comes to error reporting |
|
I mean, tbh, I'd just use a local directory as my releases dir then |
Does it need to be able to see all the previous packages to generate the diffs (I am just using squirrel for the first time)? |
Or should I mirror to local, generate update, then mirror again? |
@JakeGinnivan It does, but you could just Robocopy the opposite way |
👍 cool. Will do that instead, I have a feeling it is a weird caspol issue or something. Thanks |
At the end of the day, remember that Squirrel is very dumb, it's literally just NuGet packages and a RELEASES text file that you can easily generate. It's very easy to generate your own custom build around it, there is no magic |
I'm experiencing the same problem, when using the atom/grunt-electron-installer. There's an issue created there: electron-archive/grunt-electron-installer#96 which might be related. |
I solved this by replacing the rcedit.exe with a fresh one from https://github.com/atom/node-rcedit/raw/master/bin/rcedit.exe |
Oh I see why, the version of rcedit I package doesn't support version #s > 255 |
@codesmithx provided the clue |
@paulcbetts where do you see that the rcedit package doesn't support versions > 255? Is there a link? |
Same error on shared folder with the version 1.7.5. |
Same with 1.7,5 with a network shared folder. |
I'm getting same error when trying to deploy over UNC path |
Got us past one error into the next one: > Failed to modify resources > Fatal error: Unable to set icon > at Squirrel.Update.Program Looks like Squirrel/Squirrel.Windows#488
Hi, I have the same problem but I release in a directory on my computer. 2018-12-05 12:01:09> Program: Building embedded zip file for Setup.exe Setup: D:\PMMPowertools_Release\Setup.exe, Zip: C:\Users\S0089146\AppData\Local\Temp\tmp2C59.tmp What I see is that the Setup.exe which is generated by squirrel has attribute Read Only. So it can't modify it. When I change it manually in the explorer and launch rcedit it works. But I don't have my zip in it.... |
I go back to the 1.7.7 and it works. Don't really know why... |
It's don't work again. I try 1.7.5, 1.7.7 and the lastest 1.9.0. Squirrel : System.AggregateException: Une ou plusieurs erreurs se sont produites. ---> System.Exception: Failed to modify resources, command invoked was:
Output was: |
I found the solution ! |
Merging this into #888 which is about upgrading rcedit, but I'm hesitant that this will resolve it completely due to the various disparate discussion... |
replace place form ? |
I'm having problems running the releasify command in a powershell script, triggered by Octopus Deploy release management tool. I get the following error:
If I run the obove mentioned rcedit command, it works (I think - no error). I see that this issue have been raised before in #204.
Running Squirrel.Windows 1.2.1. The command looks like this;
Any hints?
The text was updated successfully, but these errors were encountered: