From: Maxime Devos <maximedevos@telenet.be>
To: Peter Polidoro <peter@polidoro.io>, 54737@debbugs.gnu.org
Subject: [bug#54737] gnu: python-multipart: Update to 0.2.4.
Date: Fri, 29 Jul 2022 21:38:04 +0200 [thread overview]
Message-ID: <47dff1cb-3dc9-4c2b-a64f-2cd4df6f2365@telenet.be> (raw)
In-Reply-To: <86h777wcfg.fsf@polidoro.io>
[-- Attachment #1.1.1: Type: text/plain, Size: 986 bytes --]
> (define-public python-multipart
> (package
> (name "python-multipart")
> - (version "0.0.5")
> - (source (origin
> - (method url-fetch)
> - (uri (pypi-uri "python-multipart" version))
> - (sha256
> - (base32
> - "0hzshd665rl1bkwvaj9va4j3gs8nmb478fbvligx20663xhmzfzp"))))
> + (version "0.2.4")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (pypi-uri "multipart" version))
> + (sha256
> + (base32
> "1jr24lm931pkh4x0amr19w5qknrckcg4z3k1zvz9cw5wc19j1fh6"))))
What's the reason for changing from the python-multipart to multipart?
I've looked at the home page and the pypi page, and it doesn't state
that the latter is a successor of the former, so these look like
unrelated projects or a typosquatting attack.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-29 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 19:34 [bug#54737] gnu: python-multipart: Update to 0.2.4 Peter Polidoro
2022-07-29 19:38 ` Maxime Devos [this message]
2022-07-30 12:19 ` Peter Polidoro
2022-08-01 17:35 ` Peter Polidoro
2022-08-01 17:59 ` ( via Guix-patches via
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=47dff1cb-3dc9-4c2b-a64f-2cd4df6f2365@telenet.be \
--to=maximedevos@telenet.be \
--cc=54737@debbugs.gnu.org \
--cc=peter@polidoro.io \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.