| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\
| |
| | |
libguestfs-appliance: do not build on Hydra
|
| | |
|
| |
| |
| |
| |
| |
| | |
Keras expects keras_preprocessing 1.0.2 and 1.0.4. 1.0.3 and 1.0.5
are respectively in nixpkgs.
ZHF #45960
|
| |
| |
| |
| |
| |
| | |
It broke perlPackages.MouseXGetOpt
This reverts commit ad47c381bda2d38cddb96e15efd4ea5b4836f542.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
backblaze v1.3.6 incorporates[1] a fix[2] for autocompletion that replaced
`have` function with `_have`. The postInstall hook therefore needs
to be updated to replace `_have`.
[1] https://github.com/Backblaze/B2_Command_Line_Tool#136-august-21-2018
[2] https://github.com/Backblaze/B2_Command_Line_Tool/pull/497
|
| | |
|
|/ |
|
|
|
|
|
| |
Hold off the upgrade until parquet 1.5.0 is released.
This reverts commit 72d630779d69b0aff30f47bc8423e10d1dba50b9.
|
|
|
| |
Changelog: https://github.com/go-gitea/gitea/releases/tag/v1.5.1
|
|
|
|
|
|
|
| |
This reverts commit acfa8cb2a98f96d96c46b52c7563f0be3bf4e700.
This fails because none of the tests seems to be working for the version
that's in nixpkgs master.
|
| |
|
| |
|
|
|
|
| |
The patches are unmaintained and suggest a false sense of security
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
This also fixes the build.
|
|\ \
| | |
| | | |
perlPackages.UNIVERSALref: broken with perl 5.26+
|
|/ / |
|
| |
| |
| |
| | |
https://lists.nic.cz/pipermail/knot-dns-users/2018-August/001423.html
|
| |
| |
| |
| | |
Without that I couldn't well do the grandparent commit.
|
| | |
|
| |
| |
| |
| |
| | |
Broken in 62dca7c9a; the tricky thing is that it depends on nix version.
Explanation: https://github.com/NixOS/nix/issues/629
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|
|\ \
| | |
| | | |
python.pkgs.irc: 14.2.2 -> 16.4
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds a release notes entry to make users (and especially
developers) aware so they no longer need to use </para><para> in option
descriptions as this is now done automatically on every two consecutive
newlines.
More details can be found in the commit message of f865d0feabfafbb30a9e.
Signed-off-by: aszlig <aszlig@nix.build>
|
|\ \ \
| | | |
| | | | |
augeas: 1.10.1 -> 1.11.0
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
augeas
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Name coming in the future.
|
|\ \ \ \
| | | | |
| | | | | |
nixos: Split paras by \n\n in option descriptions
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
What annoyed me for a long time was the fact, that in order to break
into a new paragraph, you need to insert </para><para> in the
description attribute of an option.
Now we will automatically create <para/> elements for every block that
is separated by two consecutive newlines.
I first tried to do this within options-to-docbook.xsl, but it turns
out[1] that this isn't directly possible with XSLT 1.0, so I added
another XSLT file that postprocesses the option descriptions that are
now enclosed in <nixos:option-description/> by options-to-docbook.xsl.
The splitting itself is a bit more involved, because we can't simply
split on every \n\n because we'd also split text nodes of elements, for
example:
<screen><![CDATA[
one line
another one
]]></screen>
This would create one <para/> element for "one line" and another for
"another line", which we obviously don't want because <screen/> is used
to display verbatim contents of what a user is seeing on the screen.
So what we do instead is splitting *only* the top-level text nodes
within the outermost <para/> and leave all elements as-is. If there are
more than one <para/> elements at the top-level, we simply don't process
it at all, because the description then already contains </para><para>.
https://www.mhonarc.org/archive/html/xsl-list/2012-09/msg00319.html
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @edolstra, @domenkozar
|
| | | | | |
|
| | | | | |
|
| | | | | |
|