From: Jack Hill <jackhill@jackhill.us>
To: 39281@debbugs.gnu.org
Subject: bug#39281: [PATCH] gnu: gnome: don't propagate gnome-initial-setup
Date: Sun, 26 Jan 2020 23:52:19 -0500 [thread overview]
Message-ID: <20200127045219.2032-1-jackhill@jackhill.us> (raw)
In-Reply-To: <alpine.DEB.2.20.2001262334250.11123@marsh.hcoop.net>
Fixes bug#39281
* gnu/packages/gnome.scm (gnome)[propagated-inputs]:
remove gnome-initial-setup
---
gnu/packages/gnome.scm | 1 -
1 file changed, 1 deletion(-)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index e843bdfe08..9db379744a 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -7865,7 +7865,6 @@ world.")
("gnome-control-center" ,gnome-control-center)
("gnome-desktop" ,gnome-desktop)
("gnome-getting-started-docs" ,gnome-getting-started-docs)
- ("gnome-initial-setup" ,gnome-initial-setup)
("gnome-keyring" ,gnome-keyring)
("gnome-menus" ,gnome-menus)
("gnome-session" ,gnome-session)
--
2.25.0
next prev parent reply other threads:[~2020-01-27 4:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d65f5a5c54b87c11f535d6b3080e794c21dbedd6.camel@student.tugraz.at>
2020-01-27 2:26 ` bug#39281: gdm doesn't start Jack Hill
2020-01-27 3:30 ` Raghav Gururajan
2020-01-27 4:50 ` Jack Hill
2020-01-27 4:52 ` Jack Hill [this message]
2020-01-27 5:24 ` Leo Prikler
2020-01-28 9:37 ` Leo Prikler
2020-01-28 18:03 ` Jack Hill
2020-01-28 18:18 ` sirgazil via Bug reports for GNU Guix
2020-01-28 18:21 ` Jack Hill
2020-01-28 18:26 ` sirgazil via Bug reports for GNU Guix
2020-01-28 20:11 ` Danny Milosavljevic
2020-01-27 8:51 ` Raghav Gururajan
2020-01-27 19:08 ` Jack Hill
2020-01-27 19:54 ` sirgazil via Bug reports for GNU Guix
2020-01-27 20:13 ` Jack Hill
2020-01-27 20:24 ` Danny Milosavljevic
2020-01-27 21:06 ` Jack Hill
2020-01-27 20:29 ` Danny Milosavljevic
2020-01-27 22:07 ` sirgazil via Bug reports for GNU Guix
2020-01-28 5:21 ` Raghav Gururajan
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=20200127045219.2032-1-jackhill@jackhill.us \
--to=jackhill@jackhill.us \
--cc=39281@debbugs.gnu.org \
/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).