* gnu/packages/statistics.scm (r-tgconfig): Update to 0.1.2-1.15cf199.
[source]: Fetch from github.
[properties]: Add field.
[home-page]: Use new URL.
[description]: Expand.
[license]: Use GPLv3 or later.
* gnu/packages/crypto.scm (crypto++): Update to 8.8.0.
[arguments]: Update to new style. Remove .so symbolic link installation as the
project does it now. Fix cross-compilation for GNU/Linux and MinGW targets.
Signed-off-by: Christopher Baines <mail@cbaines.net>
* gnu/packages/freedesktop.scm (maliit-framework) [arguments]: Override the
check phase to disable the ft_mimpluginmanager and ut_mimpluginmanager tests.
* gnu/packages/qt.scm (qtdeclarative) [outputs]: New field.
Series-version: 3
Series-to: 65922@debbugs.gnu.org
Series-prefix: qt-team
Cover-letter:
Avoid capturing python in qtbase, reinstate tests
Thes series removes Python from the closure of qtbase, both for versions 5.15
and 6.5. It also reinstate a few tests that was made possible thanks to
discussions with upstream following reported the issues.
END
* gnu/packages/qt.scm (qtbase) [arguments] [powerpc64le]: Disable the
tst_qpainter, tst_qprocess and tst_qsqlthread tests in the check phase.
Series-changes: 3
- New commit
* gnu/packages/qt.scm (qtbase) [native-inputs]: Add tzdata-for-tests.
[arguments]: Set the TZDIR and TZ environment variables, and reinstate the
tst_qdate, tst_qtimezone and tst_qdatetime tests in the check phase.
(qtbase-5) [source]: Replace qtbase-use-TZDIR.patch with
qtbase-5-use-TZDIR.patch.
* gnu/packages/patches/qtbase-use-TZDIR.patch: Refresh patch with upstream
version, and preserve the old one for qtbase@5 as...
* gnu/packages/patches/qtbase-5-use-TZDIR.patch: ... this.
* gnu/local.mk (dist_patch_DATA): Register new patch.
Series-changes: 2
- Use old TZDIR patch for qtbase@5 (the new one doesn't apply)
Fixes <https://issues.guix.gnu.org/65457>.
* gnu/packages/qt.scm (qtbase-5) [arguments]: Add #:disallowed-references
argument to guard against the problem reoccurring in the future.
Add do-not-capture-python phase.
(qtbase) [arguments]: Update do-not-capture-python phase.
Previously, the image repository name was automatically computed from
the packages in the manifest without allowing the user to set a custom
one. As such, changing the packages in the manifest would result in a
new image name. Thereby requiring updating documentation et cetera when
using `docker load` directory on the resulting image.
Inspired by `docker build -t`, this commit adds a new Docker-specific
option to `guix pack` which allows setting a custom repository name for
the resulting image. If this option is not specified, pack falls back
to computing the name from the manifest. Therefore, this change is
entirely backwards compatible.
Documentation has been added with: 373ec2cf8c.
* guix/scripts/pack.scm (guix-pack): Add --image-tag option.
(%docker-format-options): New constant.
(show-docker-format-options): New procedure.
(show-docker-format-options/detailed): New procedure.
(docker-image): Allow setting a custom
repository name for the created docker image via extra-options.
Signed-off-by: Sören Tempel <soeren@soeren-tempel.net>
Signed-off-by: Mathieu Othacehe <othacehe@gnu.org>
* etc/snippets/tempel/scheme-mode (origin): Unquote ‘git-fetch’, ‘svn-fetch’,
‘hg-fetch’, ‘cvs-fetch’, and ‘bzr-fetch’. Use ‘otherwise’ instead of ‘t’.
