From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: lxqt-base/lxqt-notificationd/
Date: Fri, 31 Jul 2020 16:33:09 +0000 (UTC) [thread overview]
Message-ID: <1596213069.008de1f98b811d1f6144766627e878f357e6ffda.zlogene@gentoo> (raw)
commit: 008de1f98b811d1f6144766627e878f357e6ffda
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 31 16:31:09 2020 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Jul 31 16:31:09 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=008de1f9
lxqt-base/lxqt-notificationd: amd64 stable wrt bug #734818
Package-Manager: Portage-2.3.103, Repoman-2.3.23
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
lxqt-base/lxqt-notificationd/lxqt-notificationd-0.15.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lxqt-base/lxqt-notificationd/lxqt-notificationd-0.15.0.ebuild b/lxqt-base/lxqt-notificationd/lxqt-notificationd-0.15.0.ebuild
index a78ba273344..1283a5bccec 100644
--- a/lxqt-base/lxqt-notificationd/lxqt-notificationd-0.15.0.ebuild
+++ b/lxqt-base/lxqt-notificationd/lxqt-notificationd-0.15.0.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} = *9999* ]]; then
EGIT_REPO_URI="https://github.com/lxqt/${PN}.git"
else
SRC_URI="https://github.com/lxqt/${PN}/releases/download/${PV}/${P}.tar.xz"
- KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~ppc64 ~x86"
fi
LICENSE="LGPL-2.1 LGPL-2.1+"
next reply other threads:[~2020-07-31 16:33 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 16:33 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-04 15:37 [gentoo-commits] repo/gentoo:master commit in: lxqt-base/lxqt-notificationd/ Arthur Zamarin
2024-09-12 17:23 Arthur Zamarin
2024-09-01 21:30 Sam James
2024-07-13 10:09 Yixun Lan
2024-07-11 19:44 Arthur Zamarin
2024-06-28 20:33 Jimi Huotari
2024-06-14 21:57 Jimi Huotari
2023-12-27 21:03 Sam James
2023-12-20 1:40 Sam James
2023-11-09 21:45 Jimi Huotari
2023-06-18 14:53 Andreas Sturmlechner
2023-05-29 21:57 Sam James
2023-05-29 11:05 Arthur Zamarin
2023-05-29 0:10 Sam James
2023-04-17 22:08 Jimi Huotari
2023-03-26 15:50 Jimi Huotari
2022-12-17 19:28 Arthur Zamarin
2022-12-16 21:49 Sam James
2022-12-16 20:33 Arthur Zamarin
2022-11-10 12:57 Jimi Huotari
2022-07-26 7:05 Sam James
2022-07-22 17:54 Sam James
2022-07-20 5:36 Sam James
2022-05-25 11:20 WANG Xuerui
2022-05-15 0:13 Sam James
2022-04-15 13:14 Arthur Zamarin
2022-04-15 6:17 Sam James
2022-01-21 19:07 Sam James
2021-04-18 5:09 Joonas Niilola
2021-01-23 22:55 Sam James
2021-01-21 9:03 Agostino Sarubbo
2020-11-23 7:12 Andreas Sturmlechner
2020-07-31 16:35 Mikle Kolyada
2020-05-20 23:28 Andreas Sturmlechner
2019-09-08 16:18 Andreas Sturmlechner
2019-05-23 12:30 Mikle Kolyada
2019-05-22 7:30 Mikle Kolyada
2018-10-17 12:30 Thomas Deutschmann
2018-10-16 13:07 Mikle Kolyada
2018-08-11 10:10 Jonathan Scruggs
2018-05-11 21:56 Patrice Clement
2018-04-15 12:43 David Seifert
2017-12-11 0:45 Anthony G. Basile
2016-10-28 19:11 Manuel Rüger
2016-08-07 8:28 Pacho Ramos
2015-11-28 17:36 Patrice Clement
2015-10-01 14:21 Michael Palimaka
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=1596213069.008de1f98b811d1f6144766627e878f357e6ffda.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