public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/fizz/
Date: Sun, 17 Apr 2022 18:13:01 +0000 (UTC)	[thread overview]
Message-ID: <1650134455.803cbb5f620564ce9cb2a47423b2203e9313d1d7.arthurzam@gentoo> (raw)

commit:     803cbb5f620564ce9cb2a47423b2203e9313d1d7
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sat Apr 16 18:40:55 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Apr 16 18:40:55 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=803cbb5f

dev-cpp/fizz: add 2022.04.11.00, drop 2022.03.21.00

Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 dev-cpp/fizz/Manifest                                                 | 2 +-
 dev-cpp/fizz/{fizz-2022.03.21.00.ebuild => fizz-2022.04.11.00.ebuild} | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/dev-cpp/fizz/Manifest b/dev-cpp/fizz/Manifest
index 7e54932b0..d9cf2728e 100644
--- a/dev-cpp/fizz/Manifest
+++ b/dev-cpp/fizz/Manifest
@@ -1 +1 @@
-DIST fizz-2022.03.21.00.tar.gz 581670 BLAKE2B 2dc9691abfaf646db56e047a74894b745102764c773b9f244c4b357b74b6d00d1a2548664a5e343f2c5f84458de36d453e99b9901c89bc621c54840a7b45b5e4 SHA512 81a7b764c2c2e17fd5df32a69ecb368eb01df04df6dbd1155a40b68fc39cda4f86ce81afc5c89425a5751ef7f4dbb8a40df8b5095685e72ce5e9043c0a74682e
+DIST fizz-2022.04.11.00.tar.gz 591060 BLAKE2B 5d773af07c70244f54b46927cf28677ef7eb7a9a822a47d497c0ddc9ee4abac34a13462cbcae5372dae5bb3370b7eafc3528c3b63c7b50c564d88c59d6a878f9 SHA512 94278ccda36c0781512a3f9245637573891c8b51d35e5b991d62aad86f2883a9a85406e004e88fd342f0a4020365a19e068ba975e0bf826bf7c360916862a1c8

diff --git a/dev-cpp/fizz/fizz-2022.03.21.00.ebuild b/dev-cpp/fizz/fizz-2022.04.11.00.ebuild
similarity index 93%
rename from dev-cpp/fizz/fizz-2022.03.21.00.ebuild
rename to dev-cpp/fizz/fizz-2022.04.11.00.ebuild
index 12e7ec567..0c689e15b 100644
--- a/dev-cpp/fizz/fizz-2022.03.21.00.ebuild
+++ b/dev-cpp/fizz/fizz-2022.04.11.00.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2021 Gentoo Authors
+# Copyright 2021-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -24,7 +24,6 @@ RDEPEND="
 	dev-libs/libsodium
 	dev-libs/openssl:0=
 "
-#TODO: discover if gtest is linked
 DEPEND="
 	${RDEPEND}
 	test? ( <dev-cpp/gtest-1.11.0 )


             reply	other threads:[~2022-04-17 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 18:13 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15 15:45 [gentoo-commits] repo/proj/guru:dev commit in: dev-cpp/fizz/ Julien Roy
2024-05-15 16:06 ` [gentoo-commits] repo/proj/guru:master " Julien Roy
2022-03-07 21:21 Ronny Gutbrod
2021-10-27  6:18 Florian Schmaus
2021-10-27  6:18 Florian Schmaus
2021-10-25 11:56 Andrew Ammerlaan
2021-10-25 11:56 Andrew Ammerlaan
2021-10-06  1:13 Theo Anderson
2021-07-05 15:48 Haelwenn Monnier
2021-06-17  5:55 Theo Anderson
2021-05-28 10:28 Andrew Ammerlaan
2021-05-05  8:33 Andrew Ammerlaan
2021-04-29  8:23 Michał Górny

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=1650134455.803cbb5f620564ce9cb2a47423b2203e9313d1d7.arthurzam@gentoo \
    --to=arthurzam@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