Toggle diff (15 lines)diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scmindex ed668c280b..e9d2965f70 100644--- a/gnu/packages/gnome.scm+++ b/gnu/packages/gnome.scm@@ -3436,7 +3436,7 @@ and RDP protocols.") ; or /etc/machine-id. #:glib-or-gtk? #t #:configure-flags '("-Denable-gtk-doc=true")))- (home-page "https://developer.gnome.org/dconf")+ (home-page "https://developer.gnome.org/dconf/") (synopsis "Low-level GNOME configuration system") (description "Dconf is a low-level configuration system. Its main purpose is to provide a backend to GSettings on platforms that don't already have-- 2.26.2
dconf has over 400 dependent packages, so this should wait for the next'staging' branch. Can you fork off the current branch and push a'staging-next' so it does not get forgotten? Otherwise LGTM. The other patch can go directly on 'master'. Thanks!
(name . Marius Bakke)(address . email@example.com)(address . firstname.lastname@example.org)
On 2020-05-23 17:42, Marius Bakke wrote:
Toggle quote (12 lines)> Brice Waegeneire <email@example.com> writes:> >> * gnu/packages/gnome.scm (dconf)[arguments]: Enable tests.> > dconf has over 400 dependent packages, so this should wait for the next> 'staging' branch. Can you fork off the current branch and push a> 'staging-next' so it does not get forgotten?> > Otherwise LGTM. The other patch can go directly on 'master'.> > Thanks!
Pushed the first patch on master as 79d7b5277f803d474f8934b1680ce598c9c27e2d.And the second on staging-next as 27106f465382fc95f0f19e1cd3147cab5716a173.