|
From: | Peter Polidoro |
Subject: | [bug#54737] gnu: python-multipart: Update to 0.2.4. |
Date: | Mon, 01 Aug 2022 13:35:35 -0400 |
User-agent: | mu4e 1.8.7; emacs 28.1 |
You can close this, thank you for catching my error. I apologize for the confusion and for your time.
Peter Polidoro <peter@polidoro.io> writes:
[1. text/plain]Hi. Good catch. I may have made a mistake when choosing between these two unfortunately named pypi packages. I need one of these two as a dependency for another Guix package. I am traveling at the moment, but I will double check this when I return in a few days. If I do need multipart instead of python-multipart, perhaps there is a better way to name the Guix packages to cause less confusion.Thanks!On Jul 29, 2022, at 3:38 PM, Maxime Devos <maximedevos@telenet.be> wrote:(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 ora typosquatting attack. Greetings, Maxime.[2. application/pgp-keys; OpenPGP_0x49E3EE22191725EE.asc]... [3. application/octet-stream; OpenPGP_signature]...
[Prev in Thread] | Current Thread | [Next in Thread] |