Is bcupkgs a fork of Nixpkgs? If so then you probably want to override
Nixpkgs in your NIX_PATH by setting NIX_PATH=nixpkgs=~/local/bcupkgs.
On 9 Mar 2017 11:53 AM, "Sébastien Petitdemange" <
sebastien.petitdema...@esrf.fr> wrote:
Hi,
I've modify fetchgit module to add an optional argument to
Hi Profpatsch,
Here is the tree of my private package:
./local/bcupkgs/
├── default.nix
└── pkgs
├── build-support
│ └── fetchgit
│ ├── builder.sh
│ ├── default.nix
│ └── nix-prefetch-git
└── development
└── libraries
└── lima-core
On 17-03-09 04:31pm, Sébastien Petitdemange wrote:
> Hi Profpatsch,
>
> Yes I'm in the folder where I changed fetchgit but it doesn't call my
> modification version.
> How can I make sure that my package (lima-core) call my modify version?
> Is there a way to do that?
I cannot tell you anything
Hi Profpatsch,
Yes I'm in the folder where I changed fetchgit but it doesn't call my
modification version.
How can I make sure that my package (lima-core) call my modify version?
Is there a way to do that?
SEB
On 03/09/2017 12:08 PM, Profpatsch wrote:
> If you’re in the folder of the nixpkgs
Hi Teo,
No, it's not a fork. It contain only few private package + fetchgit with
the modification.
SEB
On 03/09/2017 11:57 AM, Teo Klestrup wrote:
> Is bcupkgs a fork of Nixpkgs? If so then you probably want to override
> Nixpkgs in your NIX_PATH by setting NIX_PATH=nixpkgs=~/local/bcupkgs.
<>
On 17-03-09 11:52am, Sébastien Petitdemange wrote:
> Hi,
>
> I've modify fetchgit module to add an optional argument to filter
> submodule. And I would like to use this optional argument to build my
> local package. Unfortunately, nix-build still get fetchgit from the main
> channel instead of
Hi,
I've modify fetchgit module to add an optional argument to filter
submodule. And I would like to use this optional argument to build my
local package. Unfortunately, nix-build still get fetchgit from the main
channel instead of ~/local/bcupckgs:
-> nix-build --show-trace ~/local/bcupkgs
On Mon, Jan 13, 2014 at 01:40:55PM +0800, S??nke Hahn wrote:
I also tried out https-urls. The problem is that not all repos that I need
to access are public. So I have to provide some authentication. For ssh I
can just put keys in .ssh, but for https in this setting, I'm not sure if
it's even
Thomas Bereknyei wrote:
I'm not positive this is the problem, but take a look at another
example. No quotes around the url and different format.
src = fetchgit {
url = git://git.gnupg.org/libgcrypt.git;
rev = 99b18aa53;
sha256 =
On 01/13/2014 04:09 PM, Sönke Hahn wrote:
Omitting the username does not seem to work for bitbucket, though. Nixops
just hangs after initializing the git repo. I guess, github has 'git' set as
the default user.
Different providers have different URI schemes, example from nixpkgs:
src =
Vladimír Čunát wrote:
Maybe it's easy to add the support, I'll look again at it this evening
(I hope), if noone else solves it beforehand. The main problem is the
purity of ~/.ssh -- this directory just shouldn't be considered, as the
behavior inherently impure. Adding key/password to
Aristid Breitkreuz wrote:
A noteworthy workaround would be that you can just have a manual checkout
of your private repos and then do
src = ./path/to/repo;
Thanks. Yes, that's what we're doing right now. (And it's not even that
inconvenient, but I thought fetchgit could be better.)
Am
Yes, that helps, thanks! It's actually not github, we are using bitbucket
for internal repos, but bitbucket seems to have similar possibilities:
https://confluence.atlassian.com/display/BITBUCKET/OAuth+on+Bitbucket
I'm going to look into this tomorrow.
Cheers,
Sönke
aszlig wrote:
On Mon,
Previously I've had success accessing private git repos via ssh using:
1. a ssh:// URL. EG: ssh://g...@git.corp.ooyala.com/qa/tools/jenkins-ci.git
2. Patching fetchgit to pass the GIT_SSH env variable and configuring
GIT_SSH to propagate the keys as expected.
Part #2 is much like Azlig
Hi,
I am trying to use fetchgit to package code that is available in git-repos.
I am using for example this expression:
pkgs.fetchgit {
url = g...@github.com:jekor/haskell-sscgi.git;
rev = 1547156d7199bdf40a837040a905d9b6b771dd26;
}
This does not work, the error message being:
error:
I'm not positive this is the problem, but take a look at another
example. No quotes around the url and different format.
src = fetchgit {
url = git://git.gnupg.org/libgcrypt.git;
rev = 99b18aa53;
sha256 = 1rhbpxqrkfszlv8jvw8s4apwklal07k8zxv5q555l7binc1j1j3z;
};
On Mon, Jan
Hi.
On 01/13/2014 07:52 AM, Thomas Bereknyei wrote:
I'm not positive this is the problem, but take a look at another
example. No quotes around the url and different format.
src = fetchgit {
url = git://git.gnupg.org/libgcrypt.git;
rev = 99b18aa53;
sha256 =
A noteworthy workaround would be that you can just have a manual checkout
of your private repos and then do
src = ./path/to/repo;
Am 13.01.2014 08:49 schrieb Vladimír Čunát vcu...@gmail.com:
Hi.
On 01/13/2014 07:52 AM, Thomas Bereknyei wrote:
I'm not positive this is the problem, but take a
Hi,
On 19/11/12 07:11, Marc Weber wrote:
Isn't it enough to depend on the git's hash value,
No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256
hash of the expected contents.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:01:39 +0100 2012:
No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256
hash of the expected contents.
I know what the current implementation requires. Just wondering whether
this should be relaxed for git (like) VCS
Hi,
On 19/11/12 11:25, Marc Weber wrote:
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:01:39 +0100 2012:
No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256
hash of the expected contents.
I know what the current implementation requires. Just wondering
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012:
No. fetchgit won't work if it's not a fixed-output derivation, because it
won't necessarily have network access (it might run in a chroot).
Again: I'm not talking about the current state. I'm aware about how it
works.
I'm
- Original message -
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012:
No. fetchgit won't work if it's not a fixed-output derivation,
because it won't necessarily have network access (it might run in a
chroot).
Again: I'm not talking about the current
Is it terribly difficult to run nix-prefetch-git? Built-in vcs-specific support
doesn't strike me as simplification.
On Nov 19, 2012, at 7:10 AM, Joachim Schiele j...@lastlog.de wrote:
- Original message -
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012:
Could fetchgit handle that on its own though?
Also, at least for github, if you want to install a specific tag, which
isn't always the case, you can link to the .zip copy of it from the
github page.
/M
Shea Levy s...@shealevy.com writes:
Is it terribly difficult to run nix-prefetch-git?
Excerpts from Shea Levy's message of Mon Nov 19 13:38:37 +0100 2012:
Is it terribly difficult to run nix-prefetch-git?
YES: I'm talking about such configurations:
http://gembundler.com/
And here you have git repo and hash. Trying to semi automatically
package such things requires much overhead
Marc Weber marco-owe...@gmx.de writes:
Excerpts from Shea Levy's message of Mon Nov 19 13:38:37 +0100 2012:
Is it terribly difficult to run nix-prefetch-git?
YES: I'm talking about such configurations:
http://gembundler.com/
And here you have git repo and hash. Trying to semi automatically
A similar solution for rubygems would probably not be too hard.
As rubygems itself is written in ruby, you can probably plug in to its
dependency resolution and downloading capabilities so you can focus on
generating the sha256 and the nix expression.
If you still haven't got it: I worte
Excerpts from Eelco Dolstra's message of Mon Nov 19 16:31:26 +0100 2012:
Why would you need a double fetch? After running fetchgit, the Git tree is
in
the Nix store and shouldn't be downloaded again unless you do a garbage
collect
in between.
You're right about this.
I want to make bundler
Of course running nix-prefetch-git is an option, however checking
whether a store path representing { url = ..; hash = .. } already exists
is harder. If you run nix-prefetch-git twice it will fetch twice
(waste). I haven't looked for options.
nix-store --check-validity $(nix-store -q --outputs
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even using shallow clones) that much
easier than compromising a .tar.* file protected by sha256?
In anyway you have to find a hash collision.
A lot of foreign tools
On Sun, Nov 18, 2012 at 10:11 PM, Marc Weber marco-owe...@gmx.de wrote:
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even using shallow clones) that much
easier than compromising a .tar.* file protected by
On Sun, Nov 18, 2012 at 10:24 PM, Nicolas Pierron
nicolas.b.pier...@gmail.com wrote:
On Sun, Nov 18, 2012 at 10:11 PM, Marc Weber marco-owe...@gmx.de wrote:
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even
I messed up Subject and Cc m( Now, with Marc's permission publicly.
My original mail:
Hi Marc,
there are currently several expressions pointing to your server
resulting in 404s.
Why do you prefer to put sources on your private server instead of
public infrastructure?
Maybe we can
34 matches
Mail list logo
