From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-apps/kmail/
Date: Fri, 7 Oct 2016 16:02:00 +0000 (UTC) [thread overview]
Message-ID: <1475856110.7568b0e0cb4eca532a88db61d055831b7f459bbe.kensington@gentoo> (raw)
commit: 7568b0e0cb4eca532a88db61d055831b7f459bbe
Author: Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 7 16:01:45 2016 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Fri Oct 7 16:01:50 2016 +0000
URL: https://gitweb.gentoo.org/proj/kde.git/commit/?id=7568b0e0
kde-apps/kmail: require at least Qt 5.7.0
Qt 5.7.0 is required to fully resolve CVE-2016-7968.
Gentoo-bug: 596228
Package-Manager: portage-2.3.1
kde-apps/kmail/kmail-16.08.49.9999.ebuild | 1 +
kde-apps/kmail/kmail-9999.ebuild | 1 +
2 files changed, 2 insertions(+)
diff --git a/kde-apps/kmail/kmail-16.08.49.9999.ebuild b/kde-apps/kmail/kmail-16.08.49.9999.ebuild
index 5dba7cb..bff26f8 100644
--- a/kde-apps/kmail/kmail-16.08.49.9999.ebuild
+++ b/kde-apps/kmail/kmail-16.08.49.9999.ebuild
@@ -7,6 +7,7 @@ EAPI=6
KDE_HANDBOOK="forceoptional"
KDE_TEST="forceoptional"
KMNAME="kdepim"
+QT_MINIMAL="5.7.0"
VIRTUALX_REQUIRED="test"
inherit kde5
diff --git a/kde-apps/kmail/kmail-9999.ebuild b/kde-apps/kmail/kmail-9999.ebuild
index b048106..bb6cdc3 100644
--- a/kde-apps/kmail/kmail-9999.ebuild
+++ b/kde-apps/kmail/kmail-9999.ebuild
@@ -6,6 +6,7 @@ EAPI=6
KDE_HANDBOOK="forceoptional"
KDE_TEST="forceoptional"
+QT_MINIMAL="5.7.0"
VIRTUALX_REQUIRED="test"
inherit kde5
next reply other threads:[~2016-10-07 16:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 16:02 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 22:52 [gentoo-commits] proj/kde:master commit in: kde-apps/kmail/ Andreas Sturmlechner
2024-11-10 22:52 Andreas Sturmlechner
2024-08-11 6:58 Andreas Sturmlechner
2024-05-17 19:50 Andreas Sturmlechner
2024-03-03 15:05 Andreas Sturmlechner
2024-02-25 23:14 Sam James
2023-07-06 12:00 Andreas Sturmlechner
2023-01-15 12:30 Andreas Sturmlechner
2022-10-06 9:02 Andreas Sturmlechner
2022-03-03 11:07 Andreas Sturmlechner
2022-02-17 19:00 Sam James
2021-04-25 8:00 Andreas Sturmlechner
2021-04-16 9:35 Andreas Sturmlechner
2021-04-15 22:32 Andreas Sturmlechner
2021-04-04 19:21 Andreas Sturmlechner
2020-09-07 15:07 Andreas Sturmlechner
2020-08-30 19:02 Andreas Sturmlechner
2020-05-19 11:20 Andreas Sturmlechner
2020-04-04 0:41 Andreas Sturmlechner
2020-03-02 17:16 Andreas Sturmlechner
2019-10-24 18:37 Andreas Sturmlechner
2019-09-11 8:09 Andreas Sturmlechner
2019-04-27 19:08 Andreas Sturmlechner
2018-12-13 22:24 Andreas Sturmlechner
2018-10-15 10:14 Andreas Sturmlechner
2017-12-15 20:09 Andreas Sturmlechner
2017-11-25 15:24 Andreas Sturmlechner
2017-10-21 18:34 Andreas Sturmlechner
2017-08-02 23:22 Andreas Sturmlechner
2016-12-17 19:51 Johannes Huber
2016-12-14 11:27 Michael Palimaka
2016-10-13 11:41 Michael Palimaka
2016-10-13 11:41 Michael Palimaka
2016-08-31 14:33 Michael Palimaka
2016-08-10 15:35 Michael Palimaka
2016-08-05 17:28 Michael Palimaka
2016-06-23 11:54 Michael Palimaka
2016-05-11 9:51 Michael Palimaka
2016-04-04 22:25 Johannes Huber
2016-03-21 15:58 Johannes Huber
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=1475856110.7568b0e0cb4eca532a88db61d055831b7f459bbe.kensington@gentoo \
--to=kensington@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