public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility/
Date: Tue,  7 Aug 2018 22:27:26 +0000 (UTC)	[thread overview]
Message-ID: <1533678060.40dff0ee6efd2ae97c6a3f162de5a5f3994078a0.monsieurp@gentoo> (raw)

commit:     40dff0ee6efd2ae97c6a3f162de5a5f3994078a0
Author:     Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
AuthorDate: Sat Jun 23 19:11:06 2018 +0000
Commit:     Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Tue Aug  7 21:41:00 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40dff0ee

app-forensics/volatility: use HTTPs.

Closes: https://github.com/gentoo/gentoo/pull/9025

 app-forensics/volatility/volatility-2.4.1.ebuild | 6 +++---
 app-forensics/volatility/volatility-2.6.ebuild   | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/app-forensics/volatility/volatility-2.4.1.ebuild b/app-forensics/volatility/volatility-2.4.1.ebuild
index c8a3f592e56..5e8485be14a 100644
--- a/app-forensics/volatility/volatility-2.4.1.ebuild
+++ b/app-forensics/volatility/volatility-2.4.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=5
@@ -7,9 +7,9 @@ PYTHON_COMPAT=( python2_7 )
 inherit distutils-r1
 
 DESCRIPTION="Framework for analyzing volatile memory"
-HOMEPAGE="http://www.volatilityfoundation.org/"
+HOMEPAGE="https://www.volatilityfoundation.org/"
 #2.4.1 not on mirrors yet
-#SRC_URI="http://downloads.volatilityfoundation.org/releases/${PV}/${P}.tar.gz"
+#SRC_URI="https://downloads.volatilityfoundation.org/releases/${PV}/${P}.tar.gz"
 SRC_URI="mirror://gentoo/${P}.tar.gz"
 
 LICENSE="GPL-2+"

diff --git a/app-forensics/volatility/volatility-2.6.ebuild b/app-forensics/volatility/volatility-2.6.ebuild
index 74668be6464..fa24d21da65 100644
--- a/app-forensics/volatility/volatility-2.6.ebuild
+++ b/app-forensics/volatility/volatility-2.6.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=5
@@ -7,8 +7,8 @@ PYTHON_COMPAT=( python2_7 )
 inherit distutils-r1
 
 DESCRIPTION="Framework for analyzing volatile memory"
-HOMEPAGE="http://www.volatilityfoundation.org/"
-SRC_URI="http://downloads.volatilityfoundation.org/releases/${PV}/${P}.zip"
+HOMEPAGE="https://www.volatilityfoundation.org/"
+SRC_URI="https://downloads.volatilityfoundation.org/releases/${PV}/${P}.zip"
 
 LICENSE="GPL-2+"
 SLOT="0"


             reply	other threads:[~2018-08-07 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 22:27 Patrice Clement [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-23  8:51 [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility/ David Seifert
2018-08-07 22:27 Patrice Clement
2017-08-23 17:10 Michał Górny
2017-08-11 17:38 Michał Górny
2017-03-06 13:10 Chí-Thanh Christopher Nguyễn

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=1533678060.40dff0ee6efd2ae97c6a3f162de5a5f3994078a0.monsieurp@gentoo \
    --to=monsieurp@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