From: "Sebastian Pipping" <sping@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/redshift/
Date: Sun, 22 May 2022 13:15:13 +0000 (UTC) [thread overview]
Message-ID: <1653225258.378f21931988b1a2f3a2bf4e5729f931b4063955.sping@gentoo> (raw)
commit: 378f21931988b1a2f3a2bf4e5729f931b4063955
Author: Sebastian Pipping <sping <AT> gentoo <DOT> org>
AuthorDate: Sun May 22 13:14:18 2022 +0000
Commit: Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Sun May 22 13:14:18 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=378f2193
x11-misc/redshift: Re-add missing gnome2-utils inherit
Closes: https://bugs.gentoo.org/846353
Signed-off-by: Sebastian Pipping <sping <AT> gentoo.org>
Package-Manager: Portage-3.0.30, Repoman-3.0.3
x11-misc/redshift/redshift-1.12-r6.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/redshift/redshift-1.12-r6.ebuild b/x11-misc/redshift/redshift-1.12-r6.ebuild
index 6237b4da5cea..05517cf8915b 100644
--- a/x11-misc/redshift/redshift-1.12-r6.ebuild
+++ b/x11-misc/redshift/redshift-1.12-r6.ebuild
@@ -5,7 +5,7 @@ EAPI=8
PYTHON_COMPAT=( python3_{8..10} )
-inherit flag-o-matic systemd autotools python-r1
+inherit flag-o-matic systemd autotools gnome2-utils python-r1
DESCRIPTION="A screen color temperature adjusting software"
HOMEPAGE="http://jonls.dk/redshift/"
next reply other threads:[~2022-05-22 13:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 13:15 Sebastian Pipping [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 4:55 [gentoo-commits] repo/gentoo:master commit in: x11-misc/redshift/ Sam James
2024-05-29 12:15 Sam James
2024-05-29 6:26 Jakov Smolić
2024-05-28 22:01 Sam James
2023-11-05 22:04 Sebastian Pipping
2023-05-08 9:11 Pacho Ramos
2023-04-28 15:02 Arthur Zamarin
2023-04-27 23:32 Sam James
2023-04-27 23:29 Sam James
2022-12-27 0:45 Sebastian Pipping
2022-12-09 22:07 Arthur Zamarin
2022-12-09 22:07 Arthur Zamarin
2022-12-09 22:04 Arthur Zamarin
2022-10-19 8:55 Piotr Karbowski
2022-08-30 18:26 Andreas Sturmlechner
2022-06-10 21:38 Jakov Smolić
2022-06-09 7:39 Agostino Sarubbo
2022-06-09 7:34 Agostino Sarubbo
2022-06-08 8:43 Agostino Sarubbo
2022-05-22 19:11 Sebastian Pipping
2022-05-21 20:15 Sebastian Pipping
2022-01-25 21:25 Sam James
2022-01-21 10:03 Jakov Smolić
2022-01-21 10:03 Jakov Smolić
2021-10-11 8:35 Marek Szuba
2021-04-20 20:14 Sebastian Pipping
2021-04-20 16:57 Sebastian Pipping
2021-04-16 11:23 Sam James
2021-03-28 0:57 Sebastian Pipping
2021-02-21 2:36 Jonas Stein
2020-11-30 19:18 Piotr Karbowski
2020-11-30 18:57 Piotr Karbowski
2020-05-01 17:57 Pacho Ramos
2019-12-09 16:59 Sebastian Pipping
2019-12-02 5:21 Aaron Bauman
2019-12-02 5:21 Aaron Bauman
2019-11-24 23:23 Sebastian Pipping
2019-02-18 16:40 Sebastian Pipping
2018-12-09 22:00 Sebastian Pipping
2018-07-16 6:32 Johannes Huber
2018-07-15 15:13 Mikle Kolyada
2018-07-15 14:23 Thomas Deutschmann
2018-05-21 21:20 Sebastian Pipping
2018-04-13 20:24 Sebastian Pipping
2018-03-31 16:11 Sebastian Pipping
2017-05-15 14:06 Manuel Rüger
2017-04-15 7:33 Michał Górny
2017-02-23 7:44 Jeroen Roovers
2017-02-22 16:08 Agostino Sarubbo
2016-11-30 13:51 Sebastian Pipping
2016-01-03 4:16 Sebastian Pipping
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1653225258.378f21931988b1a2f3a2bf4e5729f931b4063955.sping@gentoo \
--to=sping@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox