pycollada is a python library for reading and writing collada documents.
collada is an open file format (XML based) for 3D applications. Filename
extension is .dae (digital asset exchange).
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.
Robot Framework is a generic test automation framework for acceptance
testing and acceptance test-driven development (ATDD).
http://robotframework.org/
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 fixes a few issues with symlinks and also needs to be up to date
because we're going to use it for building Chromium instead of the
bundled GYP that comes with Chromium.
Also, the package was missing a license and in the current revision, we
also have test cases, so let's enable them.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
As well as pyblock, the SHA256 changed here as well. Although the
changes between 1.99.32 and 1.99.39 aren't as minor as with pyblock,
this shouldn't have any impact on nixpart so I think it's safe to
upgrade (we'll see later, should we end up with failed tests in nixpart
or <nixos/tests/partition.nix>.
Of course we're now using the release tarball from the repo site here as
well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
As the SHA256 changed in the meantime and there are only minor changes
between 0.52 and 0.53, I've updated this to the release tarball, which
hopefully won't change anytime soon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Without this patch buildout will copy eggs from the nix store into the
./eggs directory and then try to compile them. This fails because they
are read only. This patch changes the behaviour to create symlinks to
eggs available in the nix store instead of copying them, and not to
try to compile the eggs in the store. To differentiate this from the
default buildout (which may be provided otherwise e.g. as a
dependency) the executable is renamed to buildout-nix.
This can be used in conjuntion with myEnvFun to create development
environments which make use of the python modules available in the
store while downloading any additional required eggs. A pleasant side
effect is that you can conveniently replace the symlink with a copy
for debugging purposes.
Using setup.py, the test suite isn't run at all, because it's not
referenced there. So let's call it directly.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The reason behind this is to avoid breaking NixOps while releasing
version 1.0 of nixpart. We could also use nixpart and nixpart1, but the
goal is to have nixpart as a generic part of NixOS instead of being only
used specifically for the Hetzner backend of NixOps.
Which essentially means: The partition syntax will change to be based on
attribute sets and we no longer need to use Kickstart syntax. And that's
the main reason why it will break in version 1.0.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Leaving this just in buildInputs won't help here, because the project
using Paramiko will need pycrypto in any case.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
It doesn't make sense to build tools/applications with three different
python interpreter versions, so move them out of python modules list.
Also reverts 53ffc6e0ef.
