When I run these steps:
mkdir dev
cd dev
git clone git://github.com/facebook/hhvm.git
cd hhvm
git submodule init
export CMAKE_PREFIX_PATH=`pwd`/..
export HPHP_HOME=`pwd`
cd ..
url: https://github.com/facebook/hhvm/wiki/Building-and-installing-HHVM-on-Ubuntu-12.04
I get stuck at the git submodule init I get the error: Submodule 'hphp/submodules/folly' () registered for path 'hphp/submodules/folly'
I have no clue what it means and it doesn't look like a fatal error...
UPDATE:
git submodule sync does sync php/submodules/folly but still the same error...
I would try:
git submodule update --init --recursive
And make sure that "Submodule 'xxx' registered for path 'yyy'" is indeed an error message: it looks like a standard answer for a git submodule init command.
From the git submodule book page:
The rack directory is there, but empty.
You must run two commands:
git submodule init to initialize your local configuration file, and
git submodule update to fetch all the data from that project and check out the appropriate commit listed in your superproject:
$ git submodule init
Submodule 'rack' (git://github.com/chneukirchen/rack.git) registered for path 'rack'
$ git submodule update
Initialized empty Git repository in /opt/myproject/rack/.git/
remote: Counting objects: 3181, done.
remote: Compressing objects: 100% (1534/1534), done.
remote: Total 3181 (delta 1951), reused 2623 (delta 1603)
Receiving objects: 100% (3181/3181), 675.42 KiB | 173 KiB/s, done.
Resolving deltas: 100% (1951/1951), done.
Submodule path 'rack': checked out '08d709f78b8c5b0fbeb7821e37fa53e69afcf433'
I prefer running only one command:
git submodule update --init
Related
I got this error when deploying a project on vercel. I have 4 other projects hosted on vercel and never had this issue before:
warning Pattern ["ethereumjs-abi#git+https://github.com/ethereumjs/ethereumjs-abi.git"]
is trying to unpack in the same destination
"/vercel/.cache/yarn/v6/npm-ethereumjs-abi-0.6.8-ee3994657fa7a427238e6ba92a84d0b529bbcde0/node_modules/ethereumjs-abi"
as pattern ["ethereumjs-abi#^0.6.8"]. This could result in non-deterministic behavior, skipping.
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads ssh://git#github.com/ethereumjs/ethereumjs-abi.git
Directory: /vercel/path0
Output:
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: Command "yarn install" exited with 128
deleted the package-lock.json and tried it
I made sure dev dependencies are correctly separated from dependencies.
BUt still same error. I could successfully build with
npm run build
yarn build
locally.
What worked for me was deleting my git repository using:
rm -fr .git
and initializing a new repository in the same directory but this time I didn't use npm , instead used yarn. So make sure to delete package-lock.json and node modules and then run :
yarn
In your package.json you will have this dependency:
"ethereumjs-abi": "github:ethereumjs/ethereumjs-abi"
This kind of reference defaults to access github over ssh, but github have deprecated this mode of access. Instead you should use https like this:
"ethereumjs-abi": "https://github.com/ethereumjs/ethereumjs-abi"
Getting this error:
Executing: git reset --soft HEAD~ && git restore --staged yarn.lock && git restore yarn.lock && yarn install && git add yarn.lock && git rebase --continue
yarn install v1.22.19
[1/5] π Validating package.json...
[2/5] π Resolving packages...
[3/5] π Fetching packages...
[4/5] π Linking dependencies...
[5/5] π¨ Building fresh packages...
success Saved lockfile.
β¨ Done in 10.29s.
error: could not open '/Users/devinrhode2/repos/myco/tess1/.git/worktrees/tess3/rebase-merge/author-script' for reading: No such file or directory
error: you have staged changes in your working tree
If these changes are meant to be squashed into the previous commit, run:
git commit --amend
If they are meant to go into a new commit, run:
git commit
In both cases, once you're done, continue with:
git rebase --continue
error: could not commit staged changes.
error: cannot rebase: Your index contains uncommitted changes.
warning: execution failed: git reset --soft HEAD~ && git restore --staged yarn.lock && git restore yarn.lock && yarn install && git add yarn.lock && git rebase --continue
and made changes to the index and/or the working tree
You can fix the problem, and then run
git rebase --continue
hint: Could not execute the todo command
hint:
hint: exec git reset --soft HEAD~ && git restore --staged yarn.lock && git restore yarn.lock && yarn install && git add yarn.lock && git rebase --continue
hint:
hint: It has been rescheduled; To edit the command before continuing, please
hint: edit the todo list first:
hint:
hint: git rebase --edit-todo
hint: git rebase --continue
The spirit of what I'm trying to do, is essentially re-generate the changes to yarn.lock file from the previous commit (but on the new base). It's easier to simply re-generate the changes than to validate them.
It seems you simply still need to commit the changed yarn.lock file. You do a git add command, which stages the file, but does not actually commit the result. Therefore at the point where you are trying to continue the rebase, your git working tree is still dirty, so git refuses to continue the rebase.
As git already indicates itself, you should add a git commit or git commit --amend command
#Johan
It's looking like this rebase recipe may look something like:
pick 6a33e8ebe Run `yarn add eslint --dev`
exec LAST_MSG=$(git log -1 --format=%B 6a33e8ebe); git reset --soft HEAD~ && git restore --staged yarn.lock && git restore yarn.lock && yarn install && git add yarn.lock && git commit -m "$LAST_MSG"
Of course, there's the complication of actually getting that hash in there for the LAST_MSG - should be able to reference just HEAD tho, I think.
UPDATE:
Actually, ideal pattern is for commands to have their own single commit, and do:
drop bde6f678a Run `yarn prettier --write README.md .eslintrc.js`
exec yarn prettier --write README.md .eslintrc.js && git commit -am "Run `yarn prettier --write README.md .eslintrc.js`"
Git should probably introduce a commit message syntax like:
git commit -am "exec! yarn prettier --write README.md .eslintrc.js"
When rebasing, it would basically expand to this:
drop bde6f678a Run `yarn prettier --write README.md .eslintrc.js`
exec yarn prettier --write README.md .eslintrc.js && git commit -am "exec! yarn prettier --write README.md .eslintrc.js"
Commits can never be small enough!
I'm trying to clone a git repo from my corp locally-hosted TFS/devops. However, I get failure:
batch response: Post (...) HTTP_1_1_REQUIRED
I saw recommendation to skip smudge by running git lfs install --skip-smudge
or setting GIT_LFS_SKIP_SMUDGE=1, but then the lfs-provided binaries don't get pulled and I get compile errors.
Solution - Before clone, run: git config --global --replace-all http.version HTTP/1.1
Ref, from the git-lfs developer which added the http.version option: https://github.com/git-lfs/git-lfs/issues/3875#issuecomment-607260728
My question is raised because my build-yocto server ran into the error:
ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository '/mnt/wd2tb/home/Work/skrzg1h_iWg21m_QtHmi/build/downloads/git2/github.com.qtproject.qtenginio.git'...
Fetcher failure for URL: 'git://github.com/qtproject/qtenginio.git;name=qtenginio;branch=5.6;protocol=git'. Unable to fetch URL from any source.
In the meantime, my PC can do that. So, I cloned the qtenginio repo to my local PC.
$ git clone git://github.com/qtproject/qtenginio.git;name=qtenginio;branch=5.6;protocol=git
And copy the downloaded source code above into the downloads/git2/github.com.qtproject.qtenginio.git folder of Yocto project.
Finally, I run the bitbake command.
$ bitbake qtenginio
But the fetch still fails.
Anyone can help me in this case ?
bitbake clones bare git repo, please add option '--bare' and touch a .done file to tell bitbake that do_fetch has been done already:
$ git clone --bare git://github.com/qtproject/qtenginio.git;name=qtenginio;branch=5.6 /mnt/wd2tb/home/Work/skrzg1h_iWg21m_QtHmi/build/downloads/git2/github.com.qtproject.qtenginio.git
$ touch /mnt/wd2tb/home/Work/skrzg1h_iWg21m_QtHmi/build/downloads/git2/github.com.qtproject.qtenginio.git.done
Step 1: download the package by hand (wget, git clone ...)
Step 2: copy the package into ./build/downloads
Step 3: touch a package_name.done file.
Step 4: change permission for the *.done file: chmod 777 package_name.done
I am currently using the Windows Github GUI and its pretty cool looking and easy so I'm trying to use it as often. A problem I encountered is when I fork a project I don't know how to update that fork with the git
And just for reference I copy here the detailed instructions from a post at http://processwire.com/talk/topic/1565-github-for-windows/:
In "GitHub for Windows" local repositories view, right-click and choose "open a shell here"
This will open a shell already in the right directory. Type the following commands:
# Assigns the original repo to a remote called "upstream"
git remote add upstream https://github.com/path_to_your_repository.git
# Pulls in changes from the original repo not present in your local repository,
# without modifying your files.
# Allows you to review first.
git fetch upstream
# merge fetched changes into your working files.
git merge upstream/master
GitHub for Windows only supports one remote for now (origin, which reference your fork).
So you need to manually add a remote (called 'upstream') referencing the original repo, in order for you to be able to pull (from the CLI) from upstream, updating your local repo and allowing you to push (this time with the GUI) the new commits to your fork.
See "What is the difference between origin and upstream in github" for more.
Syncing a fork
Sync a fork of a repository to keep it up-to-date with the upstream
repository.
Tip: Before you can sync your fork with an upstream repository, you
must configure a remote that points to the upstream repository in Git.
1. Open Terminal (for Mac users) or the command prompt (for Windows and Linux users).
2. Change the current working directory to your local project.
3. Fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local
branch, upstream/master.
$ git fetch upstream
4. Check out your fork's local master branch.
$ git checkout master
5. Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync
with the upstream repository, without losing your local changes.
$ git merge upstream/master
If your local branch didn't have any unique commits, Git will instead
perform a "fast-forward":
$ git merge upstream/master
Tip: Syncing your fork only updates your local copy of the repository.
To update your fork on GitHub, you must push your changes.
Source: https://help.github.com/articles/syncing-a-fork/
In Github for Windows (GUI application), press button Sync, then application will upload changed files to your own repository (at Github.com).
How to sync a fork repository from an original repository?
For easy understand, I call an reality example: Sync this repository: https://github.com/donhuvy/scrapy from https://github.com/scrapy/scrapy
Thereβre all steps:
Last login: Fri Sep 2 08:45:34 on ttys000
Dos-MacBook-Pro:~ donhuvy$
Dos-MacBook-Pro:~ donhuvy$
Dos-MacBook-Pro:~ donhuvy$ ls
AndroidStudioProjects IdeaProjects Public
Applications Library PycharmProjects
Desktop Movies example.dump
Documents Music pgadmin.log
Downloads Pictures sun-appserv-samples
Dos-MacBook-Pro:~ donhuvy$ cd Documents/
Dos-MacBook-Pro:Documents donhuvy$ ls
$RECYCLE.BIN
13256069_130212657393823_216708148326317354_n.jpg
1511456_1453604554870601_599093550_n.jpg
4578-rc007-jquery_online.pdf
Apps
Programming ebooks
Setup
Treasure_Island_NT.pdf
Video tutorial
Virtual Machines.localized
films
postgresql-9.0-A4.pdf
program_files
source_code
vy.sql
workspace_javaee
Dos-MacBook-Pro:Documents donhuvy$ cd source_code/
Dos-MacBook-Pro:source_code donhuvy$ ls
github.com
Dos-MacBook-Pro:source_code donhuvy$ cd github.com/
Dos-MacBook-Pro:github.com donhuvy$ ls
AurelioDeRosa donhuvy hibernate-orm scrapy spring-projects
Dos-MacBook-Pro:github.com donhuvy$ cd donhuvy/
Dos-MacBook-Pro:donhuvy donhuvy$ ls
ZohoCRM_integration jquery3_examples
java_examples real_estate
Dos-MacBook-Pro:donhuvy donhuvy$ git clone https://github.com/donhuvy/scrapy.git
Cloning into 'scrapy'...
remote: Counting objects: 40481, done.
remote: Total 40481 (delta 0), reused 0 (delta 0), pack-reused 40481
Receiving objects: 100% (40481/40481), 13.98 MiB | 746.00 KiB/s, done.
Resolving deltas: 100% (21135/21135), done.
Checking connectivity... done.
Dos-MacBook-Pro:donhuvy donhuvy$ '
>
>
>
Dos-MacBook-Pro:donhuvy donhuvy$
Dos-MacBook-Pro:donhuvy donhuvy$
Dos-MacBook-Pro:donhuvy donhuvy$ ls
ZohoCRM_integration jquery3_examples scrapy
java_examples real_estate
Dos-MacBook-Pro:donhuvy donhuvy$ cd sc
-bash: cd: sc: No such file or directory
Dos-MacBook-Pro:donhuvy donhuvy$ cd scrapy/
Dos-MacBook-Pro:scrapy donhuvy$ ls
AUTHORS README.rst requirements.txt
CODE_OF_CONDUCT.md artwork scrapy
CONTRIBUTING.md conftest.py sep
INSTALL debian setup.cfg
LICENSE docs setup.py
MANIFEST.in extras tests
Makefile.buildbot pytest.ini tox.ini
NEWS requirements-py3.txt
Dos-MacBook-Pro:scrapy donhuvy$ git log
commit ab42e2b5d531cbbf2ee46b49726604c90becbd3d
Author: vydn <v#vyhn.net>
Date: Sat Apr 2 06:08:28 2016 +0700
Change the content
Change the content
commit bf7f67549378269c3976afc89abcf9c2190d242f
Merge: 9d8c368 9250a5b
Author: Paul Tremberth <paul.tremberth#gmail.com>
Date: Fri Apr 1 15:47:06 2016 +0200
Merge pull request #1847 from aron-bordin/add_blocking_storage_path_setting
[MRG+2] added BLOCKING_FEED_STORAGE_PATH to settings
commit 9250a5bffa91c24dbea5c5d64c3c7cd9992a6ee7
Author: Aron Bordin <aron.bordin#gmail.com>
Date: Sat Mar 5 19:36:02 2016 -0300
added FEED_TEMPDIR to settings
commit 9d8c368ce8a24d7adb63b731df1359f3b05f3bdd
Dos-MacBook-Pro:scrapy donhuvy$
Dos-MacBook-Pro:scrapy donhuvy$
Dos-MacBook-Pro:scrapy donhuvy$ git fetch upstream
fatal: 'upstream' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Dos-MacBook-Pro:scrapy donhuvy$ git remote -v
origin https://github.com/donhuvy/scrapy.git (fetch)
origin https://github.com/donhuvy/scrapy.git (push)
Dos-MacBook-Pro:scrapy donhuvy$ git remote add upstream https://github.com/scrapy/scrapy.git
Dos-MacBook-Pro:scrapy donhuvy$ git remote -v
origin https://github.com/donhuvy/scrapy.git (fetch)
origin https://github.com/donhuvy/scrapy.git (push)
upstream https://github.com/scrapy/scrapy.git (fetch)
upstream https://github.com/scrapy/scrapy.git (push)
Dos-MacBook-Pro:scrapy donhuvy$ git fetch upstream
remote: Counting objects: 1329, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 1329 (delta 600), reused 599 (delta 599), pack-reused 723
Receiving objects: 100% (1329/1329), 425.28 KiB | 325.00 KiB/s, done.
Resolving deltas: 100% (920/920), completed with 141 local objects.
From https://github.com/scrapy/scrapy
* [new branch] 0.12 -> upstream/0.12
* [new branch] 0.14 -> upstream/0.14
* [new branch] 0.16 -> upstream/0.16
* [new branch] 0.18 -> upstream/0.18
* [new branch] 0.20 -> upstream/0.20
* [new branch] 0.22 -> upstream/0.22
* [new branch] 0.24 -> upstream/0.24
* [new branch] 1.0 -> upstream/1.0
* [new branch] 1.1 -> upstream/1.1
* [new branch] asyncio -> upstream/asyncio
* [new branch] deprecate-make-requests-from-url -> upstream/deprecate-make-requests-from-url
* [new branch] disable-toplevel-2 -> upstream/disable-toplevel-2
* [new branch] doc-arch-overview2 -> upstream/doc-arch-overview2
* [new branch] feature-1371-download-prios -> upstream/feature-1371-download-prios
* [new branch] fix-1330 -> upstream/fix-1330
* [new branch] fix-util-function-to-work-outside-project-dir -> upstream/fix-util-function-to-work-outside-project-dir
* [new branch] link-encoding -> upstream/link-encoding
* [new branch] master -> upstream/master
* [new branch] no-max-rss -> upstream/no-max-rss
* [new branch] py3-chunked -> upstream/py3-chunked
* [new branch] release-notes-1.1.2-master -> upstream/release-notes-1.1.2-master
* [new branch] remove-prerelease-configuration -> upstream/remove-prerelease-configuration
* [new tag] 1.0.6 -> 1.0.6
* [new tag] 1.1.2 -> 1.1.2
* [new tag] 1.1.0 -> 1.1.0
* [new tag] 1.1.0rc4 -> 1.1.0rc4
* [new tag] 1.1.1 -> 1.1.1
Dos-MacBook-Pro:scrapy donhuvy$ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
Dos-MacBook-Pro:scrapy donhuvy$ git merge upstream/master
error: There was a problem with the editor 'vi'.
Not committing merge; use 'git commit' to complete the merge.
Dos-MacBook-Pro:scrapy donhuvy$ git commit -m "update"
[master 6f16b46] update
Dos-MacBook-Pro:scrapy donhuvy$ git push
Counting objects: 915, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (380/380), done.
Writing objects: 100% (915/915), 235.84 KiB | 0 bytes/s, done.
Total 915 (delta 677), reused 769 (delta 535)
remote: Resolving deltas: 100% (677/677), completed with 99 local objects.
To https://github.com/donhuvy/scrapy.git
ab42e2b..6f16b46 master -> master
Dos-MacBook-Pro:scrapy donhuvy$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
Dos-MacBook-Pro:scrapy donhuvy$
Important points:
Step 1. Change directory:
cd /Users/donhuvy/Documents/source_code/github.com/donhuvy/
To be sure:
pwd
Step 2. Go to https://github.com/donhuvy/scrapy look at the top right, copy repository link
https://github.com/donhuvy/scrapy.git
Step 3. Clone from server to local
git clone https://github.com/donhuvy/scrapy.git
Step 4. Go to https://github.com/scrapy/scrapy , look at the top right, copy repository link
https://github.com/scrapy/scrapy.git
Step 5. Add upstream repository link
git remote add upstream https://github.com/scrapy/scrapy.git
Step 6. Check repo list:
git remote -v
Result:
origin https://github.com/donhuvy/scrapy.git (fetch)
origin https://github.com/donhuvy/scrapy.git (push)
upstream https://github.com/scrapy/scrapy.git (fetch)
upstream https://github.com/scrapy/scrapy.git (push)
Step 7. Fetch upstream
git fetch upstream
Step 8. Get master branch from upstream repo
git checkout master
Step 9. Merge source code:
git merge upstream/master
Vim editor open inside terminal, then you edit commit message, press i for starting edit, press esc, :wq! for quit and save.
Step 10. Make a commit
git commit -m "update"
Step 11. Push
git push
Step 12. To be sure
git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
Of course, I try to my post have no 13rd step.
Reference:
https://help.github.com/articles/configuring-a-remote-for-a-fork/
https://help.github.com/articles/syncing-a-fork/