public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/gherkin-official/
Date: Mon, 17 Feb 2025 12:32:57 +0000 (UTC)	[thread overview]
Message-ID: <1739795509.feebfb5ec46b9e9551028b24a17ee620344472e3.ionen@gentoo> (raw)

commit:     feebfb5ec46b9e9551028b24a17ee620344472e3
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 17 12:31:45 2025 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Mon Feb 17 12:31:49 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=feebfb5e

dev-python/gherkin-official: add 32.0.0, drop 31.0.0

No code changes, but it was added to pypi anyway.

Bump just for the sake of the version number.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-python/gherkin-official/Manifest                                    | 2 +-
 .../{gherkin-official-31.0.0.ebuild => gherkin-official-32.0.0.ebuild}  | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/gherkin-official/Manifest b/dev-python/gherkin-official/Manifest
index b5611d4e9385..f281d3ecfa4c 100644
--- a/dev-python/gherkin-official/Manifest
+++ b/dev-python/gherkin-official/Manifest
@@ -1,2 +1,2 @@
 DIST gherkin-30.0.4.gh.tar.gz 3858403 BLAKE2B bdf5cf80f1e06c9e8464d3fbc5a56a594b75f3d8ae6ff13dafcd583aa6571e1a6ba4aa4dd344f7c532174b09829bdaf9aae1e1e02339521e2836dbf9b3014108 SHA512 52cd5bab779e46d5d2c451558b545fb8ac408d1d5d11558e1dace94d77472ca271589eb183c412093fcbdef2574a495fdd11c98ce97d8146077a54b3369a9a6e
-DIST gherkin-31.0.0.gh.tar.gz 3850999 BLAKE2B e38bdd97af5d3a011e2c31e2cc67f25c72a4e729c9af8be4355a4a9155d83b403781f182f05e8db9b10cb929bbd208067ef39433982514bee29afa2aa4d621b4 SHA512 7b512a5ef2d4e840939f6109ff850913052dbb7263d8013a79f3485cc4037a3a2967706e9d8fbb9e7e436863819c89214953f493fa4666a496465fdb20d7c524
+DIST gherkin-32.0.0.gh.tar.gz 3842521 BLAKE2B b0afbf2638bd85817a141e2f89bd81e9ba564c96ddcbfa56f803d7239736864e1047bed6d0fa1a48edb0dac88553b8777e530b6fd06a82d71e4e971105f68020 SHA512 2ce444bde2d1e4ed3f1214205e4dd43cfa21c0f31d5194cfa9da6aeabdf2f0ac70966f1d98617b9d8f3633dadae6b773d67a6f050f0e37ae477c594b0e670aa9

diff --git a/dev-python/gherkin-official/gherkin-official-31.0.0.ebuild b/dev-python/gherkin-official/gherkin-official-32.0.0.ebuild
similarity index 100%
rename from dev-python/gherkin-official/gherkin-official-31.0.0.ebuild
rename to dev-python/gherkin-official/gherkin-official-32.0.0.ebuild


             reply	other threads:[~2025-02-17 12:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 12:32 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 12:42 [gentoo-commits] repo/gentoo:master commit in: dev-python/gherkin-official/ Jakov Smolić
2025-01-30  4:10 Michał Górny
2024-11-30 11:40 Michał Górny
2024-11-15 14:44 Ionen Wolkens
2024-11-15  9:30 Ionen Wolkens
2024-11-15  9:19 Arthur Zamarin
2024-11-15  2:23 Ionen Wolkens

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=1739795509.feebfb5ec46b9e9551028b24a17ee620344472e3.ionen@gentoo \
    --to=ionen@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