The revision of the glfw fork that Rack depends on has been removed from
GitHub. This causes cloning of the glfw submodule for the Rack git
repository to fail.
As the glfw fork just adds a function that is only needed on Darwin (and
we don't support that platform at the moment) we remove the function
call from the Rack source. We can then use the upstream version of glfw.
We fetch the rest of the submodules manually as well.
See https://github.com/NixOS/nixpkgs/issues/71189 for the context.
* friture: 0.36 -> 0.37
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/friture/versions
* friture: restrict to Linux platforms
Fails on Darwin with:
Traceback (most recent call last):
File "nix_run_setup", line 8, in <module>
exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
File "setup.py", line 13, in <module>
import sounddevice # to find the libportaudio.dylib path
File "/nix/store/2sr2xabfdkcijzkwg5ic99lprwd6slij-python3.7-sounddevice-0.3.13/lib/python3.7/site-packages/sounddevice.py", line 61, in <module>
_lib = _ffi.dlopen('/nix/store/gzy8haziv610wbalnllcjpf3gd9f5619-portaudio-190600-20161030/lib/libportaudio.so.2')
OSError: cannot load library '/nix/store/gzy8haziv610wbalnllcjpf3gd9f5619-portaudio-190600-20161030/lib/libportaudio.so.2': dlopen(/nix/store/gzy8haziv610wbalnllcjpf3gd9f5619-portaudio-190600-20161030/lib/libportaudio.so.2, 2): image not found
Fixes
$ qsynth
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Aborted (core dumped)
(Also, take qt5.* attrs as input instead of the whole qt5 attrset itself.)
elementary OS's ecosystem is curated around Ubuntu's LTS releases.
This means the development platform for their curated applications
always includes a LTS version of vala (in 18.04 it's 0.40).
Because of how vala development works it suspect some of these
applications to have serious issues if complied with the latest vala.
However in the past year or so, for Pantheon at least, I don't think
their applications will have much issues with latest vala, and if there
is I don't think they'd be difficult to fix. In this single regard they've
become more responsive since their preferred language is vala.
As for the curated applications I have less of this confidence in.
So I'd have to be accept less applications, but that's something
I'm willing to compromise on. And this is easily reversible or
could be done on a per-application basis. And nix already makes
this trivial.
