-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shouldn't we ratelimit the ISO builds somehow? A series of a few
NixPkgs commits spread over some time can launch a few NixOS ISO builds
at once. Is it considered a good idea?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
OTOH, as long as the garbage collector runs frequently enough (there were some
issues with that lately) it's not necessarily a big problem/
Heh, it's nice that buildfarm is powerful enough for that attitude.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courts wrote:
+maintainers = [
+ stdenv.lib.maintainers.raskin
+ stdenv.lib.maintainers.ludo
+];
Oh, am I the first one of NixPkgs contributors who gets to find out his
being in meta.maintainers of a package from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
On Thu, Jul 09, 2009 at 08:28:54AM +0400, Michael Raskin wrote:
Well, if someone puts up a redirect to a mirror choice instead of the
file - at the same URL... You do not want the tarball to begin with
html.
So what's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Oh, am I the first one of NixPkgs contributors who gets to find out his
being in meta.maintainers of a package from Nix-commits?
Eh eh. I took the freedom to add your name here, given that you had
been the actual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
Hi,
Michael Raskin wrote:
Log:
Fix service tree paths
...
-gw6cService = import ../../services/gw6c {
+gw6cService = import ../../../../services/gw6c {
Even better would be to move gw6c to the nixos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
+# This module allows you to export something from configuration
+# Use case: export kernel source expression for ease of configuring
Can you expand on this a bit? What is the use case?
I use custom patched (well, not so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
My main concern is whether we have some decent-looking fonts in a default
installation. Without the Core fonts we only have Bitstream Vera and the GNU
FreeFont (which may be enough - not sure). I personally don't have major
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This mscorefonts example exposes a very big issue that extends much
further than just mscorefonts. There is stuff like ffmpeg, gstreamer,
x264, freetype2 that shouldn't be made available by default but they
all have dependents which effect lots of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony White wrote:
I like the idea! On by default but option available to turn off if
undesired (Can't honestly see why that would be the case.) Testing it
might be fun. :)
Well, if someone puts up a redirect to a mirror choice instead of the
file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony White wrote:
Please do not mix these two issues too much. Filtering out proprietary
software should be one switch, and avoiding free software endangered by
possible legality of software patents in the US should be another
option. The reason
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I am about to commit an update to BtrFS progs. If there is anybody else
who is testing BtrFS in NixOS now, warning: BtrFS progs 0.19 create FS
requiring Linux 2.6.31-rc1. (If you know more specific details, you
already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
Thanks, I got you now. So at least before union mounting all those store
paths there should be a test checking for conflicts and a big fat
warning.
This is where the problem lies. I know that if I have managed to make
some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
_In depths description of the pygtk issue_:
The lib is imported by python in two phases:
import pygtk; pygtk.require 'version X'
The last command adds libPath/verisonX to its installation directiory.
The problem is that pygtk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
By using aufs you can be pretty sure that everything works as well if
you're using aufs again in your profile, correct?
No. Maybe executable name were different but library set has non-trivial
file name conflict..
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony White wrote:
Hi,
Does anyone have a method to use to generate a .config using
menuconfig? (The ncurses kernel config frontend.)
nix-build /etc/nixos/nixpkgs -A ncurses -o $HOME/ncurses
export NIX_CFLAGS_COMPILE=$NIX_CFLAGS_COMPILE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony White wrote:
Or do the .nix files have a syntax of which is slightly different to haskell?
If yes it's haskell syntax, I like syntax highlighting in editors. I
use it a lot with css, php, javascript and xhtml, etc in kwrite.
It makes spotting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathaniel Waisbrot (Cont ARL/CISD) wrote:
(That's not syntactically valid Nix.) Is it possible to do what I want
here? What's the correct way to do it?
Try to copy selectVersion approach
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Log:
Restoring builderDefs functionality in setuptools
I'm the one who changed the `setuptools' expression to `stdenv' a few
I noticed..
days ago when I updated it and fixed `easy_install'. I made this choice
I assumed
Eelco Dolstra wrote:
Add an ftruncate call paired with fallocate to play safe with some FSes
(namely, BtrFS fallocate sets file size to allocated size, i.e. multiple of
block size)
That seems like a fairly large bug in BtrFS...
(And should we have workarounds for bugs in pre-alpha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
I had a look at your patch and I don't understand why you are not
using the mkOverride function introduced to tackle your problem. I
think you may have some problems with your method.
Well, I am ready to reply why. I want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arie Middelkoop wrote:
We have to use the directy sleep hack, because it there is time window
between starting the dbus daemon process and when it is really active.
You could create a busy loop with dbus-send and keep on retrying until
it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I added gimp into release.nix. However, Hydra hasn't tried to build it
yet (queue is empty). Is Hydra down or is there any reason?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Log:
version bump to coreutils-7.1
This change was made in `stdenv-updates' some time ago. IIUC, such
changes should *not* be made in `trunk' as they cause essentially full
rebuilds (and/or re-downloads).
Yes. More
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
http://hydra.nixos.org/channel/latest
http://hydra.nixos.org/channel/all
http://hydra.nixos.org/project/nixpkgs/channel/latest
http://hydra.nixos.org/project/nixpkgs/channel/all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I see that nixpkgs/pkgs/top-level/release.nix defines jobs to build.
What is the policy w.r.t. that file? Is job count kept small as for now?
Are notation changes to simplify syntax considered bad or good (if
properly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I see that currently Hydra provides manifests etc. So it is very close
to be actually used. Unfortunately, URLs that Hydra gives for .nar.gzs
are somewhat strange: if I know a store path, I have to guess a build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
If you really want to start X from console manually you should have a
a look at xlaunch or use this script:
It extracts teh important information form the /etc/event.d/xserver file
and writes a launch script with the same setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Breuer wrote:
$ xlaunch
Using :0
egrep: /etc/event.d/xserver: No such file or directory
export _XARGS_=[snip]
/nix/store/[snip]-xorg-server-1.4.2/bin/X $_XARGS_
At that point xlaunch gets stuck and does not do anything anymore.
Hm.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Breuer wrote:
Now I would like to build a live DVD. Simply running
nix-build nixos/installer/cd-dvd/live-dvd-X.nix -A rescueCD
Looks right. I committed some fixes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Breuer wrote:
it looks like you've done the right things.
You really should tell us about the failures.
I just updated both the nixos and the nixpkgs trees. Then I tried
Checkout services/ too (to the same dir). Symlink nixos/services
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg F. Wittenberger wrote:
c) gnome-terminal dies, because it's called with a -ls argument, which
it does not understand.
Question: how do I find the call site?
When is it called in he first place?
That was my question. Meanwhile I found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg F. Wittenberger wrote:
The worst part seems to be: I can't find out, how to make those packages
available, which are already installed on the system. For instance, I
have /nix/store/paiq*-gnome-panel.2.2.1/ on my system, but when I try to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lluís Batlle wrote:
What should I do, if I want to roll back to an older system
generation? afaik, it's not only about changing the profiles/system
link to point to another generation, but there are also files in /etc
that should be rebuilt.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
Main modifications made in this branch:
- a few upstart-jobs conversion.
- upstart-jobs/default.nix, etc/default.nix are configuration files.
- extensible activation script.
- system parts can be build in multiple files.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
c) what about sshd so that you can watch installation progress from
another machine?
So do you mind me adding them to the list of extraPackages?
Is installer/cd-dvd/rescue-cd.nix the best file to do so?
There are a many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
Log:
* Generate manifests on demand. Next step: generate NAR archives on
demand, then we can have channel support and one-click installs in
Hydra.
Generating archives on demand looks too much like nix-http-export.. So I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
Log:
* Suspend when the laptop lid is closed.
That should be optional
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
The reason has been another: I think nix is a really great tool and at
least I'd like to think about beeing able using native windows tools
one day. That's why I don't want to have to support symlinks for such a
optional feature.
/apache) # symlink
(import pkgs_new/app-admin/apache) # real file
(import pkgs_new/daemons/apache) # symlinks
(import pkgs_new/servers/apache) ) # symlink
?
I've abused the syntax here.. But I think you get the point
Michael Raskin can you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Altobelli wrote:
For the past week I've been working on a branch of nixpkgs that moves
the packages into an file hierarchy modeled after the Gentoo portage
system (http://gentoo-portage.com/Browse). I have since completed the
reorganization
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courts wrote:
Mount `/dev/shm' (shared memory support).
mount -t tmpfs -o mode=0755 none /dev
+mkdir -m 0777 /dev/shm
+mount -t tmpfs -o rw,nosuid,nodev tmpfs /dev/shm
mkdir -m 0755 -p /dev/pts
mount -t devpts none /dev/pts
Why make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Mount `/dev/shm' (shared memory support).
mount -t tmpfs -o mode=0755 none /dev
+mkdir -m 0777 /dev/shm
+mount -t tmpfs -o rw,nosuid,nodev tmpfs /dev/shm
mkdir -m 0755 -p /dev/pts
mount -t devpts none /dev/pts
Why make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Altobelli wrote:
The problem is that if I enter the knownVideoDriver as radeonhd in
configuration.nix, it goes to the radeonhd version 1.2.1 which does
not have the xf86videoradeonhd_124 naming convention. I basically
changed the name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I currently have a problem with both 2.6.28 kernels on i686 I have
(personal config and NixPkgs default). If I run firefox (either 3.0.5 or
3.1 beta 2), or thunderbird nothing happens. If I boot 2.6.27 everything
is OK..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Simons wrote:
Maybe I'm just missing an obvious insight, but I don't understand how
the wrapper code found in the new Python expression improves that
situation, even if it's just for Python. Let's say I want to build
cheetahTemplate with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Valentin David wrote:
Would it be actually possible to have TeXLive 2008 instead of 2007?
The nix expression for it seems very complex. I am not sure I am
capable of updating it.
My expression relies on Debian having done one quite tedious part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Valentin David wrote:
Would it be actually possible to have TeXLive 2008 instead of 2007?
The nix expression for it seems very complex. I am not sure I am
capable of updating it.
My expression relies on Debian having done one quite tedious part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
On Fri, Jan 9, 2009 at 00:02, Michael Raskin 7c6f4...@mail.ru wrote:
Modified: nixpkgs/trunk/pkgs/lib/default.nix
===
--- nixpkgs/trunk/pkgs/lib/default.nix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
On Fri, Jan 9, 2009 at 01:23, Michael Raskin 7c6f4...@mail.ru wrote:
Added: nixos/trunk/upstart-jobs/guest-users.nix
===
--- nixos/trunk/upstart-jobs/guest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
There throw should not throw an exception in the C++ code but it
should just return a normal form.
throw foo: is a normal form
(throw foo) + bar : is not a normal form and it returns throw foo.
This remove the problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andres Loeh wrote:
Mainly because of the already mentioned trickyness that exceptions in
lazy languages tend to escape their surrounding try-block, try-catch
is generally considered not a very useful construct in the face of laziness.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
Hi,
Many people have reported that message are not very helpful and this
is really the case inside NixOS where everything is merged and you are
not able to figure out what is the problem. So I have made a patch
for nix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
In fact, I don't see much drawback.
So I vote for reducing functionality to force
rethinking implementation if a need arises.
What do you mean ?
I have made this because I need this trick to handle error messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Artyom Shalkhakov wrote:
- if there's a REPL for Nix? I'd like to debug network-interfaces.nix
Basic answer: no
There is nix-instantiate (and --eval-only flag to it), but it is not
always comfortable to use.
(I can connect to my home
wireless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ville Oikarinen wrote:
Hello.
First, thank you for a very inspiring bunch of ideas and implementations,
I really hope nix will work for me, to help fight against the constant
software rot around us. (Configuration file rot is another problem,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pjotr Prins wrote:
Two problems so far: you meant 0.12 and it is very risky to use stable.
I think that is misguiding. Rather than pointing towards SVN head we
Currently it is not.
ought to fix the stable branch when it fails. That is what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe we should reverse the situation?
Obviously, we should try to avoid building just what we need each time
and always ending up with a bunch of near-identical builds.
We can already have .passthru.function in any package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
real life. I'd vote for composableDerivation..
1. You are biased.
2. We would better define interface first, not the implementation.
libXDefaultOptsAndFun = {
fun = opts : stdenv.mkDerivation { ... };
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
I found a package that carries LICENCE file
The correct spelling is `license' with an `s' (maybe that package is
broken?).
1. License is American spelling. I would not say that American
spelling is correct and British is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courts wrote:
Add `host' to `systemPathList'.
pkgs.gnutar
pkgs.grub
pkgs.gzip
+pkgs.host
pkgs.iputils
pkgs.less
pkgs.lvm2
I don't think that is a good idea... host is a part of BIND distribution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
I'm not sure I've understood how this works:
So can I copy some dirs from /nix/store to my home directory,
modify them, change their hash to a hash which is very likely to be
installed by the system anyway later on (due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arie Middelkoop wrote:
Maybe I understand incorrectly, but how would a
NIX_OTHER_STORE be less secure than for example a channel you've
registered to?
That's the point I make.. It could turn out to be implemented insecurely
if a user running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Speaking of Bison, I fail to get any useful info as to what's failing on
the build farm (and, needless to say, it all works flawlessly on my i686
box). So yes, I'd be happy if someone could reproduce the problem. :-)
Get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
TU Delft Nix Buildfarm wrote:
This is the build job supervisor script at cartman.
I previously informed you that the build job `nixpkgsTrunk' had failed.
I'm now happy to inform you the problem has disappeared; this job now
Should I recreate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Anyway, it should certainly be improved to be detected at
`nixos-rebuild'-time, but I'm not sure how.
Maybe a good way would be for each package to define setuidPrograms it
would like to install, and then we could have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Dijk wrote:
[EMAIL PROTECTED] /etc/nixos/nixos # svn diff upstart-jobs/xserver.nix
Index: upstart-jobs/xserver.nix
===
--- upstart-jobs/xserver.nix (revision 13157)
+++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeevakan Suresh wrote:
So can I upgrade my nix (via nix) so that it handles these - or do I
have to rebuild from svn trunk?
I have some NixPkgs Nix as a fallback. It works.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
BTW, can someone explain to me what xorgReplacements is for? And why the
crazy
complexity of that function:
To have xserver job using non-default set of X.org packages.
{stdenv, fetchurl, xorg, automake, autoconf, libtool,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pjotr Prins wrote:
Ask him to make a hard link. You can also do away with the
pre-compiled packages. I find it is no problem and you can share
precompiled binaries with other systems as long as the path is the
same. BTW current server farm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeevakan Suresh wrote:
I just did an svn update, and when I try to install anything - I get the
following error.
error: while evaluating the function at
`/home/isdtc/jsuresh/.nix-defexpr/channels/channel/nixexpr/pkgs/lib/defa
ult.nix', line 42:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
Buildfarm status page displays the same lines from Gnash test failure
(I temporarily switched Gnash testsuite off for next build attempt to
succeed) for a very long time. Has buildfarm locked up?
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I got some luck, and now I have a second monitor where I work. The
problem is that I have an ATi card and use ati 6.9.0 driver (chipset
RC410). Does anybody have experience with 1) NixOS + ati + RC410 +
Xinerama, 2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
1. Buildfarm trunk build fails over and over again.
Ouch, sorry!
Well, I decided I need OpenOffice from buildfarm, so I commented out
gnash from build list, fell asleep, and uncommented it in the morning.
Let's assume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
I do feel sorry and I try hard to avoid such issues, but errare humanum
est.
I'd say that most of the time commit blindly - wait - maybe comment
out is an OK tactics (I also use it, especially for big packages that
failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arie Middelkoop wrote:
Currently, Nixpkgs contains a fair amount of non-free software, some of
which gets installed by default. I would personally like it if we would
gradually separate non-free software from free software in Nixpkgs, so
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I noticed the following:
1. Buildfarm trunk build fails over and over again.
2. The only two packages from build-for-release that fail are updated
Gnash packages.
3. The real build failure is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pjotr Prins wrote:
Ah, Michael pointed out it is the same kernel header problem. I am
trying to use binary downloads on an older kernel - writing a
tutorial for newbies.
How do we make this appetizing for Nix newbies? Can we have binaries
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
cp: preserving times for
`/nix/store/jfy9vwhnj79r7yh2k196n1wnv8jl6dy7-gcc-4.2.4/nix-support/utils.sh':
Function not implemented
2.6.18-5-xen-amd64 - mentioned in the end of original post
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
Can't we instead solve that by doing the job of `texLiveAggregationFun',
i.e., collecting things in a single directory, in each package's
`postInstall'? That is, `texlive-{core,beamer,extra}' would install
cls/sty files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
use. The only real solution would be per-process bind mounts, which would
cause
the bind mount to disappear automatically when the Nix process exits (and they
wouldn't be visible for other processes, so you wouldn't be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Are we ready to (optionally) do chattr +i on successful builds? That
would also help.. Because doing _anything_ with +i file is really hard.
It's a bit ext[234]-specific, right?
Only a bit. As in works on XFS, too (I have /nix/store on XFS, so I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pjotr Prins wrote:
Michael: a broken package is no reason to comment it out. Because of
late binding nothing will happen. I think the only acceptable
Unfortunately, it actually caused a few failures on buildfarm. Buildfarm
really checks that all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
Maybe we even can mark them as broken by adding a meta tag?
meta = {
broken = true;
}; ?
Then we could have a look at them periodically to see wether we want to
remove or fix them..
I think that applies only to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeevakan Suresh wrote:
Basically, the following command fails with a 'curl: (7) couldn't
connect to host' error
nix-env -if /path/to/pkgs git
Usually a trick is to have http_proxy set for nix-worker daemon process
or to build with NIX_REMOTE=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pjotr Prins wrote:
nix-store --verify
checking path existence
checking path meta-information
error: path `/nix/store/pbmf37alssdncil52kv29vlck19hnihh-coreutils-6.12' is
not valid
- the problem persists.
Try any build operation now.. Should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
* xulrunner-wrapper: use Firefox 3 directly (via firefox -app),
since it has full support for running XUL applications. This saves
a lot of space (you don't need two copies of basically the same
software).
Did you fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eelco Dolstra wrote:
Did you fix the problem with xpidl? Default firefox build seems to lack it.
I didn't fix anything... I did notice that xulrunner3 installs a lot of
programs that Firefox doesn't (67 programs under $out/bin in fact).
Well,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I decided that having 3 options *Support and option sqlite is too
confusing and renamed sqlite to sqliteSupport in python getConfig.
Please update your configuration if you were using python.sqlite option
(which is for
I'm running the nix-env (Nix) 0.12pre12474 and am trying to install vim
I really hope that exact Nix version is irrelevant..
- and it fails :(
Configure works fine, but make fails with
the following error.
touch: setting times of `src/auto/link.sed': Function not
implemented
Author: raskin
-{stdenv, fetchurl, perl, bison, mktemp, kernel}:
+{stdenv, fetchurl, perl, bison, mktemp, kernel
+ , version ? 1.5
+ , sha256 ? 1izhf8kscjymsvsvhcqw9awnmp94vwv70zdj09srg9bkpjj0n017
+ , subdir ?
+}:
I don't think this is a good idea, unless there is a very good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
| It's more about checking out.. Automatic rebuilding and switching to the
| updated configuration can be annoying that very day when you want to
| finish configuring something before massive rebuild.
| But it's the only way
The complete build log has been stored in
/home/buildfarm/buildfarm-state/jobs/nixpkgsTrunk/2008-08-06_20:46:52.log.bz2.
Is there a web page for it ?
Go http://buildfarm.st.ewi.tudelft.nl/status .
There is
You overestimate organizational level of nixpkgs maintenance.
Ideally, every update should be built and tested separately on all supported
platforms. Well, it doesn't happen - and no infrastructure is in place for
detailed testing.
Most version updates are done like nix-prefeth-url + build -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bárður Árantsson wrote:
| My problem is that I want to provide Ruby to biologists, and can not
| support all GEMs they will think of.
|
| I still think that a wrapper that is a combination of Ruby plus all the
| gems you need for a certain package
Hi, what about adding
environment {
nixManual = [ apache elinks firefox less ];
nixOsManual = [ apache elinks firefox less ];
}
apache should add http://localhost/nix/ or such
and elinks/ firefox should provide
nix-manual-elinks
nix-manual-firefox
nix-manual-less (html
Well, I looked at your message and understood the trouble.. You set glibclibdir
to lib64 and hope it will find /usr/lib/crt1.o . I fail to understand how it
worked for you.. Maybe emacs over glibc2.5 somehow uses other dependencies..
OK, I think that what I have just committed will fix the
Michael Raskin wrote:
Well, once we determine which plugins are ever needed we can create a
wrapper.. Without wrapper the easiest thing is just symlinking it into
~/.bazaar/plugins . Installing in the PATH like Python uses by default has
drawback - you cannot have symlink from current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Pierron wrote:
| Log:
| Ported fixSheBang from stdenv-updates to builder-defs.nix, tested on
Metasploit.
| No other rebuilds caused.
|
| I think You miss the stopNest command at the end of the function, or
| there is something that I am
Finally I've solved this problem chrooting into my Debian system and
getting connection up from there. Installation went smoothly, but in the
end there was a failure to install grub loader for some reason. Message
was something like grub/stage1 not read, and there was no changes to
my
701 - 800 of 820 matches
Mail list logo
