public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/sushi/
Date: Wed,  6 Mar 2019 21:17:41 +0000 (UTC)	[thread overview]
Message-ID: <1551907037.d1a2e76c4e4d58ecb8efde4925c02ca56964900c.leio@gentoo> (raw)

commit:     d1a2e76c4e4d58ecb8efde4925c02ca56964900c
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Wed Mar  6 20:19:01 2019 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Wed Mar  6 21:17:17 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d1a2e76c

gnome-extra/sushi-3.24.0: add explicit build dep on glib-utils

Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>

 gnome-extra/sushi/sushi-3.24.0.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gnome-extra/sushi/sushi-3.24.0.ebuild b/gnome-extra/sushi/sushi-3.24.0.ebuild
index 3a0f5d97509..3bcb3f8cea0 100644
--- a/gnome-extra/sushi/sushi-3.24.0.ebuild
+++ b/gnome-extra/sushi/sushi-3.24.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -37,6 +37,7 @@ COMMON_DEPEND="
 	office? ( app-office/unoconv )
 "
 DEPEND="${RDEPEND}
+	dev-util/glib-utils
 	>=dev-util/intltool-0.40
 	virtual/pkgconfig
 "


             reply	other threads:[~2019-03-06 21:17 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 21:17 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-20 20:37 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/sushi/ Arthur Zamarin
2024-08-09  9:54 Pacho Ramos
2024-03-02 22:33 Mart Raudsepp
2024-02-18  6:09 Arthur Zamarin
2024-01-08  7:03 Sam James
2023-09-24  9:02 WANG Xuerui
2023-09-22  3:13 Matt Turner
2023-09-22  2:33 Matt Turner
2023-09-18 21:56 Matt Turner
2023-08-16 22:32 Matt Turner
2023-07-27  5:11 WANG Xuerui
2023-07-15 11:43 Arthur Zamarin
2023-07-03  8:42 Jakov Smolić
2023-07-02 11:18 Sam James
2023-05-30 15:53 Matt Turner
2023-05-28  8:44 Pacho Ramos
2022-10-30 23:21 Matt Turner
2022-07-29  2:59 Sam James
2022-07-02  3:19 Matt Turner
2022-05-28  5:45 Sam James
2022-04-06  6:26 Matt Turner
2022-04-03  0:07 Matt Turner
2022-04-01 17:51 Matt Turner
2022-03-08  9:35 Sam James
2021-12-18 23:39 Matt Turner
2021-07-26  7:15 Matt Turner
2021-06-06 21:49 Matt Turner
2021-04-15 15:36 Matt Turner
2021-04-15  5:25 Sam James
2021-04-14 18:51 Mikle Kolyada
2021-03-13 18:08 Matt Turner
2020-04-25 20:17 Mart Raudsepp
2020-03-29 16:19 Mart Raudsepp
2019-12-23 22:02 Mart Raudsepp
2019-09-28 20:52 Mart Raudsepp
2019-08-05  2:46 Aaron Bauman
2019-05-18 22:08 Mart Raudsepp
2018-12-14 12:09 Gilles Dartiguelongue
2017-05-20  4:59 Mart Raudsepp
2017-05-16  8:01 Agostino Sarubbo
2017-05-15 14:17 Agostino Sarubbo
2017-05-01 16:38 Mart Raudsepp
2017-02-04 12:39 Pacho Ramos
2016-06-25 19:13 Pacho Ramos
2016-06-25 19:13 Pacho Ramos
2016-03-06 18:03 Mikle Kolyada
2015-11-15 10:30 Pacho Ramos
2015-11-15 10:30 Pacho Ramos
2015-09-07 19:58 Mikle Kolyada

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=1551907037.d1a2e76c4e4d58ecb8efde4925c02ca56964900c.leio@gentoo \
    --to=leio@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