depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2009-03-05	* Install some headers in the right location.	Eelco Dolstra	2	-2/+6

2009-03-03	* Allow the channel to declare a name for itself.	Eelco Dolstra	1	-0/+6

2009-02-27	* nix-install-package: don't pollute /nix/var/nix/manifests.	Eelco Dolstra	3	-11/+11

2009-02-27	* Use the regular progress bar; the hash bar isn't very useful when	Eelco Dolstra	1	-1/+1
	the size of the download isn't known in advance.
2009-02-27	* nix-build: support --option.	Eelco Dolstra	1	-0/+7

2009-02-27	* Allow options from the Nix config file to be overriden from the	Eelco Dolstra	3	-0/+21
	command line (e.g. "--option build-use-chroot true").
2009-02-27	* nix-channel: use nix-build.	Eelco Dolstra	1	-8/+6

2009-02-27	* Check the manifest version.	Eelco Dolstra	1	-3/+4

2009-02-26	* Handle base-16 hashes in manifests.	Eelco Dolstra	1	-1/+12

2009-02-19	* download-using-manifests: don't check the cryptographic hash of	Eelco Dolstra	1	-18/+30
	downloaded files; rather, check the hash of the unpacked store path. When the server produces bzipped NAR archives on demand (like Hydra does), the hash of the file is not known in advance; it's streamed from the server. Thus the manifest doesn't contain a hash for the bzipped NAR archive. However, the server does know the hash of the uncompressed NAR archive (the "NarHash" field), since it's stored in the Nix database (nix-store -q --hash /nix/store/bla). So we use that instead for checking the integrity of the download.
2009-02-19	Replace wrong (w.r.t. PATH) sed call with in-shell substitution	Michael Raskin	1	-1/+2

2009-02-16	* Release output locks as soon as possible, not when the destructor of	Eelco Dolstra	3	-0/+14
	the DerivationGoal runs. Otherwise, if a goal is a top-level goal, then the lock won't be released until nix-store finishes. With --keep-going and lots of top-level goals, it's possible to run out of file descriptors (this happened sometimes in the build farm for Nixpkgs). Also, for failed derivation, it won't be possible to build it again until the lock is released. * Idem for locks on build users: these weren't released in a timely manner for failed top-level derivation goals. So if there were more than (say) 10 such failed builds, you would get an error about having run out of build users.
2009-02-05	documentation for previous commit	Marc Weber	1	-0/+30

2009-02-05	added primop functions __isBool, __isString, __isInt	Marc Weber	1	-0/+25

2009-02-03	* Build hook: compress the transferred data.	Eelco Dolstra	1	-2/+2

2009-02-02	* Build hooks: use nix-store --import. This prevents a redundant	Eelco Dolstra	3	-22/+29
	scan for runtime dependencies (i.e. the local machine shouldn't do a scan that the remote machine has already done). Also pipe directly into `nix-store --import': don't use a temporary file.
2009-01-28	vim syntax: support for indented strings ('' .. '')	Marc Weber	1	-1/+3

2009-01-27	Add the "addErrorContext" builtin to add more information in the stack trace.	Nicolas Pierron	1	-0/+14

2009-01-27	* Make it compile on Debian 4.0 (which doesn't define PER_LINUX32_3GB	Eelco Dolstra	1	-1/+1
	in sys/personality.h).
2009-01-13	* When using a build hook, distinguish between transient failures	Eelco Dolstra	2	-6/+30
	(e.g. an SSH connection problem) and permanent failures (i.e. the builder failed). This matters to Hydra (it wants to know whether it makes sense to retry a build).
2009-01-13	(no commit message)	Eelco Dolstra	1	-1/+1

2009-01-12	* Support i686-linux builds directly on x86_64-linux Nix	Eelco Dolstra	2	-2/+24
	installations. This is implemented using the personality() syscall, which causes uname to return "i686" in child processes.
2009-01-12	* Make Nix build with Bison 2.4.	Eelco Dolstra	1	-0/+1

2009-01-05	* Removed reference to losser.st-lab.cs.uu.nl, which is RIP after 9	Eelco Dolstra	1	-1/+1
	years of loyal service :-)
2008-12-16	* nix-store --verify: repair bad hash fields in the metadata file.	Eelco Dolstra	2	-5/+16

2008-12-16	* Pass --use-atime / --max-atime to the daemon.	Eelco Dolstra	3	-1/+9

2008-12-15	* Delete the chroot if it already exists (e.g. left over from an	Eelco Dolstra	1	-0/+1
	interrupted build).
2008-12-12	* Put chroots in the Nix store. This ensures that we can create hard	Eelco Dolstra	2	-2/+14
	links to the inputs.
2008-12-12	* Simplify deleting .lock files in /nix/store: just don't delete them	Eelco Dolstra	4	-34/+38
	if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12	* Some hackery to make "make check" succeed on Cygwin.	Eelco Dolstra	2	-0/+15

2008-12-12	* Detect whether unshare() is available.	Eelco Dolstra	2	-4/+2

2008-12-12	* We can't use string objects in signal handlers because they might	Eelco Dolstra	1	-4/+4
	allocate memory, which is verboten in signal handlers. This caused random failures in the test suite on Mac OS X (triggered by the spurious SIGPOLL signals on Mac OS X, which should also be fixed).
2008-12-12	* Use a PathSet for the chroot directories so that we don't	Eelco Dolstra	1	-6/+7
	accidentally bind-mount a directory twice.
2008-12-12	* Define _GNU_SOURCE. Hopefully this fixes the build on Debian 4.0	Eelco Dolstra	1	-0/+3
	(http://hydra.nixos.org/nixlog/384/1).
2008-12-11	* Don't provide the whole Nix store in the chroot, but only the	Eelco Dolstra	1	-10/+44
	closure of the inputs. This really enforces that there can't be any undeclared dependencies on paths in the store. This is done by creating a fake Nix store and creating bind-mounts or hard-links in the fake store for all paths in the closure. After the build, the build output is moved from the fake store to the real store. TODO: the chroot has to be on the same filesystem as the Nix store for this to work, but this isn't enforced yet. (I.e. it only works currently if /tmp is on the same FS as /nix/store.)
2008-12-11	* Revert r13150: now that we use private namespaces for the chroot, we	Eelco Dolstra	4	-9/+1
	don't have to put the chroot in /nix/var/nix/chroots anymore. They're back in /tmp now.
2008-12-11	* Provide a minimal /etc/passwd in the chroot to keep some builders	Eelco Dolstra	1	-1/+12
	happy.
2008-12-11	* Do chroot builds in a private namespace. This means that all the	Eelco Dolstra	2	-134/+46
	bind-mounts we do are only visible to the builder process and its children. So accidentally doing "rm -rf" on the chroot directory won't wipe out /nix/store and other bind-mounted directories anymore. Also, the bind-mounts in the private namespace disappear automatically when the builder exits.
2008-12-11	* Open the connection to the daemon lazily (on demand) so that	Eelco Dolstra	3	-6/+38
	read-only operations (like nix-env -qa) work properly when the daemon isn't running.
2008-12-04	* Build on Debian 4.0 (GCC 4.1.1).	Eelco Dolstra	1	-1/+1

2008-12-04	* Doh.	Eelco Dolstra	1	-2/+2

2008-12-04	* Build some 64-bit RPMs/Debs.	Eelco Dolstra	1	-10/+21

2008-12-04	* Be sure to clean up the daemon if the test fails.	Eelco Dolstra	1	-0/+2

2008-12-04	(no commit message)	Eelco Dolstra	1	-2/+1

2008-12-04	* Propagate --max-silent-time to remote machines.	Eelco Dolstra	2	-2/+7

2008-12-04	* Prefer building on a remote machine over a local machine. This	Eelco Dolstra	1	-5/+6
	makes more sense for the build farm, otherwise every nix-store invocation will lead to at least one local build. Will come up with a better solution later...
2008-12-04	* Build RPMs, Debs, coverage analysis.	Eelco Dolstra	1	-50/+154

2008-12-04	* When using build hooks, for any nix-store -r build operation, it is	Eelco Dolstra	2	-7/+18
	necessary that at least one build hook doesn't return "postpone", otherwise nix-store will barf ("waiting for a build slot, yet there are no running children"). So inform the build hook when this is the case, so that it can start a build even when that would exceed the maximum load on a machine.
2008-12-04	* Force allocation of a pseudo-terminal to clean up the remote	Eelco Dolstra	1	-1/+6
	nix-store process when the connection is interrupted.
2008-12-04	* Don't ignore errors from writing to stderr. That way, when	Eelco Dolstra	1	-5/+1
	nix-store -r (or some other operation) is started via ssh, it will at least have a chance of terminating quickly when the connection is killed. Right now it just runs to completion, because it never notices that stderr is no longer connected to anything. Of course it would be better if sshd would just send a SIGHUP, but it doesn't (https://bugzilla.mindrot.org/show_bug.cgi?id=396).