-
-
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
grep installs, but dependency file does not, so grep is not functional #2384
Comments
Please run |
Hi Richard, Thanks for the quick response. Didn't even think of trying that, since I just install scoop 2 days ago. I did check for bugs around this area, before reporting, but my search was too narrow. I'm guessing that this was a symptom of the robocopy file handling issue. Did the: scoop upgrade; scoop uninstall grep; scoop install grep However, along the way I ran into one that was already reported, and marked as closed: #1935: So, it claimed a successful update, but then threw an error/warning. For those of us who generally stick with cmd, Thanks again, |
@r15ch13 is there a way to turn on debugging to determine what’s causing the
errors? That single “ char is very suspicious. |
Unfortunately, I couldn't figure out what causes this error. AppVeyor drove me crazy the day I worked on my project. |
No. It does not happen now. This could have to do with a configuration issue stemming from the original install (although I believe I followed the install instructions precisely). These were some additional symptoms / observations:
So potential root cause path is new install in powershell, followed by some activity installing apps in cmd, followed by scoop upgrade in cmd. Seems to be a one-time spurious warning, as all seems to be working. ~paul |
As per this comment, as for workaround, installing the package via PS removed
Related: |
Thanks @kenorb. The error with the inability to find/run 'itcode' has now disappeared from my system. In my case it was a transient error between an install of an early July version, and an upgrade shortly thereafter. I think this issue can be closed out, as the original problem had an identified root cause that was a bug corrected by the changes on 10 July. |
The problem is still there using the latest version of Here is the demo build.
|
I my case I had run the original install in powershell (in Windows 10). I'm OK with this issue being re-titled to focus on the 'itcode' aspect of the problem, rather than the 'grep/multi-package' aspect. Or a new issue can be created. I was just trying to make sure the maintainers weren't caught with trying to solve two different problems under one issue. |
I just encountered the same issue. I ran
I scouted around the codebase trying to figure out how on earth this might happen. My theory is that an 'exitcode' string is being chopped up somehow. The most suspicious piece of code I could find is: https://github.com/lukesampson/scoop/blob/a9fa775d59b14e7dce335313faa0eff855469764/lib/core.ps1#L602 I have no clue what this is doing precisely, but with all the string substitution it looks like the most obvious candidate. Anyone have an idea of how to investigate this further? |
getting the same: when running scoop update from a cmd and not from powershell it does update all fine btw |
installing grep causes a download of both: grep-2.5.4-bin.zip and grep-2.5.4-dep.zip.
But it only extracts the bin.zip, and doesn't extract the dep.zip
Because of this, when trying to run grep, there are pop-ups alerting to error with missing pcre3 and regex2.
Unzipping the .dll files from the dep.zip file to the grep/2.5.4/bin directory in the scoop tree provides a work-around/local solution.
~paul
The text was updated successfully, but these errors were encountered: