public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/solo-python/
Date: Fri, 30 Apr 2021 14:40:13 +0000 (UTC)	[thread overview]
Message-ID: <1619793538.59db0a9dc0377faf9ca66e7b5ebec3026dc67f8c.marecki@gentoo> (raw)

commit:     59db0a9dc0377faf9ca66e7b5ebec3026dc67f8c
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 30 14:38:58 2021 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Fri Apr 30 14:38:58 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=59db0a9d

sys-auth/solo-python: add 0.0.30, drop 0.0.28

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 sys-auth/solo-python/Manifest                                           | 2 +-
 .../{solo-python-0.0.28.ebuild => solo-python-0.0.30.ebuild}            | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-auth/solo-python/Manifest b/sys-auth/solo-python/Manifest
index b6b4d04bb6b..fee539b663c 100644
--- a/sys-auth/solo-python/Manifest
+++ b/sys-auth/solo-python/Manifest
@@ -1,2 +1,2 @@
 DIST solo-python-0.0.27.tar.gz 35657 BLAKE2B 747d8849ad4bdda7c0e4b079dce2d7162f07dad4784bb941242dd8ea759cccd763537cec2c7cd9ecf6f467c771729217648b72aa36292622f5fc3adb8a0c280c SHA512 50d564916e07a0c65a843bd2d0328a735ba71eadcfc893b13fac84a3e51822ed2bf80fc3f7662943a5635c6cd6b3ded8ba5b5a9ac2282c9f9bcdfe9de191e445
-DIST solo-python-0.0.28.tar.gz 34818 BLAKE2B 788d71d2641848c0e01640a87c4b20462ba3380a9005a9ab2d4452575bd4ddb560e677538a4ba42e24f9b7f282b0f7a03ce151e2823d3613ff4f93d00bc20524 SHA512 f0af3c350554fc9724f7130566019fc0b0292cbdb9035a9afa602df12e655f63b03f966605bd4b29ee5c07b0b421e9515b7ec612411d4423940461628843716f
+DIST solo-python-0.0.30.tar.gz 34932 BLAKE2B 6787d9c6e102cd2cb5579be0cb3ffbbe76b3ae90f4fa6891b6a1ca3e76436568a949daa6796fc17c9868d10d5de3b0dd377619936eccb0d436a284a35efa40a9 SHA512 bba63e598ef585ef49e98f3ec2a79911cf8af3fc38c9407bd91b7500dc55bf84f365664e6f80ff0ed3553ce93f5d61ba11c5301e8b36d6000c7a922857adaa5e

diff --git a/sys-auth/solo-python/solo-python-0.0.28.ebuild b/sys-auth/solo-python/solo-python-0.0.30.ebuild
similarity index 100%
rename from sys-auth/solo-python/solo-python-0.0.28.ebuild
rename to sys-auth/solo-python/solo-python-0.0.30.ebuild


             reply	other threads:[~2021-04-30 14:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 14:40 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-20 15:25 [gentoo-commits] repo/gentoo:master commit in: sys-auth/solo-python/ Marek Szuba
2022-04-20  6:41 Jakov Smolić
2022-03-15 11:20 Marek Szuba
2022-03-15 11:20 Marek Szuba
2021-12-16 10:16 Marek Szuba
2021-12-15 13:40 Jakov Smolić
2021-11-13 23:48 Marek Szuba
2021-11-13 23:48 Marek Szuba
2021-08-01 22:07 Marek Szuba
2021-05-31 21:08 Marek Szuba
2021-05-31 11:40 Sam James
2021-05-31  8:51 Marek Szuba
2021-05-27 15:37 Marek Szuba
2021-04-26 10:56 Marek Szuba
2021-04-26 10:56 Marek Szuba
2021-03-12 15:25 Sam James
2021-03-09 14:52 Marek Szuba
2021-01-22 16:53 Agostino Sarubbo
2021-01-22 10:47 Marek Szuba
2020-12-03 16:53 Marek Szuba
2020-09-16 20:42 Marek Szuba

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=1619793538.59db0a9dc0377faf9ca66e7b5ebec3026dc67f8c.marecki@gentoo \
    --to=marecki@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