The last release of this plugin appears to be 2015, and the package no
longer builds as it depends on libxfce4ui-1 which was removed when gtk+-2
support was dropped in 2019.
* gnu/packages/xfce.scm (xfce4-embed-plugin): Delete variable.
Signed-off-by: 宋文武 <iyzsong@member.fsf.org>
The last release of this plugin appears to be 2013, and the package no
longer builds as it depends on libxfce4ui-1 which was removed when gtk+-2
support was dropped in 2019.
* gnu/packages/xfce.scm (xfce4-equake-plugin): Delete variable.
Signed-off-by: 宋文武 <iyzsong@member.fsf.org>
* gnu/packages/irc.scm (weechat): Update to 3.8.
[arguments]: Do not build tests any more: since version 3.8, ‘make test’
is successful when tests are not built.
[native-inputs]: Remove dependency on cpputest as tests are not built
any more.
Signed-off-by: 宋文武 <iyzsong@member.fsf.org>
* doc/contributing.texi ("Submitting Patches")["Sending a Patch Series"]:
Note that a bug in 'git send-email' means '-v REVISION' (with a
space) will not work.
Signed-off-by: Christopher Baines <mail@cbaines.net>
Add more examples of when it can be appropriate to push changes without
review, as I think this can be appropriate in the case of trivial changes (as
mentioned before), but also non-trivial fixes.
No longer suggest pushing simple new packages or package upgrades (that don't
cause lots of rebuilds) without sending to guix-patches. Now there's some
automation for testing changes sent to guix-patches, sending changes there
before pushing can mean that more rigorous testing takes place and help speed
up substitutes becoming available. This is true, even if no human review takes
place.
Only suggest waiting one week for review for simpler changes, wait two weeks
for more significant changes.
Also, reorder some of the information in this section so it's grouped together
better.
* doc/contributing.texi (Commit Policy): Tweak.
Signed-off-by: Christopher Baines <mail@cbaines.net>
The full set of patches already merged into the U-Boot is included for
simplicity and avoiding mistakes like the previous one, where a conflicting
hunk got dropped, causing the following error when running patman:
WARNING: Unknown setting get_maintainer_script
* gnu/packages/bootloaders.scm (u-boot) [source]: Replace the
u-boot-patman-fix-help.patch, u-boot-patman-local-conf.patch and
u-boot-patman-get-maintainer.patch with u-boot-patman-guix-integration.patch.
* gnu/local.mk (dist_patch_DATA): Update patch registrations.
* gnu/packages/patches/u-boot-patman-fix-help.patch: Delete file.
* gnu/packages/patches/u-boot-patman-get-maintainer.patch: Likewise.
* gnu/packages/patches/u-boot-patman-local-conf.patch: Likewise.
* gnu/packages/patches/u-boot-patman-guix-integration.patch: New file.
Reported-by: Jelle Licht <jlicht@fsfe.org>
This fixes a regression from 543d971ed2 whereby
match-lambda due to configuration field reordering.
* gnu/services/security.scm:
[serialize-fail2ban-ignore-cache-configuration]: Switch to match-record.
[serialize-fail2ban-jail-filter-configuration]: Switch to match-record.
[serialize-fail2ban-jail-action-configuration]: Switch to match-record.
Signed-off-by: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Aarch64 CI build still fail with ‘timed out after 3600 seconds of
silence’.
* gnu/packages/linux.scm (make-linux-libre*):
Increase the max-silent-time to 3 hours.
Reported by akirakyle in #guix.
