* gnu/packages/emacs-xyz.scm (emacs-exwm): Fix the package.
EXWM project team removed exwm-config-example. Now exwm will not work if
the user doesn't have any configuration in ~/.emacs (or any other emacs init
file). I suggest leaving exwm-enable and a link to the project's wiki
page. So the user will have at least a fullscreen emacs window to work with.
Signed-off-by: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Change-Id: If415c91899f694e59f21b519d42548dde89c0628
This remedies an issue where applications like systemsettings and
plasma-discover do not completely respect theming (e.g. when dark theme is
enabled), with the following notable error message:
kf.kirigami.platform: Failed to find a Kirigami platform plugin for style "org.kde.desktop"
* gnu/packages/kde-frameworks.scm (qqc2-desktop-style)[inputs]: Add
kcolorscheme.
[arguments]<#:tests?>: Disable failing tests introduced by adding the
kcolorscheme input.
Change-Id: Ic34da2a2fc788737e543eb3cd2b23edf85a736a4
* gnu/packages/python-check.scm (python-pytest-mp): Upstream archived this
project and it is not used by any other packages.
Change-Id: Ibe0d98b8d7442a29aee7fcddf508caa40db72a0c
* gnu/packages/guile-xyz.scm (guile-cv): Update to 0.4.0.
[arguments]: Set GUILE_AUTO_COMPILE to prevent warnings, fix and
separate phase modifications into different tasks. Use G-expression.
Remove trailing #t.
[inputs]: Replace guile-2.0 with guile-3.0.
[native-inputs]: Update syntax. Add autoconf, automake, texinfo,
libtool and gettext-minimal.
[propagated-inputs]: Update syntax.
Change-Id: I0a4141740de7cdadbe103c62831f11474cb4ddb2
The tarball was modified upstream. Apart from regenerating
pan/inst/doc/pan-tr.pdf and updating pan/DESCRIPTION, it changes
build/vignette.rds, data/YWC.data.rda, data/bitest.rda, and
data/marijuana.rda all in the same 020f → 0403 way:
-00000000: 5244 5832 0a58 0a00 0000 0200 020f 0200 RDX2.X..........
+00000000: 5244 5832 0a58 0a00 0000 0200 0403 0200 RDX2.X..........
No idea what that means (probably nothing) but now you've been Informed.
* gnu/packages/cran.scm (r-pan)[source]: Update sha256.
Change-Id: Ib6e6d13fe7b3a46de21c7eeef7223c9338565860
* gnu/packages/admin.scm (dool): Update to 1.3.3.
[arguments]<phases>: Fix "check" phase by removing "-f" option from the dool
arguments as it leads to failures during tests but works after installation.
Don't remove "examples/dstat.py" as it is already removed in the upstream.
Change-Id: I22714bc03bf248b97ba8f21835aedb213e1b281b
The nano variant for was not nano. It was just a copy of the original
one with different name. This meant there were no _nano.a files present
at all, and the flags were the same, not producing a smaller library.
* gnu/packages/embedded.scm (make-base-newlib-arm-none-eabi-7-2018-q2-update):
Rename variable from make-newlib-arm-none-eabi-7-2018-q2-update.
* gnu/packages/embedded.scm (make-newlib-nano-arm-none-eabi-7-2018-q2-update):
Add variable.
* gnu/packages/embedded.scm (make-newlib-arm-none-eabi-7-2018-q2-update):
Inherit from make-base-newlib-arm-none-eabi-7-2018-q2-update.
Change-Id: I01517ed860dfb2b6a9c7e912fd724832f5a0500a
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
The arm-none-eabi nano toolchain had same libstdc++ as the non-nano variant.
The libstdc++ should be compiled with -fno-exceptions to make a nano
toolchain.
Additionally, since the "_nano.a" variants were not present, it was impossible
to compile C++ programs with libstdc++ using --specs=nano.specs,
since libstdc++_nano.a was not found.
The `--with-target-subdir="."` flag is a preparation for gcc-12 introduction
since the libstdc++ doesn't build without that, failing on GCC_NO_EXECUTABLES
error in configure stage. I have not been able to find out another workaround.
* gnu/packages/embedded.scm (make-libstdc++-arm-none-eabi):
[arguments]<#:make-flags>: Add CFLAGS and CXXFLAGS.
[arguments]<#:configure-flags>: Add --with-target-subdir.
* gnu/packages/embedded.scm (make-libstdc++-nano-arm-none-eabi): Add variable.
Change-Id: I06a507fef07352a4ec80d84e4d97065343fc2295
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
The libstdc++ made for arm-none-eabi puts the contents
into "lib" folder, but that's unexpected when the resulting
toolchain is a cross toolchain.
The folder should be "arm-none-eabi/lib", that's the path
added to CROSS_C_LIBRARY_PATH
* gnu/packages/embedded.scm (make-libstdc++-arm-none-eabi):
[arguments]<#:configure-flags>: Point --libdir to arm-none-eabi/lib.
[arguments]<#:strip-directories>: Set to arm-none-eabi/lib.
Change-Id: Ia8b867a1c6ebeedeae9564e0a6a1e0401b35bd5b
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This fixes native-search-paths of arm-none-eabi toolchains
The toolchains CROSS_CPLUS_INCLUDE_PATH had C include directory
first, and the C++ as second. Since <cstdlib> does #include_next <stdlib.h>,
the toolchains could not build anything using <cstdlib>. The C include
has to come later than C++ one. This is already fixed in xgcc search-path.
* gnu/packages/embedded.scm (make-gcc-arm-none-eabi-4.9,
make-gcc-arm-none-eabi-7-2018-q2-update): [native-search-paths]: Put C include
path as last.
Change-Id: Ib7e36e57e510ac87960375cad40ff0b9e749101c
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Fixes CVEs 2024-9392, 2024-9393, 2024-9394, 2024-9401 and 2024-9680.
See the Mozilla Foundation Security Advisories
<https://www.mozilla.org/en-US/security/advisories/mfsa2024-48/> and
<https://www.mozilla.org/en-US/security/advisories/mfsa2024-51/>
for details.
* gnu/packages/tor-browsers.scm (%torbrowser-build-date): Update to
20241008182800.
(%torbrowser-version): Update to 13.5.7.
(%torbrowser-firefox-version): Update to 115.16.0esr-13.5-1-build3.
(torbrowser-translation-base): Update to
ceb66dd0937da14962cb535699242b2526e11f02.
(torbrowser-translation-specific): Update to
dbf1454fdbd3256d65985cc1c46391ce0ec159e7.
(make-torbrowser) [arguments] <#:phases>: On 'copy-basebrowser-locales
stop copying 'cryptoSafetyPrompt.properties'. See
<cf68476c67>.
Change-Id: Ic17a669c1311d92da347e11ea08acc7a218bc728
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This changes adds a ‘timeout’ property, which is necessary when building
either ‘linux-libre’ or ‘linux-libre-headers’ on aarch64-linux, where
deblobbing takes more than 5 hours (the default timeout for Cuirass
jobs).
* gnu/packages/linux.scm (%linux-libre-timeout-properties): New
variable.
(make-linux-libre-headers*): Use it.
(make-linux-libre*): Likewise.
Change-Id: I0c398e06f1b9b1d217fa82493b79bca8589408c0
