Frederik Rietdijk e29cf29086 libyaml: actually use 0.2.2 ... The archive that was used turned out to be incorrect. https://github.com/yaml/pyyaml/issues/320 By now a correct tarball has been uploaded but in order to prevent issues like these we fetch now instead from GitHub.		2019-07-16 11:14:40 +02:00
..
applications	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
build-support	Merge master into staging-next	2019-07-13 09:45:40 +02:00
common-updater	treewide: use dontUnpack	2019-07-01 04:23:51 -04:00
data	victor-mono: init at 1.2.1	2019-07-13 11:58:34 -04:00
desktops	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
development	libyaml: actually use 0.2.2	2019-07-16 11:14:40 +02:00
games	Merge master into staging-next	2019-07-13 09:45:40 +02:00
misc	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
os-specific	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
servers	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
shells	Merge pull request #63920 from Ma27/package-zsh-you-should-use	2019-07-09 23:28:53 +02:00
stdenv	setup.sh: add dontUnpack	2019-07-01 04:23:51 -04:00
test	treewide: use dontUnpack	2019-07-01 04:23:51 -04:00
tools	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00
top-level	Merge branch 'master' into staging-next	2019-07-15 09:39:03 +02:00