| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
It's hugely inefficient as we can't use shallow cloning (--depth=1).
This has been tested and adapted for quite a few hosts fetchgit is used on in
Nixpkgs. For those where fetching the hash directly doesn't work (most notably
git.savannah.gnu.org), we simply fall back to the old method.
|
| |
|
|
| |
Fixes: 74128561 ("fetchgit: add lfs support")
|
| |\
| |
| | |
fetchgit: escape dot in regex
|
| | |
| |
| |
| | |
This regex should match files ending in `.git`, not any character and `git` after that.
|
| |\ \
| | |
| | | |
fetchgit: support passing tree hashes as "rev"
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason for this change is simply to avoid the following messages
that are unnecessary and can be confusing (and these messages will be
repeated for each submodule):
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
With this change the behaviour remains unchanged (apart from the
suppressed "warning" in the console output of course) and therefore this
doesn't cause any hashes to change and by default nix-prefetch-git uses
the "fetchgit" branch anyway (branchName can be set to override the
default):
Switched to a new branch 'fetchgit'
For that reason the initial branch name doesn't matter anyway and since
we're not relying on / hardcoding "master" we could simply switch to
"main" (which seems most common nowadays). See [0] for more details on
why this wouldn't break anything.
However, since the initial branch name doesn't matter and to avoid any
additional risks it was "decided" to keep using "master" (s. #113313).
[0]: https://github.com/NixOS/nixpkgs/pull/113313#issuecomment-780589516
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
whitespace"
|
| |\
| |
| | |
fetchzip, fetchgit: cleanup handling of optional features and whitespace
|
| | |
| |
| |
| |
| | |
No intended functional difference, just trying to polish to make this easier to
extend and more aligned with other nix conventions.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
`git repack` and `git gc` sometimes print “Nothing new to pack.”
to stdout, which breaks redirecting output to JSON file.
Let’s move the stdout of all git calls where it is not used to stderr
so that we still receive the info but it does not pollute our output.
|
| |/
|
|
|
| |
Just like in https://github.com/NixOS/nixpkgs/commit/be30ba8e0eabbc2483122ddf9d5911484df3a578
we want `fetchgit (builtins.fromJSON (builtins.readFile ./src.json))` to work.
|
| |
|
|
|
| |
Listing the option and brief explanation.
Addresses: https://github.com/NixOS/nixpkgs/issues/74182
|
| |
|
|
|
|
| |
Since Nix 2.0 we have `builtins.fetchGit` which is a much better
option since it runs in the evaluator and has access to the regular
users ssh keys.
|
| | |
|
| | |
|
| |\
| |
| | |
nix-prefetch-git: propagate errors under --quiet
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
Especially as a new user it is a much better experience to receive a
proper help response to `-h`. Currently passing `-h` will cause some
runtime error with the `git remote` error help being shown. Not very
helpful.
It doesn't hurt to be a bit more user friendly in this case.
|
| |
|
|
|
|
| |
This is useful when running tools like NixOps or nix-review
on workstations where the upload to the builder is significantly
slower then downloading the source on the builder itself.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The script would parse the output of `git submodule status` but
didn't handle paths with spaces in them. This would result in the
following error when trying to determine the URL of the submodule:
error: key does not contain a section: .url
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
According to git-submodule manpage,
"git submodule status" prefixes the hash with a '-' if it is not
initialized, and other chars in other circumstances.
(this is consistent on the various git versions tested)
nix-prefetch-git runs "git submodule init" which does you'd think,
but apparently despite this earlier versions of git before 2.16
would still give the hash the '-' suffix.
In particular this is the behavior when using 2.15 and 2.14.1
from the nixos-17.09 and nixos-17.03 channels respectively.
The script then used awk to drop the first char of the first field
which does the wrong thing when there is no prefix emitted:
while there is a space character before the hash, this is not
part of the field and so we ended up eating the first character
of the hash.
To fix this in a way that also works with the previous behavior,
this commit instead uses awk to grab the hash field
and uses tr to delete any '-' chars should they be present.
This seems to work in my testing, and for example can now
successfully fetch the source for "nginxModules.brotli"
where previously it would generate an error:
fatal: '22564a95d9ab58865a096b8d9f7324ea5f2e03e' is not a commit and a branch 'fetchgit' cannot be created from it
(we dropped a '2' from the beginning of the hash)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Currently we wrap ssh so it can find the config file passed in by
<ssh-config-file>. If one however uses ProxyCommand ssh, then ssh that
is on PATH is taken (which is also unavailable when using nix-shell
--pure), which is the plain ${openssh}/bin/ssh.
This commit makes sure our wrapped ssh is available on PATH.
|
| |
|
|
|
|
| |
This makes them produce the same store paths as builtins.fetchgit,
builtins.fetchTarball etc. See
https://github.com/NixOS/nix/commit/65b5f177b5fbb1b0778ede047a13a3cee9c59cfe.
|
| |
|
| |
s/understand/understood/
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
They're additional commits from #26877.
Changing names of the fetched stuff was changing very many hashes,
and I think it's better to avoid that for the moment to reduce work
needed by nixpkgs users. The fetchers are expected to be commonly
used even outside nixpkgs, and the current naming wasn't that bad
usually.
(commit analogical to d10c3cc5eedf58e80e2; I haven't noticed the part of
the PR has already got to master)
|
| | | |
|
| | |
| |
| |
| | |
"${repo}-${rev}-scr" to avoid mass rebuild
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
Update the code that extracts the base name from a git repo URL so that
it can deal with URLs like "git@server:repo".
|
| | |
|
| |
|
|
| |
fixes #4491
|
| |
|
|
| |
improve hash mismatch error message.
|
| |
|
|
|
| |
in some cases `git show` include tag information in the output
this is suppressed by the parameter '-1'
|
| |
|
|
| |
json requires certain characters to be escaped in strings.
|
| |
|
|
|
|
|
|
| |
Deprecation warnings should not be used in Nixpkgs because they spam
innocent "nix-env -qa" users with (in this case) dozens of messages
that they can't do anything about.
This also reverts commit 2ca883338389b7ab995924a0cab0211993bdf1da.
|
| |
|
|
|
|
|
|
| |
This commit extends fetchFromGitHub with ability to fetch GitHub
repositories with submodules, so we can use the function consistently
with all GitHub repositories.
Note it doesn't change the previous behavior.
|
| | |
|
| |
|
|
| |
Apparently everyone just copied those variables, instead of creating a
library constant for them. Some even removed the comment. -.-
|