public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_perl/
Date: Wed,  8 Feb 2017 00:41:42 +0000 (UTC)	[thread overview]
Message-ID: <1486514497.3d44e2d5ebd9837924b766627ab58d55cec43afa.robbat2@gentoo> (raw)

commit:     3d44e2d5ebd9837924b766627ab58d55cec43afa
Author:     Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
AuthorDate: Wed Feb  8 00:39:17 2017 +0000
Commit:     Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
CommitDate: Wed Feb  8 00:41:37 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d44e2d5

www-apache/mod_perl: missing DEPEND

mod_perl needs the APR_ECRYPT header definition which was introduced in
apr-util-1.4.x. Any box with only apr-util-1.3.x would fail to compile
otherwise. Compile failure found during infra upgrades, as nothing else
brought in newer apr-util on old systems.

Package-Manager: portage-2.3.2

 www-apache/mod_perl/mod_perl-2.0.10.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/www-apache/mod_perl/mod_perl-2.0.10.ebuild b/www-apache/mod_perl/mod_perl-2.0.10.ebuild
index 000d701..61a70b4 100644
--- a/www-apache/mod_perl/mod_perl-2.0.10.ebuild
+++ b/www-apache/mod_perl/mod_perl-2.0.10.ebuild
@@ -29,6 +29,7 @@ RDEPEND="
 	dev-lang/perl[ithreads=]
 	>=dev-perl/Apache-Test-1.400.0
 	>=www-servers/apache-2.0.47
+	>=dev-libs/apr-util-1.4
 	!ithreads? ( www-servers/apache[-apache2_mpms_event,-apache2_mpms_worker,apache2_mpms_prefork] )
 "
 DEPEND="${RDEPEND}


             reply	other threads:[~2017-02-08  0:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  0:41 Robin H. Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-27 17:55 [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_perl/ Arthur Zamarin
2024-05-07  7:57 Andreas K. Hüttel
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2023-11-13  4:35 Sam James
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-07-05  1:25 Sam James
2022-08-26 10:46 Sam James
2020-06-13 21:09 Matt Turner
2020-05-11 16:49 Agostino Sarubbo
2020-05-06  6:28 Agostino Sarubbo
2020-05-05  6:46 Agostino Sarubbo
2020-05-04 16:56 Agostino Sarubbo
2020-03-17  9:44 Andreas K. Hüttel
2018-12-22 12:46 Andreas K. Hüttel
2018-07-23  8:15 Christian Ruppert
2017-04-30  9:37 Agostino Sarubbo
2017-04-19 21:32 Andreas Hüttel
2017-03-31  8:41 Michael Weber
2017-02-02  0:06 Kent Fredric
2017-01-20 23:38 Andreas Hüttel
2017-01-14 13:52 Andreas Hüttel
2017-01-10  8:23 Aaron Bauman
2016-12-21 21:34 Thomas Deutschmann
2016-12-05 15:54 Tobias Klausmann
2016-11-25  8:44 Tobias Klausmann
2016-10-28 23:50 Andreas Hüttel
2016-10-21 23:28 Andreas Hüttel
2016-10-08 12:45 Patrice Clement
2016-10-01 18:11 Andreas Hüttel
2016-08-26  9:28 Pacho Ramos
2016-05-23 11:42 Tobias Klausmann
2016-03-07 12:54 Agostino Sarubbo
2016-01-22 17:38 Andreas Hüttel
2016-01-22  0:02 Andreas Hüttel
2016-01-09 19:31 Andreas Hüttel
2016-01-09 19:30 Andreas Hüttel
2015-11-22  8:02 Markus Meier

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=1486514497.3d44e2d5ebd9837924b766627ab58d55cec43afa.robbat2@gentoo \
    --to=robbat2@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