public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/scrypt/
Date: Wed, 22 Nov 2023 17:10:02 +0000 (UTC)	[thread overview]
Message-ID: <1700672943.f346589280ac10c57d6992eff25f1ad9ee262fed.jsmolic@gentoo> (raw)

commit:     f346589280ac10c57d6992eff25f1ad9ee262fed
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 22 17:08:26 2023 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Wed Nov 22 17:09:03 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f3465892

app-crypt/scrypt: drop 1.3.1

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 app-crypt/scrypt/Manifest            |  1 -
 app-crypt/scrypt/scrypt-1.3.1.ebuild | 19 -------------------
 2 files changed, 20 deletions(-)

diff --git a/app-crypt/scrypt/Manifest b/app-crypt/scrypt/Manifest
index 6b44a1a73e92..ef195b690316 100644
--- a/app-crypt/scrypt/Manifest
+++ b/app-crypt/scrypt/Manifest
@@ -1,2 +1 @@
-DIST scrypt-1.3.1.tgz 394516 BLAKE2B 91faa22dc317927b92abe26c5e15cd52c409722716076c7cc502a0c6e4e84ceaaf60222b3ef141c6a209f36084df2d7f45d8f19482aa035c3e2442513c4283d9 SHA512 c76c29463d2a4db6b62283daca80bc4124a6272f37f983d472d44251b98da702f1edb16ad15058a8d0ea320c23bc1486892ab25d367d37ec77c38a55ad7e69fe
 DIST scrypt-1.3.2.tgz 424414 BLAKE2B aac8dc8360652d5d4d3654d47de961eec99675ee20d8507abf1ffb4de0b7bc8f040cd58cabfd5c0b8c2c197b2302206ea2c747aee1f62a2fe3eaa64e108bce6e SHA512 5f2c4f74cec107b08675c5e287c151d633b3a02f12c71d9484ecb14750b3a45b90e2da9dae9090af59346518492aeab01c215961fd592c4f5e5b944f27d9afc7

diff --git a/app-crypt/scrypt/scrypt-1.3.1.ebuild b/app-crypt/scrypt/scrypt-1.3.1.ebuild
deleted file mode 100644
index fd30ce906416..000000000000
--- a/app-crypt/scrypt/scrypt-1.3.1.ebuild
+++ /dev/null
@@ -1,19 +0,0 @@
-# Copyright 1999-2020 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-DESCRIPTION="A simple password-based encryption utility using scrypt key derivation function"
-HOMEPAGE="http://www.tarsnap.com/scrypt.html"
-SRC_URI="http://www.tarsnap.com/scrypt/${P}.tgz"
-
-LICENSE="BSD-2"
-SLOT="0"
-KEYWORDS="amd64 x86"
-
-DOCS=( FORMAT )
-
-src_test() {
-	# There's an empty check target, so can't call default.
-	emake test
-}


             reply	other threads:[~2023-11-22 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 17:10 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-17 12:07 [gentoo-commits] repo/gentoo:master commit in: app-crypt/scrypt/ Sam James
2023-11-17 12:07 Sam James
2023-10-11 21:07 Jakov Smolić
2023-06-30 19:19 Sam James
2020-10-12  9:06 Joonas Niilola
2020-10-09  8:41 Agostino Sarubbo
2020-10-09  8:31 Agostino Sarubbo
2020-09-14 18:29 Sam James
2020-09-14 18:29 Sam James
2020-09-07 14:54 Thomas Deutschmann
2020-06-17 17:00 Joonas Niilola
2020-06-17 17:00 Joonas Niilola
2020-06-17 17:00 Joonas Niilola
2017-02-17 20:18 David Seifert
2017-02-04  1:31 Alon Bar-Lev
2016-06-12 13:41 Alon Bar-Lev
2015-08-25  4:31 Tim Harder

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=1700672943.f346589280ac10c57d6992eff25f1ad9ee262fed.jsmolic@gentoo \
    --to=jsmolic@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