public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/zenlib/
Date: Sat, 30 Dec 2023 15:48:33 +0000 (UTC)	[thread overview]
Message-ID: <1703811016.b17d1aff8fff8ad16294496c37214268bc4108ec.davidroman@gentoo> (raw)

commit:     b17d1aff8fff8ad16294496c37214268bc4108ec
Author:     Zen <z <AT> pyl <DOT> onl>
AuthorDate: Fri Dec 29 00:50:16 2023 +0000
Commit:     David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Fri Dec 29 00:50:16 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=b17d1aff

dev-python/zenlib: Bump to 1.3.1 with improved dict checking

Signed-off-by: Zen <z <AT> pyl.onl>

 dev-python/zenlib/Manifest                                     | 2 +-
 dev-python/zenlib/{zenlib-1.3.0.ebuild => zenlib-1.3.1.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/zenlib/Manifest b/dev-python/zenlib/Manifest
index fb6671e045..1df6288515 100644
--- a/dev-python/zenlib/Manifest
+++ b/dev-python/zenlib/Manifest
@@ -1,2 +1,2 @@
 DIST zenlib-1.2.0.tar.gz 12766 BLAKE2B 9366beb9496d136cbf0efc9fd97c6d430b442eae4ede87d85c32e1bee9a17315cab04e0b8f97ad8b8e2b599d2965dc2cd3c57ebe4830ba9abe53adc13825f634 SHA512 e5630a0869cdcbd909ea829f5876057ad1787ae1b63f80f9b1db7deeb80799eef9deac56027291dac55efd1e974b82a737b236189a1d7a8657a215bb866bca91
-DIST zenlib-1.3.0.tar.gz 13412 BLAKE2B 607b1e886892c48f6777fec6814318fecb9038592250417b17b0355309a18300ffdfd91bea416ee258ef328d3cdc037ad92f11107cb8d4d5a9f9a080ceb078b6 SHA512 667d8370c7b88b8ed48ae6554a92f6223f80039cfd58a9967fbf8298b2d0f0efdba4c0c6f20a6d22f8150b188a123f7d02a0d5b26f802beafd0075b879ecdb4a
+DIST zenlib-1.3.1.tar.gz 13470 BLAKE2B 03bd8dce7a46641e60646173607ea6cd574fed58cbfa5d81c4c7f1deabf863a3acd12bdfd3b59fd5fc853762d7320d57613e40d72407216cc3ae1d82f7744789 SHA512 50a6ac2cb26fd74b6e92e3691463ec707259fe27e37af2f2c68a9a1e0c247b789cdf17d5b1f882e02dbca5f0653a4137caab39f3f0380d0b5391efaf41f1312d

diff --git a/dev-python/zenlib/zenlib-1.3.0.ebuild b/dev-python/zenlib/zenlib-1.3.1.ebuild
similarity index 100%
rename from dev-python/zenlib/zenlib-1.3.0.ebuild
rename to dev-python/zenlib/zenlib-1.3.1.ebuild


             reply	other threads:[~2023-12-30 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 15:48 David Roman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-15 19:27 [gentoo-commits] repo/proj/guru:master commit in: dev-python/zenlib/ Andrew Ammerlaan
2024-05-13 17:48 Julien Roy
2024-05-13 17:48 Julien Roy
2024-05-07 23:05 [gentoo-commits] repo/proj/guru:dev " Julien Roy
2024-05-07 23:12 ` [gentoo-commits] repo/proj/guru:master " Julien Roy
2024-05-07  3:54 Rui Huang
2024-05-07  3:54 Rui Huang
2024-04-30 12:22 David Roman
2024-04-28 21:05 David Roman
2024-04-27 18:34 David Roman
2024-04-20 15:12 Julien Roy
2024-04-17 15:11 Arthur Zamarin
2024-03-10 21:26 Haelwenn Monnier
2024-01-22 17:27 David Roman
2024-01-01  3:56 David Roman
2023-12-30 15:48 David Roman
2023-12-23  7:33 Viorel Munteanu
2023-11-24 17:20 David Roman

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=1703811016.b17d1aff8fff8ad16294496c37214268bc4108ec.davidroman@gentoo \
    --to=davidroman96@gmail.com \
    --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