Also leaving 0_8 branch, as it's compatible with older ffmpeg versions.
I'm planning that all expressions will be able to switch easily
between ffmpeg and libav (whatever default we choose, but I prefer libav).
Add linux kernel modules needed to do kernel tracing with LTTng.
To make them available to lttng in NixOS, add this to configuration.nix:
boot.extraModulePackages = [ pkgs.linuxPackages.lttngModules ];
Babeltrace is a command-line tool and library to read and convert LTTng
tracefiles. Give it a (binary) trace file/dir path and it will print a
human readable event log to standard out.
This is the Linux Trace Toolkit. Included in this package:
Command-line client:
lttng
Tracing daemons:
lttng-sessiond (automatically started by lttng)
lttng-relayd (remote trace collection daemon)
Userspace tracing can be done by using liblttng-ust. To do kernel
tracing we also need the LTTng kernel modules.
I've added a patch that changes "/sbin/modprobe" to just "modprobe".
It has been submitted for inclusion in mainline, so it will probably
make it into 3.11 (or 3.12 as 3.11 is fairly close to release).
It is very local, only affecting people who use the "send" feature.
Without it, send is unstable/unsafe to use incrementally.
It can probably be applied to 3.9 and 3.8 as well, but as I only
tested it against 3.10, so I didn't bother.
It turns out that the .deb only contains the changelog and some other docs.
Revert back to using the i686 version, but keep the double url for the future.
The script installed with this expression only copies a boostrapper and another
script to the user's home folder. Those also need to be patched to get on with
the installation.
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>
Conflicts (a little tricky, I did some cleanup of interacting changes):
pkgs/development/compilers/llvm/default.nix
pkgs/development/libraries/libpng/default.nix
pkgs/tools/package-management/nixops/default.nix
pkgs/top-level/all-packages.nix
It's bad to have the kernel config scattered across two places. (This
should also be done for the other architectures.)
Also, restore Xen and KVM guest support in Linux 3.10.
Having N different copies of the NixOS kernel configuration is bad
because these copies tend to diverge. For instance, our 3.10 config
lacked some modules that were enabled in older configs, probably
because the 3.10 config had been copied off an earlier version of some
older kernel config.
So now there is a single kernel config in common-config.nix. It has a
few conditionals to deal with new/removed kernel options, but
otherwise it's pretty straightforward.
Also, a lot of cut&paste boilerplate between the kernel Nix
expressions is gone (such as preConfigure).
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.
We cannot import the packages from all of these three packages sets into
the global namespace, because they are indistinguishable. For example:
$ nix-env -qaP \* | grep pylint
pypyPackages.pylint pylint-0.26.0
python33Packages.pylint pylint-0.26.0
python27Packages.pylint pylint-0.26.0
When someone tries to install pylint by running "nix-env -i pylint",
then it's impossible to tell which one of these three versions was
chosen.
I can think of two ways to remedy this problem with recurseIntoAttrs:
1) Bake the name of the Python interpreter into every package's name,
i.e. offer "python27-pylint", "python33-pylint", and so on.
2) Ensure that all non-default package sets mark all their packages
'lowPrio' to unsure that the choice during installation is
deterministic.
We already have mini_httpd, but IMHO it is *too* minimal as in not very
flexible in configuration (for example, I haven't found any runtime
configuration for disabling logging), so that's why I decided to add
thttpd, which serves quite well as an ad-hoc HTTPd.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This introduces the following changes:
- New subcommand "show" for hetznerctl which shows additional
information about one or more servers.
- Allow to get subnets of a specific server through the "subnets"
attribute.
- Allow te get IP addresses of a specific server through the "ips"
attribute.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is a simple tool to scan Nixpkgs for violations of the packaging
guidelines, such as multiple packages with the same name, packages
that lack a description or license, and so on.
To use:
$ nix-env -i nixpkgs-lint
$ cd .../nixpkgs
$ nixpkgs-lint
Current statistics:
Number of packages: 8666
Number of missing maintainers: 3711
Number of missing licenses: 6159
Number of missing descriptions: 1337
Number of bad descriptions: 633
Number of name collisions: 277
KQEMU was a linux kernel module for accelerating the QEMU virtual
machine on x86 hardware. Since QEMU 0.11 (and up), there is no support
for KQEMU any more, the focus is now on KVM.
http://wiki.qemu.org/KQemu/Doc
This introduces the following changes:
- Validate Robot's SSL server certificates.
- Admin accounts can new be managed with the "admin" property of a
server instance.
- Better and fixed up error reporting.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I also added a patch that makes dovecot search for
plugins in /var/lib/dovecot/modules. This way, you
can add plugins from several packages without running
into circular dependencies. The module dir needs to
be populated before the dovecot service is started,
for example. This is currently not done in NixOS, so
you need to implement your own service in order to
get the plugins working.
The module patch has not been added to the old 2.1.x
package.
If no config.pulseaudio is explicitely set to false, build with pulse
support, because even if there is no pulse server available, chromium
will fall back to using ALSA.
And we definitely want to avoid that users have to build chromium for
themselves just for the sake of having pulse support. Thanks to @devhell
for actually helping me discovering this (I for myself do always rebuild
Chromium, so I won't notice those kind of things).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Changes are:
- Ability to set the name of a server (Server.set_name()).
- New sub-command (set-name) for hetznerctl to set server name.
- Show server name in list command.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Slic3r is a G-code generator for 3D printers.
- Math-Clipper and Boost-Geometry-Utils have been bumped to satisfy
Slic3r.
- Slic3r has problems with perl 5.16 due to a locale issue (comma vs
period in floating point numbers). So we use perl 5.14.
- The tests fail, so we skip them. According to the author of Slic3r,
that should be safe:
"Tests failed because of a typo when the 0.9.10b tag was applied.
You can safely ignore the test results, Slic3r will work."
See https://github.com/alexrj/Slic3r/issues/1303
For reference, the errors look like this:
Use of uninitialized value $deg in numeric eq (==) at /tmp/nix-build-perl-slic3r-0.9.10b.drv-0/git-export/t/../lib/Slic3r/TriangleMesh.pm line 328.
# Looks like your test exited with 255 before it could output anything.
This is just a small dependency fix for ExtUtils::CBuilder and
Module::Build to make them build with perl 5.10.
It seems that perl gradually adds CPAN modules into its core. So when
using older perl there typically some more dependencies to take care of.
ExtUtils-CBuilder 0.280202 is not available anymore, so I had to bump it
to 0.280205.
Add missing dependencies for ExtUtilsTypemapsDefault, needed when
building with perl < 5.16. This works for perl 5.16 too.
ExtUtils-ParseXS 3.15 has disappeared from the mirrors, so I had to bump
it to something available from CPAN; version 3.18.
See note from CPAN[1]:
This module [ExtUtilsTypemap] exists merely as a compatibility
wrapper around ExtUtils::Typemaps. In a nutshell, ExtUtils::Typemap
was renamed to ExtUtils::Typemaps because the Typemap directory in
lib/ could collide with the typemap file on case-insensitive file
systems.
The ExtUtils::Typemaps module is part of the ExtUtils::ParseXS
distribution and ships with the standard library of perl starting with
perl version 5.16.
[1] http://search.cpan.org/~smueller/ExtUtils-Typemap-1.00/lib/ExtUtils/Typemap.pm:
This fixes a bunch of issues for the NixOps Hetzner backend, because over there,
it's quite difficult to export the references graph without either duplicaing
lots of code or make a bunch of workarounds.
A detailed description about how it works can be found in the
meta.longDescription attribute.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is for NixOps and the corresponding Hetzner backend and allows for easy
referencing by nix-build using the -A argument.
Basically the Hetzner rescue system uses an older udev version from Debian, so
we need to use shared object major number 0 here.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
