When trying to install the gem "u2f" from the repo at "castle/ruby-u2f" I get an error message:
Fetching git://github.com/castle/ruby-u2f.git
fatal: Needed a single revision
Revision master does not exist in the repository git://github.com/castle/ruby-u2f.git. Maybe you misspelled it?
I cannot find any information about this error message. The text does not appear in any of the bundler source files, so I don't even know where to start debugging.
If anyone has any insight into the source and cause of this error, I'd love to know.
If you're trying to install a gem from a github source and got this, it may be because the repo changed its default branch from "master" to "main". Try adding branch: 'main' and see if it works.
Try pulling from the master branch
I git pull a project to the local (on MacOS), and almost the same problem occurred during the bundle install. But I tried the above answers to no avail.
Related
I made a new repo and I'm fetching through SPM and XCode and I keep getting this message
"Error while fetching remote repositoryssh://git#someBitbucketurl.git: An unknown error occurred. reference 'refs/remotes/origin/dev' not found (-1)"
Did I mess up setting up the repo? I have to delete a bunch of stuff to get it to update properly.
I checked my git repo and I have a dev branch set as a default. I'm not sure what I should do to fix the dev branch.
Please help.
I'm getting the following error when trying to build. It shows up as the only item in the build log, too.
Here are the packages I'm using:
For me, it turned out that, even though Xcode was able to resolve and clone these packages, it didn't like that 2 of them pointed to the GitHub repo page, rather than the git file version.
Changing them so they're all .git URLs fixed it:
I'm trying to have Jenkins retrieve the submodules of a repository, but I cannot get it to work. I've looked around on the internet for a solution, but most problems there center around authentication, which is not the issue in this case. From what I've been able to gather from the error message, the issue seems to be related to the way the git-client plugin handles reponses from the command-line tools.
As we had Git for Windows version 2.6.0 installed and the Jenkins Git-client plugin 'officially' supports version 2.5.0, I also tried uninstalling version 2.6.0 and installed version 2.5.0, but that made no difference.
Does anyone here have any experience with this problem or a possible solution?
The error is:
FATAL: Command "c:\Program Files\Git\bin\git.exe submodule update" returned status code 1:
stdout:
stderr: Cloning into 'mysubmodule'...
error: cannot spawn echo : No such file or directory
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'http://somerepo': No error
Clone of 'http://somerepo/scm/bf/mysubmodule.git' into submodule path 'mysubmodule' failed
I have experienced the very same error, with same version of Git and Jenkins Git-client plugin.
It appears that this could be a combination of a bug and a misconfiguration of the submodule(s) in the .gitmodules file of the main repository. And the error message is definitely not as helpful as it could be!
In my case the .gitmodules file in the main repository contained the absolute url path to the submodule. This caused Jenkins to not be able to authenticate properly for the submodule. Changing the submodule path to be relative (../mysub.git) fixed it for me.
This helped me quite a lot:
https://issues.jenkins-ci.org/browse/JENKINS-31244
I hope you find this helpful.
I cloned the trunk branch from my fork of Ruby on GitHub and I am following the directions in the README to build ruby-trunk. Step #2 in the How to compile and install is
If ./configure does not exist or is older than configure.in, run
autoconf to (re)generate configure.
The configure file wasn't there in the repo so I ran autoconf. When I execute the generated configure file, I get an error
build git:(trunk) ../configure
config.guess already exists
config.sub already exists
configure: error: cannot run /bin/bash ../tool/config.sub
I use zsh so I thought that may have something to do with the problem. So I did a clean clone of the repo again and followed the same directions using bash but I still got the same error.
I did google this and all replies to this error said that I have to have ruby already installed to build ruby. But I already have several rubies installed on my system and I'm still getting this error each time. I use rbenv to manage the ruby versions.
Has anyone else faced this problem or does anyone else have any suggestions about what I can do to resolve this?
After pulling from main master, encountering a conflict and resolving conflict.
I'm working in a sub-folder of the main project repo (on automated tests) and so generally don't have to worry about conflicts. It seems however that every time a conflict is encountered and fixed, where I attempt to commit the pulled files RubyMine gives me this error message and won't allow anything to be done to resolve. I've previously taken a new fork from the GitHub main and manually merged in my own lost commits but it's happened again.
I can't find any reference to this dialog on searching the web and our TA has investigated the issue, concluding that it may be a RubyMine bug. I'm continuing my search for relevant info but aside from poring through the bugs in http://youtrack.jetbrains.com/issues/RUBY (which I have now done with no relevant issues found) I can't see where any leads might come from.
Latest version of RM (6.0.3) running on Macbook Pro (Mavericks)
RubyMine was used to resolve the conflicts; git status shows only the pulled files I'm now trying to commit as tracked and uncommitted - I have untracked files managed in a gitignore file
The dialog says:
Commit
Commit failed with errors
With error message displayed in terminal:
Error: Error executing git commit --only -F
[list of files I attempted to commit]
Try like this
Goto Tools -> Open terminal
Use this command
git status
Then add untracked files
git add .
Commit changes like this
git commit -i * -m "commit message"
If you still have errors please post the error. You can see the Version control logs at the bottom of rubymine
Are you using Rubymine to resolve the conflicts? If not, it's possible RubyMine has kept stale state of the filesystem and is reporting the errors because of this.
What does git status . tell you in your working directory? Is your current tree clean, or do you have unmerged changes?