public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/
Date: Tue, 13 Aug 2024 07:36:33 +0000 (UTC)	[thread overview]
Message-ID: <1723534585.6ab3ec62f93cd1de812762a5f15f3a88dca0d17d.juippis@gentoo> (raw)

commit:     6ab3ec62f93cd1de812762a5f15f3a88dca0d17d
Author:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 13 07:23:32 2024 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Tue Aug 13 07:36:25 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6ab3ec62

dev-libs/libsecp256k1: fix VariableOrderWrong

Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 dev-libs/libsecp256k1/libsecp256k1-0.5.1.ebuild | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dev-libs/libsecp256k1/libsecp256k1-0.5.1.ebuild b/dev-libs/libsecp256k1/libsecp256k1-0.5.1.ebuild
index 92bfd82bdf47..f048f1b97499 100644
--- a/dev-libs/libsecp256k1/libsecp256k1-0.5.1.ebuild
+++ b/dev-libs/libsecp256k1/libsecp256k1-0.5.1.ebuild
@@ -9,6 +9,7 @@ MyPN=secp256k1
 DESCRIPTION="Optimized C library for EC operations on curve secp256k1"
 HOMEPAGE="https://github.com/bitcoin-core/secp256k1"
 SRC_URI="https://github.com/bitcoin-core/secp256k1/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+S="${WORKDIR}/${MyPN}-${PV}"
 
 LICENSE="MIT"
 SLOT="0/2"  # subslot is "$((_LIB_VERSION_CURRENT-_LIB_VERSION_AGE))" from configure.ac
@@ -30,8 +31,6 @@ PATCHES=(
 	"${FILESDIR}/0.4.0-fix-cross-compile.patch"
 )
 
-S="${WORKDIR}/${MyPN}-${PV}"
-
 src_prepare() {
 	default
 	eautoreconf


             reply	other threads:[~2024-08-13  7:36 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  7:36 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-23  1:42 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/ Sam James
2025-08-22  4:03 Sam James
2025-08-22  4:03 Sam James
2025-08-22  4:03 Sam James
2025-07-23  2:32 Sam James
2024-12-10 15:25 Sam James
2024-12-10 15:22 Sam James
2024-12-10 15:22 Sam James
2024-12-10 14:37 Arthur Zamarin
2024-12-01 11:51 Sam James
2024-11-09 13:24 Arthur Zamarin
2024-11-09 13:24 Arthur Zamarin
2024-11-09  9:58 Arthur Zamarin
2024-11-09  9:02 Arthur Zamarin
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:06 Sam James
2024-11-07  7:46 Sam James
2024-11-06 14:28 Sam James
2024-11-06 14:28 Sam James
2024-11-06 10:57 Sam James
2024-10-12  7:52 Michał Górny
2024-10-11  0:24 Sam James
2024-10-10  6:54 Arthur Zamarin
2024-08-25 15:24 Andreas K. Hüttel
2024-08-13  7:36 Joonas Niilola
2024-05-08 20:48 Florian Schmaus
2024-05-08 20:48 Florian Schmaus
2024-01-21 17:09 Sam James
2023-10-24  9:14 Joonas Niilola
2023-10-24  9:14 Joonas Niilola
2023-09-18  9:01 Sam James
2023-05-14 17:11 Sam James
2023-05-14  7:51 Sam James
2023-04-11  4:07 Sam James
2023-03-13 18:07 Sam James
2023-03-13 18:07 Sam James
2023-01-07  7:41 Sam James
2023-01-07  7:41 Sam James
2023-01-07  7:41 Sam James
2023-01-07  7:41 Sam James
2023-01-06 12:43 Sam James
2021-05-28  3:17 Sam James
2021-05-28  2:27 Sam James
2021-02-07  9:03 Joonas Niilola
2021-02-07  9:03 Joonas Niilola
2021-01-21 23:41 Sam James
2020-08-30 17:14 Thomas Deutschmann
2020-08-29 13:23 Sam James
2020-05-01 15:09 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-01-11 21:38 Craig Andrews
2017-01-05 14:12 Anthony G. Basile
2016-12-20  9:08 Agostino Sarubbo
2016-12-19 19:56 Tobias Klausmann
2016-06-26  0:09 Anthony G. Basile
2016-03-20 15:42 Anthony G. Basile

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=1723534585.6ab3ec62f93cd1de812762a5f15f3a88dca0d17d.juippis@gentoo \
    --to=juippis@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