* gnu/packages/gnome.scm (arc-theme)[version]: Update to 20181022.
[source]: Use new fork, change to git-fetch.
[inputs]: Remove and move gtk+ to native-inputs.
[native-inputs]: Add gtk+, glib:bin, gnome-shell, inkscape, optipng and sassc.
[home-page]: Adapt to new fork.
[license]: Fix to GPL 3 or later (gpl3+).
Signed-off-by: Maxim Cournoyer <maxim.cournoyer@gmail.com>
* gnu/packages/web.scm (sassc)[arguments]: Delete bootstrap phase; let
phase end on boolean.
Signed-off-by: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Fixes <https://bugs.gnu.org/33639>.
Thanks to Ricardo Wurmus and Thomas Schmitt for their suggestions!
* gnu/build/vm.scm (make-iso9660-image): Pass "-padding 10m" to
xorriso.
The version of test-unit used is greater than one of the gemspec files was
specifying. It was already being changed in two places, so this commit changes
the json-java.gemspec file as well.
* gnu/packages/ruby.scm (ruby-json-pure)[arguments]: Add new
fix-json-java.gemspec phase.
I'm looking to upgrade capnproto, and mash fails to build with 0.7. Therefore,
tweak the compilation to allow it to build with 0.7. The package also builds
with the current version of capnproto. I got the idea of changing the c++
version from here [1].
1: https://github.com/marbl/Mash/issues/98
* gnu/packages/bioinformatics.scm (mash)[arguments]: Add new use-c++14 phase.
Some parts of Boost which are used by other Guix packages require C++14 support.
Fixes <https://bugs.gnu.org/33605>.
* gnu/packages/boost.scm (boost)[arguments]: Pass 'cxxflags=-std=c++14'
to #:make-flags.
Previously, the 'unless (file-exists? "/etc/guix/acl")' guard would mean
that only the first key in the list would get registered since were were
generating one registration snippet per key. This fixes that.
* gnu/services/base.scm (hydra-key-authorization): Change to be a
'for-each' loop iterating on #$KEYS.
Normally we shouldn't disable tests just because they fail. However,
since the recent glibc update, it's not possible to keep using an old
khal, because khal requires locales to be set up properly.
* gnu/packages/calendar.scm (khal)[arguments]: Disable a failing test.
StumpWM version 1.0.0 was the last version to support lisps other than SBCL.
This patch renames the current version of Stumpwm to simply 'stumpwm' instead
of 'sbcl-stumpwm' since it's redundant, and removes the unmaintained
'ecl-stumpwm' package.
* gnu/packages/lisp.scm (sbcl-stumpwm): Deprecate in favor of 'stumpwm'.
[name]: Rename to 'stumpwm'.
[arguments]: Set '#:asd-system-name' to 'stumpwm'.
[properties]: Replace ecl-variant with cl-source-variant.
(ecl-stumpwm): Remove variable.
(cl-stumpwm): Replace 'sbcl-stumpwm' with 'stumpwm' and adapt.
(sbcl-stumpwm+slynk): Deprecate in favor of 'stumpwm+slynk'.
[name]: Rename to 'stumpwm-with-slynk'.
[inherit, inputs, arguments]: Replace 'sbcl-stumpwm' with 'stumpwm'.
Signed-off-by: Oleg Pykhalov <go.wigust@gmail.com>
The lists of new and upgraded packages in 'NEWS' had become way too long
and redundant with what 'guix pull' reports.
* build-aux/update-NEWS.scm (write-packages-added): Don't print ADDED.
(write-packages-updates)[important, table, latest, noteworthy]: New
variables.
Print NOTEWORTHY rather than all of UPGRADED.
(main): Print PREVIOUS-VERSION and NEW-VERSION.
I guess this broke when upgrading go. I did try upgrading to the later patch
and minor releases, but they had similar problems, so lets upgrade separately.
* gnu/packages/databases.scm (mongo-tools)[arguments]: Add patch-source phase.
Looks like this test isn't compiling with newer versions of go, so fix it to
get the package building again.
* gnu/packages/golang.scm (go-gopkg.in-tomb.v2)[arguments]: Add new
patch-source phase.
The system closure has grown slightly above 1GiB so adjust accordingly.
* gnu/tests/install.scm (%simple-installation-script): Increase vdb2 size of
1.2G,
(%extlinux-gpt-installation-script); ditto
(%simple-installation-script-for-/dev/vda): ditto,
(%separate-store-installation-script): ditto for vdb3,
(%encrypted-root-installation-script): ditto.
Marius Bakke