From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/baobab/
Date: Fri, 12 Mar 2021 08:01:21 +0000 (UTC) [thread overview]
Message-ID: <1615536072.29b7a66f8d40e2a4f9a697c3232aecbc8a1f1fb3.zlogene@gentoo> (raw)
commit: 29b7a66f8d40e2a4f9a697c3232aecbc8a1f1fb3
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 12 07:59:53 2021 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Mar 12 08:01:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=29b7a66f
sys-apps/baobab: Stabilize 3.38.0 amd64, #774927
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
sys-apps/baobab/baobab-3.38.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/baobab/baobab-3.38.0.ebuild b/sys-apps/baobab/baobab-3.38.0.ebuild
index d979140c605..31b963eaf1c 100644
--- a/sys-apps/baobab/baobab-3.38.0.ebuild
+++ b/sys-apps/baobab/baobab-3.38.0.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://wiki.gnome.org/Apps/Baobab"
LICENSE="GPL-2+ FDL-1.1+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
RDEPEND="
>=dev-libs/glib-2.44:2
next reply other threads:[~2021-03-12 8:01 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 8:01 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 8:41 [gentoo-commits] repo/gentoo:master commit in: sys-apps/baobab/ Pacho Ramos
2024-07-16 8:41 Pacho Ramos
2024-03-02 22:33 Mart Raudsepp
2024-02-18 6:09 Arthur Zamarin
2024-01-08 7:03 Sam James
2023-11-17 7:47 Sam James
2023-09-24 9:02 WANG Xuerui
2023-09-22 3:14 Matt Turner
2023-09-22 3:14 Matt Turner
2023-09-22 2:33 Matt Turner
2023-09-19 1:52 Matt Turner
2023-06-09 3:01 Matt Turner
2023-05-17 21:55 Matt Turner
2023-05-02 19:44 Arthur Zamarin
2023-05-02 18:28 Arthur Zamarin
2023-05-02 17:34 Arthur Zamarin
2023-05-01 12:49 Sam James
2023-04-02 0:57 Matt Turner
2023-03-19 23:38 Matt Turner
2022-12-04 2:41 Matt Turner
2022-11-23 17:52 Jakov Smolić
2022-11-07 7:26 Sam James
2022-11-05 5:59 Arthur Zamarin
2022-09-21 22:28 Matt Turner
2022-05-28 5:45 Sam James
2022-05-28 1:27 Sam James
2022-05-28 1:20 Sam James
2022-05-15 3:10 Sam James
2022-05-10 4:06 Arthur Zamarin
2022-05-07 18:28 Arthur Zamarin
2022-04-18 20:48 Jakov Smolić
2022-03-25 21:56 Matt Turner
2022-03-18 19:24 Matt Turner
2022-03-08 9:35 Sam James
2021-12-31 3:42 Yixun Lan
2021-12-11 17:36 Mart Raudsepp
2021-06-01 2:16 Matt Turner
2021-05-31 2:00 Matt Turner
2021-04-16 22:54 Matt Turner
2021-04-13 16:12 Matt Turner
2021-04-01 16:44 Thomas Deutschmann
2021-02-28 17:22 David Seifert
2020-11-07 15:23 Mart Raudsepp
2020-08-30 15:17 Thomas Deutschmann
2020-07-19 18:30 Mart Raudsepp
2019-12-23 22:23 Mart Raudsepp
2019-12-08 11:52 Mikle Kolyada
2019-12-08 11:41 Mikle Kolyada
2019-10-13 11:27 Mart Raudsepp
2019-08-05 3:51 Aaron Bauman
2019-05-18 23:05 Mart Raudsepp
2019-05-10 17:49 Mikle Kolyada
2019-05-08 9:33 Mikle Kolyada
2019-03-06 19:36 Mart Raudsepp
2018-12-29 12:41 Gilles Dartiguelongue
2018-12-28 23:58 Gilles Dartiguelongue
2018-12-02 17:27 Mart Raudsepp
2018-12-02 14:29 Mikle Kolyada
2018-12-02 10:12 Mikle Kolyada
2018-08-03 10:30 Mart Raudsepp
2018-02-03 23:43 Mart Raudsepp
2018-01-18 2:53 Mikle Kolyada
2017-08-13 17:03 Gilles Dartiguelongue
2017-04-01 16:31 Agostino Sarubbo
2017-04-01 13:16 Agostino Sarubbo
2016-11-11 12:47 Gilles Dartiguelongue
2016-10-23 23:02 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2016-06-28 20:30 Pacho Ramos
2016-06-28 20:30 Pacho Ramos
2016-03-06 18:03 Mikle Kolyada
2015-11-15 14:23 Pacho Ramos
2015-11-15 14:23 Pacho Ramos
2015-09-12 9:11 Agostino Sarubbo
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=1615536072.29b7a66f8d40e2a4f9a697c3232aecbc8a1f1fb3.zlogene@gentoo \
--to=zlogene@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