pitz is a distributed bug tracker, inspired by ditz. Homepage:
http://pitz.tplus1.com/
pitz has a command line interface, pitz-<command>, and a webapp,
pitz-webapp.
TODO: pitz has a pitz-shell utility that depends on ipython, but when I
enabled it it raised an exception. I think it depends on an old IPython
version:
from IPython.Shell import IPShellEmbed
ImportError: No module named Shell
A broken pitz-shell doesn't affect the rest of the command line
interface nor the webapp, so it is not critical to have it working.
There are not many distributed bug trackers out there, so I hope that
adding pitz to nixpkgs may inspire people to support pitz (or similar
software).
Theoretically this could be automatically detected by finding all
packages named 'linux' and choosing the latest, but that's overkill.
Just update it when a new kernel is added.
Signed-off-by: Shea Levy <shea@shealevy.com>
Add these new attributes (all default to true):
notebookSupport
qtconsoleSupport
pylabSupport
pylabQtSupport
This adds jinja2, matplotlib, pyqt4 and sip as new dependencies of
ipython.
This commit fixes "ipython --pylab" so that it no more errors out with
"ImportError: No module named matplotlib" (which was my initial goal).
Actually only pyGtkGlade was missing in propagatedBuildInputs. In addition,
buildInputs is quite redundant in this case, so let's drop it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
That is, there are now distinct jobs like ‘coreutils.x86_64-linux’ and
‘coreutils.x86_64-darwin’, rather than a single job ‘coreutils’ with
multiple builds. This means that testing a job is simpler:
$ nix-build pkgs/top-level/release.nix -A coreutils.x86_64-linux
See https://github.com/NixOS/hydra/issues/60 for the motivation.
First, pass in `self' again so that overriding works properly (thanks
for pointing that out, @edolstra)
Second, instead of having linuxPackages*.kernel mean something different
inside the set and out, add a new attribute linuxPackages*.kernelDev,
which for the generic kernel is simply linuxPackages*.kernel but for the
manual-config kernel is the `dev' output (which has the build tree,
source tree, etc.)
The second change required trivial modifications in a bunch of
expressions, I verified that all of the linuxPackages* sets defined in
all-packages.nix have the same drv paths before and after the change.
Signed-off-by: Shea Levy <shea@shealevy.com>
