public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/lrzip/
Date: Sat, 17 Jul 2021 19:41:26 +0000 (UTC)	[thread overview]
Message-ID: <1626550763.5e64f414a64336e01044ef70c079a0de019bd757.dilfridge@gentoo> (raw)

commit:     5e64f414a64336e01044ef70c079a0de019bd757
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 17 19:39:23 2021 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Jul 17 19:39:23 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e64f414

app-arch/lrzip: virtual/perl-Pod-Parser -> dev-perl/Pod-Parser

Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 app-arch/lrzip/{lrzip-0.641.ebuild => lrzip-0.641-r1.ebuild} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-arch/lrzip/lrzip-0.641.ebuild b/app-arch/lrzip/lrzip-0.641-r1.ebuild
similarity index 97%
rename from app-arch/lrzip/lrzip-0.641.ebuild
rename to app-arch/lrzip/lrzip-0.641-r1.ebuild
index a89029b177f..6c8ec1c9d02 100644
--- a/app-arch/lrzip/lrzip-0.641.ebuild
+++ b/app-arch/lrzip/lrzip-0.641-r1.ebuild
@@ -22,7 +22,7 @@ RDEPEND="
 "
 DEPEND="
 	${RDEPEND}
-	virtual/perl-Pod-Parser
+	dev-perl/Pod-Parser
 	x86? ( dev-lang/nasm )
 "
 


             reply	other threads:[~2021-07-17 19:41 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 19:41 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-26 20:17 [gentoo-commits] repo/gentoo:master commit in: app-arch/lrzip/ Ionen Wolkens
2024-02-25  0:01 Joshua Kinard
2024-02-17 12:26 Jakov Smolić
2022-11-23  7:53 WANG Xuerui
2022-04-14  8:10 Agostino Sarubbo
2022-04-10 17:38 Arthur Zamarin
2022-04-10 17:38 Arthur Zamarin
2022-04-09 20:02 Arthur Zamarin
2022-04-09 19:41 Arthur Zamarin
2022-04-07 20:58 Jakov Smolić
2022-04-07 20:58 Jakov Smolić
2022-03-11 11:01 Sam James
2022-03-02  2:31 Sam James
2021-12-19 12:13 Stephan Hartmann
2021-12-19 11:58 Sam James
2021-07-17 19:41 Andreas K. Hüttel
2021-04-14 22:07 Sam James
2021-04-14 16:26 Sam James
2021-04-14 16:25 Sam James
2021-04-14 16:24 Sam James
2021-04-14 16:23 Sam James
2021-04-14 16:23 Sam James
2021-04-13 18:43 Sergei Trofimovich
2021-03-07 23:04 Sam James
2021-02-22  7:25 Sam James
2021-01-06 12:52 Fabian Groffen
2020-07-13 18:08 Sam James
2020-03-19 19:09 Thomas Deutschmann
2019-11-11 19:39 Sergei Trofimovich
2019-11-07  0:21 Aaron Bauman
2019-11-01 23:25 Sergei Trofimovich
2019-11-01 10:34 Mikle Kolyada
2019-10-28  9:43 Agostino Sarubbo
2019-10-27 23:20 Thomas Deutschmann
2019-10-26 23:36 Thomas Deutschmann
2019-03-02 23:28 Andreas Sturmlechner
2018-10-14 10:18 Pacho Ramos
2018-10-14 10:18 Pacho Ramos
2018-03-30 18:50 Aaron Bauman
2017-04-08  6:06 Michał Górny
2017-03-03 10:09 Agostino Sarubbo
2016-07-23  6:53 Jeroen Roovers
2016-07-06 16:52 Amy Winston
2016-06-23 18:36 Michael Palimaka
2016-06-17 15:13 Patrice Clement
2016-06-17 14:53 Patrice Clement
2016-06-10 15:32 Agostino Sarubbo
2016-06-08 19:38 Markus Meier
2016-05-28 10:52 Pacho Ramos

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=1626550763.5e64f414a64336e01044ef70c079a0de019bd757.dilfridge@gentoo \
    --to=dilfridge@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