This essentially unbreaks deploying new Hetzner machines with NixOps,
because the Hetzner robot has changed its way of handling admin
accounts.
It also now provides a more helpful error message (instead of an
AssertionError) if admin account creation has failed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Reported-by: Graham Christensen <graham@grahamc.com>
Issue: https://github.com/NixOS/nixops/issues/563
I have not yet tested scanning, but the main application works so far.
A lot of patching is required here, because the upstream project
references some paths from well-known FHS locations which of course are
not available on Nix(OS).
We also use all available aspell dictionaries right now, which is maybe
a bit ugly but it makes language switching easier.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
While not explicitly checked by setup.py or by the "chkdeps" command
from the project I have added pyinsane2 and pyocr to the list of
dependencies as well, because they're referenced in the source.
Tested by building against Python 3.3, 3.4, 3.5 and 3.6.
The build against Python 3.6 failed because pycairo doesn't build, so
it's a non-issue at least for paperwork-backend.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
First of all: This is NOT the same package as "pillowfight".
I'm not sure why people want to choose this particular name, but well,
so be it.
I haven't investigated why test_ace and test_all_2 fail, but I've
disabled these tests by now and reported the failures upstream at
jflesch/libpillowfight#2.
Tested by building against Python 3.3, 3.4, 3.5 and 3.6.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This package is a bit more involved because it assumes a lot of paths
being there in a FHS compliant way, so we need to patch the data and
binary directories for Tesseract and Cuneiform.
I've also tried to get the tests working, but they produce different
results comparing input/output. This is probably related to the
following issue:
https://github.com/jflesch/pyocr/issues/52
So I've disabled certain tests that fail but don't generally impede the
functionality of pyocr.
Tested by building against Python 3.3, 3.4, 3.5 and 3.6.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This optionally adds support for GI, because it's needed for
paperwork-backend. The new poppler_gi attribute is also marked as
lowPrio so that users won't accidentally install it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @ttuegel
The tests require a scanner to be physically attached.
Quote from the upstream README:
> Tests require at least one scanner with a flatbed and an ADF
> (Automatic Document Feeder).
>
> If possible, they should be run with at least 2 scanners connected.
> The first that appear in "scanimage -L" must be the one with the ADF.
>
> For reference, my current setup is:
>
> - HP Officejet 4620 (Flatbed + ADF)
> - HP Deskjet 2050 J510 series (Flatbed)
So we disable the tests even though it might be theoretically possible
to use qemu and an emulated scanner. Instead of the upstream tests we
just do a quick check whether initialization of the library succeeds.
Other than that the library uses ctypes.cdll to dlopen() the libsane
shared library, so we need to patch in the right store path.
Tested by building against Python 2.7, 3.3, 3.4, 3.5 and 3.6.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The upstream tag actually says 1.5.7 but the commit actually bumps the
version to 1.5.8:
https://github.com/hickeroar/simplebayes/commit/b8da72c50d20b6f8c0d
We needed to patch the setup.py because the upstream project's setup.py
reads in the README.rst for the longDescription. That very README.rst
contains non-ASCII characters which in turn throws a decoding error with
Python 3 on Nix because I think this has to do with our setup.py wrapper
that doesn't seem to recognize the right encoding when using compile().
Tested by building against Python 2.7, 3.3, 3.4, 3.5 and 3.6.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Upstream changelog without issue numbers:
* Fixes several issues with C++ template deduction.
* Fixes a issue with bound method type inference.
* Fixes a bug with cascaded tuple assignment.
* Fixed or silenced many Clang warnings.
* Fixes bug with powers of pure real complex numbers.
The full changelog with issue numbers can be found here:
https://github.com/cython/cython/blob/0.25.2/CHANGES.rst
My main reason for updating is because there were test failures on
i686-linux, although version 0.25.2 still has one test that fails.
So if we're on i686-linux and on Python 2 we just fix that one little
doctest.
The test failure has already been reported upstream at:
https://github.com/cython/cython/issues/1548
All of the failing tests (including the latter) had to do with integer
representations in that long integers are suffixed by an L while the
test cases weren't expecting this.
Built successfully on i686-linux and x86_64-linux against Python 2.7 and
Python 3.5.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
stanchion: make pam nullify typesafe
stanchion: add Darwin support
stanchion: make pam OS-checked inside of stanchion.nix
stanchion: add Darwin support
stanchion: remove OS-checked pam on all-packages.nix
stanchion: add Darwin support
This library is a fork of ``libstrophe'' and is needed if the
``profanity'' XMPP client is to have TLS support. TLS support has been
added to ``profanity'' since version 5.0.
Without this we get the following Python exception when trying to fetch
a graph in the graphite web app:
File "/nix/store/nj62jqk2xmp5c3h93pfnlqn66qj1kkvs-python-2.7.12-env/lib/python2.7/site-packages/opt/graphite/webapp/graphite/storage.py", line 335, in fetch
return whisper.fetch(self.fs_path, startTime, endTime, now)
TypeError: fetch() takes at most 3 arguments (4 given)
Fixes#21032.
Since Nix now runs builds in a user namespace with uid == 0, this
triggered the message
warning: the group ‘nixbld’ specified in ‘build-users-group’ does not exist
which make-tarball.nix turns into a fatal error. So clear
build-users-group.
http://hydra.nixos.org/build/44817408
Travis reports hash mismatch during the darwin build, although the hash has been obtained using 'nix-prefetch-url' (on NixOS). Exclude darwin from platforms until the cause is identified.
Only zoom-us depends on icu4c-54.1. Since we know that version has some vulnerabilities, and zoom-us appears to work with icu4c-57.1, I remove the icu/54.1.nix file, remove icu_54_1 from all-packages.nix, and have zoom-us depend on icu (i.e., icu4c-57.1)
A package set is constructed for a specific interpreter. Therefore, we add the
possibility to override the package set to the interpreter. This should make it
easier to override the interpreter and the package set at the same time.
Use a fixed-point combinator for the Python package set to allow easier overriding of its contents.
Earlier implementations were proposed in #16784 and #17428. This commit is by comparison much smaller
and changes only what is needed.
With the symlinked build it's only renaming 'coreutils' to
'gcoreutils' and leaving all the actual command symlinks alone.
Instead of custom renaming scripts, let's use --program-prefix
from the autotools kitchen sink. This has the nice(?) bonus that
the manpages also get prefixed with 'g' now.
The build system refuses to enable both single-binary build and
--program-prefix - but the symlink-based single-binary build couldn't
possibly work either (as it will be looking at "$0" for which command
to execute).
Add the Perl module `Swim`, version 0.1.44, generated by
`nix-generate-from-cpan`.
This Perl module is the reference implementation for the lightweight
markup language [Swim].
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
[Swim]: <https://github.com/ingydotnet/swim-info>
Add the Perl module `HTML::Escape`, version 1.10, generated by
`nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
Add the Perl module `Module::Build::Pluggable::PPPort`, version 0.04,
generated by `nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
Add the Perl module `Module::Build::Pluggable`, version 0.10,
generated by `nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
- The darwin test can now force the use of the freshly-booted darwin stdenv
- The linux test now passes enough dummy arguments
This may make debugging harder, if so, check out #20889
This largely reverts commit 599312739e.
The main reason is that it breaks the plugins, because the mentioned
commit didn't change the attributes for the plugins as well.
But instead of just fixing the attributes when we import the plugin
packages, let's just override pythonPackages in all-packages.nix.
Right now, Beets is in transition to Python 3, so we don't need to wait
that long until we can remove the dependency on Python 2:
https://github.com/beetbox/beets/releases/tag/v1.4.1
Once Python 3 support is no longer beta, we can just change this by
changing one line only instead of several.
Tested this by building beets with both external plugins.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @FRidh
Packaging itself is pretty much straightforward, the tests however
revealed a few issues, which I have fixed with a small patch that has
been upstreamed at https://github.com/karlch/vimiv/pull/32.
The other sed-based patches in postPatch are mostly NixOS-specific.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
There's no reason to disable ALL tests just because only one particular
test module is failing.
Tested on i686-linux and x86_64-linux against these Python versions:
Python 2.6: The interpreter itself doesn't build
Python 2.7: Successful for both architectures
Python 3.3: Successful for both architectures
Python 3.4: Successful for both architectures
Python 3.5: Successful for both architectures
Python 3.6: One of the dependencies of pillow doesn't build (pytest)
Tests for PyPy still fail, which is why the doCheck attribute is only
set to false if we're building for PyPy.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @desiderius, @goibhniu, @prikhi
