From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 38544@debbugs.gnu.org
Subject: bug#38544: [PATCH] gnu: gparted: Use the Glib-or-GTK build system.
Date: Tue, 14 Jul 2020 15:50:19 +0200 [thread overview]
Message-ID: <20200714135019.25283-1-me@tobias.gr> (raw)
In-Reply-To: <87muc16c8x.fsf@elephly.net>
Fixes <https://issues.guix.gnu.org/38544>.
* gnu/packages/disk.scm (gparted)[build-system]: Use
glib-or-gtk-build-system.
---
raingloom 写道:
> I tried fixing this by adding the wrapper step from glib-or-gtk but
> that didn't do anything.
Strange, this works for me (after a pointless detour writing a custom wrap phase with shared-mime-info et al):
gnu/packages/disk.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/disk.scm b/gnu/packages/disk.scm
index a5278d8c8c..6d812f560c 100644
--- a/gnu/packages/disk.scm
+++ b/gnu/packages/disk.scm
@@ -78,6 +78,7 @@
#:use-module (gnu packages xml)
#:use-module (gnu packages xorg)
#:use-module (guix build-system gnu)
+ #:use-module (guix build-system glib-or-gtk)
#:use-module (guix build-system go)
#:use-module (guix build-system python)
#:use-module (guix build-system trivial)
@@ -432,7 +433,7 @@ and can dramatically shorten the lifespan of the drive if left unchecked.")
version "/gparted-" version ".tar.gz"))
(sha256
(base32 "092rgwjh1825fal6v3yafq2wr0i61hh0a2n0j4296zn0zdx7pzp2"))))
- (build-system gnu-build-system)
+ (build-system glib-or-gtk-build-system)
(arguments
;; Tests require access to paths outside the build container, such
;; as '/dev/disk/by-id'
--
2.27.0
next prev parent reply other threads:[~2020-07-14 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 10:10 bug#38544: gparted segfaults Ricardo Wurmus
2019-12-10 7:38 ` Gábor Boskovits
2020-01-04 18:35 ` raingloom
2020-07-14 13:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-07-16 10:07 ` bug#38544: [PATCH] gnu: gparted: Use the Glib-or-GTK build system Ludovic Courtès
2020-07-16 18:18 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714135019.25283-1-me@tobias.gr \
--to=bug-guix@gnu.org \
--cc=38544@debbugs.gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).