public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/semantic_version/
Date: Wed, 11 May 2022 10:04:02 +0000 (UTC)	[thread overview]
Message-ID: <1652263437.17aec2237ca70136e0ae8014d49b825529cab373.mgorny@gentoo> (raw)

commit:     17aec2237ca70136e0ae8014d49b825529cab373
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed May 11 09:44:53 2022 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed May 11 10:03:57 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=17aec223

dev-python/semantic_version: Fix remote-id

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/semantic_version/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/semantic_version/metadata.xml b/dev-python/semantic_version/metadata.xml
index 0036e57a3eda..920bd3fa3a30 100644
--- a/dev-python/semantic_version/metadata.xml
+++ b/dev-python/semantic_version/metadata.xml
@@ -14,7 +14,7 @@
   </longdescription>
   <stabilize-allarches/>
   <upstream>
-    <remote-id type="pypi">semantic_version</remote-id>
+    <remote-id type="pypi">semantic-version</remote-id>
     <remote-id type="github">rbarrois/python-semanticversion</remote-id>
     <bugs-to>https://github.com/rbarrois/python-semanticversion/issues</bugs-to>
   </upstream>


             reply	other threads:[~2022-05-11 10:04 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 10:04 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-29  8:02 [gentoo-commits] repo/gentoo:master commit in: dev-python/semantic_version/ Agostino Sarubbo
2022-07-26  6:32 Michał Górny
2022-06-09  2:43 Sam James
2022-05-31 14:56 Jakov Smolić
2022-05-31 11:05 Jakov Smolić
2022-05-31  9:21 Jakov Smolić
2022-05-31  9:21 Jakov Smolić
2022-05-31  8:54 Agostino Sarubbo
2022-05-31  8:51 Agostino Sarubbo
2022-05-26 18:54 Michał Górny
2022-05-11 10:04 Michał Górny
2022-03-15 14:26 Michał Górny
2022-03-15 13:07 Jakov Smolić
2022-03-08 17:11 Jakov Smolić
2022-02-06 23:23 Michał Górny
2022-02-06 20:13 Michał Górny
2022-02-02  9:55 Michał Górny
2022-02-02  9:55 Michał Górny
2021-05-21 21:05 Michał Górny
2021-05-21 21:05 Michał Górny
2021-05-20 21:37 Michał Górny
2021-05-20 21:37 Michał Górny
2021-01-18 14:52 Sam James
2020-11-14 19:00 Sam James
2020-09-13  9:04 Sam James
2020-09-13  8:59 Sam James
2020-07-30 20:41 Michał Górny
2020-07-30 20:09 Sam James
2020-07-30 19:39 Sam James
2020-06-24  7:07 Michał Górny
2020-06-24  7:07 Michał Górny
2020-02-11 11:42 Alexey Shvetsov
2020-02-06  5:59 Michał Górny
2020-02-05 21:28 Andreas Sturmlechner
2019-12-03  3:02 Aaron Bauman
2019-10-04 11:14 Alexey Shvetsov
2019-07-12  8:32 Alexey Shvetsov
2018-07-05 19:00 Louis Sautier
2018-07-05 19:00 Louis Sautier
2018-06-25 23:20 Thomas Deutschmann
2018-06-25 10:40 Jason Zaman
2018-06-24 14:22 Pacho Ramos
2017-06-13 17:30 Manuel Rüger
2017-03-26  4:16 Matt Thode
2017-02-27  2:51 Matt Thode
2016-10-08 16:09 Pacho Ramos
2016-02-28  7:08 Matt Thode
2015-11-16 16:26 Agostino Sarubbo
2015-11-16 16:15 Agostino Sarubbo
2015-08-31  3:49 Ian Delaney

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=1652263437.17aec2237ca70136e0ae8014d49b825529cab373.mgorny@gentoo \
    --to=mgorny@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