From: Marius Bakke <marius@gnu.org>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: 42364@debbugs.gnu.org
Subject: [bug#42364] [PATCH v2] gnu: Add python-robber.
Date: Thu, 30 Jul 2020 00:23:39 +0200 [thread overview]
Message-ID: <87eeouq7tg.fsf@gnu.org> (raw)
In-Reply-To: <20200727082627.wmg4fplswlikpbwp@melmoth>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Tanguy Le Carrour <tanguy@bioneland.org> writes:
> Hi Marius,
>
>
> Le 07/25, Marius Bakke a écrit :
>> Tanguy Le Carrour <tanguy@bioneland.org> writes:
>>
>> > * gnu/packages/python-check.scm (python-robber): New variable.
>>
>> [...]
>>
>> > + ;; The last version tagged in Github (0.1.0) is older than the one on PyPI.
>> > + ;; Reported upstream: <https://github.com/vesln/robber.py/issues/20>.
>>
>> Wow, it's concerning that someone just uploaded a fork on PyPI without
>> notifying the original author, yet reuses the original home page.
>
> He might have tried, but… the original author's email address given on
> PyPI does not exist any more!
Oh, right. That makes sense. :-)
>> Even more so when there are no tags matching the uploaded tarball.
>>
>> I think we should adjust the home page of this package to point to the
>> fork, and maybe add a comment explaining the situation. WDYT?
>
> I've just send a email to the author of the last commit in the second
> repo. Let's see what will happen!
> In the worst case scenario, I can open a claim request on PyPI and fix
> the mess myself. But let's hope I don't have to do that! ^_^'
I hope so too! Meanwhile I think we can take the original patch you
sent, but adjust the home page to that of the fork.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-29 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:28 [bug#42364] [PATCH] gnu: Add python-robber Tanguy Le Carrour
2020-07-21 21:22 ` Marius Bakke
2020-07-22 8:14 ` Tanguy Le Carrour
2020-07-22 8:14 ` [bug#42364] [PATCH v2] " Tanguy Le Carrour
2020-07-25 15:40 ` Marius Bakke
2020-07-27 8:26 ` Tanguy Le Carrour
2020-07-29 22:23 ` Marius Bakke [this message]
2020-07-30 9:40 ` [bug#42364] [PATCH v3] " Tanguy Le Carrour
2020-09-24 15:49 ` bug#42364: " Ludovic Courtès
2020-09-27 13:39 ` [bug#42364] " Tanguy Le Carrour
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeouq7tg.fsf@gnu.org \
--to=marius@gnu.org \
--cc=42364@debbugs.gnu.org \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).