This only happens during setup.py build and generates the corresponding
_pb2.py files from the .proto files, as they're no longer included in
the source distribution starting from 2.5.0.
Thanks to @iElectric for reporting this build failure:
http://hydra.nixos.org/build/6897112
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Changes:
0.9.0 (2013-10-05)
Support python 3.2 and 3.3 (thanks to @masayuko)
Drop supports for python 2.4 and 2.5
Replace dependency: PIL -> Pillow
(The test phase still fails, so continue having it disabled.)
Changes:
1.0.0 (2013-10-05)
Support python 3.2 and 3.3 (thanks to @masayuko)
Drop supports for python 2.4 and 2.5
Replace dependency: PIL -> Pillow
(The test phase still fails, so continue having it disabled.)
Changes:
0.5.1 (2013-10-22)
Fix bugs
0.5.0 (2013-10-05)
Support python 3.2 and 3.3 (thanks to @masayuko)
Drop supports for python 2.4 and 2.5
Replace dependency: PIL -> Pillow
(The test phase still fails for one test, so continue having it disabled.)
Changes:
1.3.2 (2013-11-19)
Fix bugs
1.3.1 (2013-10-22)
Fix bugs
1.3.0 (2013-10-05)
Support python 3.2 and 3.3 (thanks to @masayuko)
Drop supports for python 2.4 and 2.5
Replace dependency: PIL -> Pillow
(The test phase still fails for one test, so continue having it disabled.)
Changes:
* Added context manager support to Cursor
* Added padding for driver bugs writing an extra byte
* Cursor.executemany now accepts an iterator or generator.
* Compilation improvements for FreeBSD, Cygwin, and OS/X
* Use SQL_DATA_AT_EXEC instead of SQL_DATA_LEN_AT_EXEC when possible for driver compatibility.
* Row objects can now be pickled.
This patch pushes django 1.4.1 -> 1.4.10 and adds django 1.5.5 and
django 1.6. Additionally, it creates the default django package which
always points to the latest version.
Socket library built in C but provides bindings in many languages.
Highly efficient and easy to use.
[@bjornfor: whitespace fixes, quote shell variables and add meta.platforms]
Robot Framework is a generic test automation framework for acceptance
testing and acceptance test-driven development (ATDD).
http://robotframework.org/
Deepseq is a core package, and building Cabal with a version that differs from
the one shipped with GHC is probably not a good idea.
For GHC 7.0.x, however, we must override deepseq, because the library just
won't build otherwise.
- It now uses JavaScript for configuration (only),
so I had to "convert" config for NetworkManager.
- I tested suspend/restart/(un)mount on KDE/Xfce,
Phreedom tested NetworkManager config conversion.
The firmware file needs to be downloaded or extracted from the windows
driver file and configured in nixpkgs.config e.g.:
sane.snapscanFirmware = /firmware/esfw41.bin;
The default setting for extraLibs used to be the set of modules that come with
python by default but aren't usually enabled in our standard python derivation
because they require additional libraries. This meant that users who want to
*add* libraries to that set had to use a fairly complicated override, to add
more entries without loosing the ones set by default.
After this patch, the "standard libraries" such as "curses' are listed in
stdLibs while the extraLibs argument remains empty by default. This allows
users to override extraLibs without overriding the standard libraries.
Furthermore, the wrapper environment can be messed around with in an
additional 'postBuild' step. One nice application of this build step is
to patch scripts and binaries to use the wrapped python interpreter
instead of the pristine one, thereby enabling them to pick up all
modules that have been configured. The following example shows how this
is done for the 'pylint' utility:
pkgs.python27Full.override {
extraLibs = [pkgs.pylint];
postBuild = ''
cd ${pkgs.pylint}/bin
for i in *; do
rm $out/bin/$i
sed -r -e "s|^exec |exec $out/bin/python -- |" <$i >$out/bin/$i
chmod +x $out/bin/$i
done;
'';
};
The ghcWithPackage expression now has an argument 'ignoreCollisions' that
allows users to disable the path collision check like so:
(pkgs.haskellPackages.ghcWithPackages (pkgs: with pkgs; [ haskellPlatform ])).override { ignoreCollisions = true; };
See d64917ad17
for a long and detailed discussion of why these path collisions may occur.
The function ‘mkDerivation’ now checks whether the current platform
type is included in a package's meta.platform field. If not, it
throws an exception:
$ nix-build -A linux --argstr system x86_64-darwin
error: user-thrown exception: the package ‘linux-3.10.15’ is not supported on ‘x86_64-darwin’
These packages also no longer show up in ‘nix-env -qa’ output. This
means, for instance, that the number of packages shown on
x86_64-freebsd has dropped from 9268 to 4764.
Since meta.platforms was also used to prevent Hydra from building some
packages, there now is a new attribute meta.hydraPlatforms listing the
platforms on which Hydra should build the package (which defaults to
meta.platforms).
There's a zlib version included with milkytracker,
but there's no makefiles for it. I've only included
the header here, but it fails at link-time with
several 'undefined reference' errors, which simply
means it can't find the definitions, e.g. compiled
zlib.
There's bug reports on other package systems although
unfortunately still unresolved.
https://bugs.archlinux.org/task/31324http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/082180.html
I actually had this breeding in my nixpkgs overrides for a year and only
recently took the time to fix it and thus revive my video feeds :-)
The package uses a patch which is removing the dependency on gconf and
switches to storage within a shelve in ~/.miro/config instead.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Compiles fine on linux i686 and amd64. Adding myself as maintainer, even
though I'm not using the package by myself, but a friend is using it for
DJing from a NixOS live system I'm maintaining.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This uses a patch from Gentoo to disable Java support for now, as it is
not needed for supporting Mixxx (which is the package I'm preparing).
Hopefully, the patch will be applied upstream so we can safely drop it
here.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
To prevent multiple Qt libraries when developing with a custom one, the Qt
support can now be activated by directly supplying the Qt libraries as an
argument (qtLib).
qtSDK and qtFull users/developers now just have to define an override such
as the following one in order to use it inside their development
environment:
vtk.override { qtLib = qt4SDK; };
The previous behavior is still the same for vtk and vtkWithQt4 end-users.
Change-Id: I517762d4ff7de46d32cc46e6e725fd62737caa52
* There now is full support for building Haskell packages as shared libraries
for GHC versions 7.4.2 or later. The Cabal builder recognizes the following
attributes:
- enableSharedLibraries configures Cabal to build of shared libraries in
addition to static ones. This option requires that all dependencies of
the package have been compiled for use in shared libraries, too.
- enableSharedExecutables configures Cabal to prefer shared libraries when
linking executables.
The default values for these attributes are arguments to the haskellPackages
expression.
* Haskell builds now run in a LANG="en_US.UTF-8" environment to avoid plenty
of build and test suite errors. Without this setting, GHC seems unable to
deal with the UTF-8 character encoding that's generally considered standard
in the Haskell world.
* The Cabal builder supports a new attribute 'testTarget' to specify the exact
set of tests to be run during the check phase.
* The ghc-wrapper attribute ghcVersion has been removed. Instead, we use the
ghc.version attribute, which exists in unwrapped GHC derivations, too.
xc3sprog is command-line tools for programming FPGAs, microcontrollers
and PROMs via JTAG.
Homepage: http://xc3sprog.sourceforge.net/
I'm using the latest from subversion as xc3sprog doesn't seem to make
proper releases. There are only a few seemingly random snapshots at
sourceforge. And these snapshots are built binary packages, not source
archives.
NOTE: I haven't tested this on any hardware yet.
Consider this as a first step towards the integration of Qt5 into nixpkgs,
it does not yet intends to replace Qt4 on every packages even if possible.
My goal here is to have a first derivation in common between people who
needs qt5 for development purposes.
The derivation has been written from scratch but I took care to read at the
version 4 to re-integrate some patches which are still compatible. However,
I did not had enough time to test gtkStyle and flashplayerFix as I do not
use any of them. Also, OSX users will have to do some extra work because
I do not have any mac.
Finally, as some configure flags have changed and in an hope to provide a
clear package definition before it becomes mature, I voluntary added some
flags which are default. Once every option will be mastered, we will just
have to redo a pass on qt5 configure flags and remove the ones which are
set by default.
To give the ability to use a different Qt version than the default one
(which can build 3 different times Qt Libraries if we mixed the default
one, the qtcreator one and the version including all the examples and the
docs).
Right now a developer can choose to directly install the QtSDK which
includes a "full" (developerBuild + docs + examples) Qt version and uses
it to build QtCreator.
The possibility to only install QtCreator and its previous behavior has
been kept for flexibility purposes (we do not need to force someone on the
SDK approach).
FriBID is an open source software for the Swedish e-id system called
BankID. FriBID also supports processor architectures and Linux/BSD
distributions that the official software doesn't support.
https://fribid.se/index.en.html
FriBID plugin is a firefoxWrapper plugin. Enabled by setting:
nixpkgs.config.enableFriBIDPlugin = true
Kept the old hacks where they don't break the build in case they things
they fix are still relevant.
I checked that the upgrade doesn't break:
1) Asymptote and EProver builds.
2) My XeLaTeX demo from configurations/ repository.
3) Some of my own files.
The upgrade fixes problems with simultaneous use of 3D and LaTeX labels
in Asymptote.
Please provide a test that worked previously and is broken now if you
need to revert this update or its parts.
Features:
+ configurable via environment variables
+ can skip the actual launching of the lisp implementation (source it
with NIX_LISP_SKIP_CODE=1 to get all the settings)
+ currently supports SBCL, CLisp, ECL
+ determines lisp implementation from NIX_LISP_COMMAND variable or
from buildInputs
+ sets ASDF search path for packages using buildInputs
Somehow Dwarf Fortress suddenly started failing to use our libpng (or
zlib). I tried all possible combinations (supplying them via
LD_LIBRARY_PATH in the script) but it just won't work.
This solution was found in the Archlinux bug tracker: It just symlinks
all problematic .png files to their .bmp counterparts. It's ugly and
*sadly* breaks tileset support (unless you convert them to bmp) but I
think it's acceptable, as the whole expression is pretty problematic
in terms of purity.
Let's hope the next release of Dwarf Fortress will be easier to
support.
(fixes#710)
The current asciidoc expression is impure; it relies on several tools to
be found in PATH at runtime. This commit adds a enableStandardFeatures
parameter that, if true, pulls in all dependencies and patches asciidoc
to contain full paths to the tools.
I've set enableStandardFeatures = false for the existing asciidoc
attribute so that the closure size stays unchanged, at 255 MiB. The new
asciidocFull attribute (with enableStandardFeatures = true) has a
closure size of 1.5 GiB.
imagemagick, transfig, inkscape, fontconfig and ghostscript are missing
dependencies of dblatex. Instead of adding all those dependencies to the
existing dblatex attribute, make a new dblatexFull attribute for that.
Also pass --use-python-path at install time so that script shebangs end
up with #!/path/to/python instead of #!/path/to/env python (which is
impure when not run in a wrapper).
This introduces the following changes:
- Remove scraping of the Robot web interface for getting the server ID.
- Display server number whenever appropriate.
- Remove duplicate definition of exceptions.
- Gracefully return if there are no subnets available.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit 58fdf34296, because it
wasn't actually very fitting for nixpkgs in general, so let's wait for
the upcoming upstream release to address this.
Details can be found at:
https://github.com/NixOS/nixpkgs/commit/58fdf34#commitcomment-4231461
Thanks to @iElectric for the notice.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The upstream package has a new maintainer (Jeff Forcier) and thus the
main homepage for the project is the GitHub page.
Also the long description contains quite a lot of unrelevant
information, so I've used the one from PyPI, which is a lot smaller and
just contains what the library supports and does.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This patch should be backwards-incompatible and is also submitted
upstream as paramiko/paramiko#218.
The main reason for this patch is that we need it for NixOS/nixops#124
in order to cope with NixOS/nixops@a2718b6, which makes ECDSA private
key the default for new deployments.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
A small summary of the changes:
- Add tentative support for ECDSA keys.
- Add server-side support for the SSH protocol's 'env' command.
The full change log can be found at:
https://github.com/aszlig/paramiko/blob/master/NEWS
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is needed for the latest Paramiko release, which includes support
for ECDSA keys using this library.
I'm using ECDSA in the description itself, because the name also
reflects the functionality and "cryptographic signature library" would
sound odd in this case.
Also, I'm adding myself to maintainers, because I'm going to take over
maintenance for Paramiko as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit aef81d6eb6.
It's really not good to have every little package that depends on
asciidoc to pull in 1.5 GiB in dependencies (such as Lilypond).
