Change:
We currently have ~100 failing jobs on hydra: I'm hoping for a big effort from all contributors and maintainers to get this down to zero for the release at the end of march. I'll be updating this issue with further information continuously. Off we go on a sprint to making 17.03 the best release possible! Hydra jobset: Evaluation: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers: maintainers:
I can't reproduce failure of locally. EDIT: seems a transient error, marked as done.
I picked some stuff from staging that I trust. I know little about the python stuff in there, so I omitted those changes (/cc which made this a relatively large rebuild when compared to staging. I created branch and so that we're not slowed down when fixing stuff directly on 17.03.
the only issue I saw was with Python 3.4 (which is hardly used in Nixpkgs) and expat. That's an easy to solve issue. The rest is fine so I think it should all go in.
Shall we mark packages as when it works on hydra or when the build works locally?
when it is commited, I regurlarly update the list in the description based on the current hydra failures.
pandas on i686 is a known upstream bug: - I could remove the test for that platform if that's acceptable to ?
Asterisk works locally, maybe with it would also build on hydra...
yes go ahead. Upstream doesn't test against i686. Another option is to mark it as broken for i686.
So, all commits now merged from staging to master were cherry-picked to 17.03 directly, and that causes almost no rebuilds (all cached from staging). I just reset to , so we can still use it if need be.
- I sampled the Haskell failures and I'd say 80% of them are either upstream issues with e.g. newer GHCs or require manual overrides for dependencies. How about we identify the packages that people consider to be really important (e.g. I have a PR to fix purescript) and mark the rest as broken?
yes, that is what I usually do. Don't worry about the Haskell packages. There will be 0 errors in a few days.
had spurious failures - couldn't reproduce locally.
Can't reproduce failure of on my machine or a clean VM. Ran the 'reproduce locally' script and everything compiles fine.
I see in the log. Normal builds aren't allowed networking iff sandboxing is used.
Could someone have a look at and ? Travis has (the same?) issues on both, but I'm pretty sure at least should build.
We have 280 failing Python packages in 17.03.
Haskell packages now contribute 0 build or evaluation errors to
Regarding the failing of VirtualBox with kernel 4.10 I found that version 5.1.16 is working so maybe this needs to be backporter for 17.03.
Just for fun I looked at (boomerang) and the associated source code. The C++ code is so bad that the solution to the issue would be to tell upstream to write valid C++. The reason it worked before is what I would describe as "pure chance". (Yes, we can try to fix every problem ever created by everyone who ever touched a computer, but I don't think we should.) My vote (not that this is a democracy) is to remove boomerang as a package from NixOS, if the author does not fix it upstream in a reasonable amount of time.
is asterisk which has a dependency on some SVN repository, which is likely new, which means the dependency needs to be extracted out of the SVN repository in potentially a new package and the asterisk package needs to be updated. It appears that asterisk is already fixed; this needs to be reflected in the status post.
Package 'refind' is just another case of "We can't write valid code". Such garbage can better just be directed to /dev/null.
(or one of its dependencies) should be compiled with a C++11 compatible compiler, so that's a packaging flaw for the Nix maintainer in lightdm.
nbci_tools is another Nix packaging problem (it uses a compiler which is potentially too new).
refers to . That can't possibly be healthy. It also refers to non-existing tools in its compile time configuration, which would likely make some code paths useless at run-time. I.e., it needs repackaging and possibly upstream shouldn't hardcode such stuff (perhaps they shouldn't be writing code in the first place).
Marked as broken (in & )
sage seems to be an upstream problem. See: The general trend I see is that many of the packages listed are simply of low quality. It's worth considering the question: should we encourage the distribution of sequences of bits which hardly earn the label "software"?
clisp requires a build time dependency on automake-1.15 and then it will probably work.
(ultrastard) specifies a dependency when the tree has the dependency itself; it probably shouldn't specify the dependency, since it fails explicitly on user-defined libraries.
(octave) needs a C++11 compiler configured. So, that's a packaging bug.
(panomatic) shows build tool issues (autotools) and missing symbols, which might stem from too old dependencies (the upstream build system is broken, because it shouldn't try to compile things which it cannot compile). Solution would be for upstream to fix their build system first, and then we could consider it for inclusion.
(robomongo) seems so low quality that I would again vote to get rid of it completely.
sipp misses libpcap.
(ponyc) requires e.g. LLVM 3.9.0, but nothing newer.
aliceml returned this gem: ` There are many other issues; my recommendation would be to tell upstream to fix their system first and get it out of Nix. After it's fixed, it can be repackaged. The quality is just not there to have people look at this mess.
1 will probably be OK for ponyc, as there are only bugfixes atop.
We have proof that 3.9.1 does not work in the logs. We can tell them that ponyc's build system is broken after we have actually tried it with 3.9.0. They specifically mention 3.9.0. We should respect that, before we tell them something is wrong (when there likely isn't).
(taskjuggler) requires a dependency on kde-config (no idea which package that is).
(manticore) needs upstream to fix their code: From a packaging perspective can be as a dependency, since a WARNING is displayed when it's not found.
asterisk should've been fixed in . Maybe pick that to the release branch? I do use sage, it'd be nice if it was in nixpkgs (also, a more recent version) (currently I resolved the problem by having the sysadmins install it on an ubuntu server). The build failure seems to be related to a wrong version (also see ).
(freestyle) checks whether the build platform is x86-64 and stops when it is not. Whether or not this should be a problem I don't know; in principle it should be possible to do cross builds, but I thought Nix didn't always do these. If cross-building works, the check could simply be removed. Another way to fix it is to tag the build in some way such that the build infrastructure only uses x86-64 machines to build.
A way to get sage in nixpkgs is then to install it on Ubuntu and check the exact versions it is using per package and compare those to the currently specified versions in Nix and then report back on that.
Tried to just pass version of to . to run a specific script called in some directory, running this script fails…
I was the maintainer of the aliceml package. I don't use Nix anymore and would suggest removing it if recent Nix changes have broken it.
re: : I think a fresh (last week) release wants LLVM 3.9.1
I had looked on and only noticed adding 3.9.1 to the list of allowed versions, without any real changes in the code. (I don't count switching CI to 3.9.1, etc.)
Bumping the version fixed the build
(ispc) can be easily fixed by changing the dependency to . This is apparently a known regression of flex 2.6.3 ()
fixed already
I have looked into tribler, both the current version (6.4.3) and the latest stable release (6.5.2) depend on wxPython 2.8, wich was removed in commit . I suppose we should either bring back wxPython 2.8, mark tribler as broken, or upgrade it to a more recent beta version. I volunteer to do any of these things if you want.
claimed that wxPython 2.8 is broken. may remember more.
the last update on the package by a user was . If tribler needs wxPython 2.8 then that means it was broken already for at least 10 months (and thus also in 16.09). Therefore I think we should mark it as broken or just get rid of it.
I agree. I will probably try to build the 7.0.0-beta for myself though, would it be Ok to mark it as broken and add it back when there is a stable release? or is it better to remove it and maybe add it back whenever it's working again?
If the 7.0.0-beta works you can update to that, too.
Ok, then, I will try it.
should fix blink once merged.
python3.5- build has been one of the channel channel blockers for a few days (a transitive dependency of gnome); any ideas?
yep, there's a upgrade on master that is needed. There are a couple of commits that depend on that as well so let's see whether I can cherry-pick them without breaking anything more.
Thanks! The less risky, the better. Our plan is to release in about ten days and our channel is still ten days old... (which lowers the amount of users running the code and may hide other problems)
Staged that fix, so blink should be OK after that.
Tested job succeeded! Expecting channel bump today :-)
tribler 7.0.0-beta working,
~I can't reproduce the error of on my machine. The build process runs through without an error and the binaries seem to work as intended. If someone can confirm this we should be able to remove it from the list.~ Seems to be reproducible with 32bit
Refind was dropped? Well, I think it is a good thing: it only compiles with an old version of gnu-efi.
I'm fairly confident that the daemontools and runit.i686 failures are hydra problems; both build fine locally.
Closing as the release is imminent and there are no larger failures.

Discussion:
<ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.15.2"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.15/${name}.tar.xz"; sha256 = "0g71zq6dpqrw2f40wfzdf18fdw41ymr17laqniy2kr622hkxdi8w"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>

<ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.16.1"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.16/${name}.tar.xz"; sha256 = "1n708n9ixyy9qrzyv1wf4ybvcclx43ib9ki028wwpvkz6kv8zqlb"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>

{stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { <del> name = "vala-0.14.2"; </del> <ins> version = "0.17.2"; name = "vala-${version}"; </ins> src = fetchurl { <del> url = mirror://gnome/sources/vala/0.14/vala-0.14.2.tar.xz; sha256 = "1l5kllw9vpwv24lzv9fp64l3sad46wpxgvsgryrwlrjg91w6jzl0"; </del> <ins> url = "mirror://gnome/sources/vala/0.17/${name}.tar.xz"; sha256 = "09i2s0dwmrk147ind2dx7nq845g12fp6fsjqrphhrr0dbi0zzgh3"; </ins> }; buildNativeInputs = [ yacc flex pkgconfig xz ];

meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; <ins> license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; </ins> }; }

urweb = callPackage ../development/compilers/urweb { }; <del> vala = callPackage ../development/compilers/vala { }; </del> <ins> vala = vala17; vala15 = callPackage ../development/compilers/vala/15.2.nix { }; vala16 = callPackage ../development/compilers/vala/16.1.nix { }; vala17 = callPackage ../development/compilers/vala/default.nix { }; </ins> visualcpp = callPackage ../development/compilers/visual-c++ { };