From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 50854-done@debbugs.gnu.org
Subject: bug#50854: [PATCH 0/2] Make the PyPI importer honor the ‘upstream-name’ package property
Date: Thu, 30 Sep 2021 23:24:12 +0200 [thread overview]
Message-ID: <87h7e121vn.fsf@gnu.org> (raw)
In-Reply-To: <cover.1632772957.git.public@yoctocell.xyz> (Xinglu Chen's message of "Mon, 27 Sep 2021 22:09:21 +0200")
Xinglu Chen <public@yoctocell.xyz> skribis:
> If a PyPI package contains a “-” followed by one or more digits, e.g.,
> “AV-98”, the PyPI importer/updater will think that the digits after the
> “-” is the version of the package, and instead of trying to update
> “AV-98” it will try to update “AV”.
>
> $ ./pre-inst-env guix refresh av-98
> following redirection to `https://pypi.org/pypi/av/json'...
> /home/yoctocell/src/guix/gnu/packages/web-browsers.scm:914:13: av-98 would be upgraded from 1.0.1 to 8.0.3
>
> The first patch makes the PyPI importer honor the ‘upstream-name’
> property; it will also generate a package with an ‘upstream-name’
> property if the package name contains a “-” followed by one or more
> digits.
>
> The second patch sets the ‘upstream-name’ property for the ‘av-98’
> package.
Nice.
> Xinglu Chen (2):
> import: pypi: Honor the 'upstream-name' package property.
> gnu: av-98: Set 'upstream-name' property.
Applied, thanks!
Ludo'.
prev parent reply other threads:[~2021-09-30 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 20:09 [bug#50854] [PATCH 0/2] Make the PyPI importer honor the ‘upstream-name’ package property Xinglu Chen
2021-09-27 20:11 ` [bug#50854] [PATCH 1/2] import: pypi: Honor the 'upstream-name' " Xinglu Chen
2021-09-27 20:11 ` [bug#50854] [PATCH 2/2] gnu: av-98: Set 'upstream-name' property Xinglu Chen
2021-09-30 21:24 ` Ludovic Courtès [this message]
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=87h7e121vn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50854-done@debbugs.gnu.org \
--cc=public@yoctocell.xyz \
/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).