From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-web2py: bump to version 3.3.3
Date: Fri, 30 Oct 2026 21:26:57 +0100 [thread overview]
Message-ID: <c3957c004d011e7f2f9bfe4924dd340d@free.fr> (raw)
In-Reply-To: <20261030115313.3112716-1-angelo.compagnucci@gmail.com>
Hi Angelo,
Thanks for the patch.
On 30/10/2026 12:53, Angelo Compagnucci wrote:
> Release notes:
> https://github.com/web2py/web2py/releases/tag/v3.3.3
This release note link does not provide much useful information.
Could you change it to an actual change description, please?
If there is no change summary, you can put for example:
https://github.com/web2py/web2py/compare/v3.1.1...v3.3.3
>
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> ---
> package/python-web2py/python-web2py.hash | 2 +-
> package/python-web2py/python-web2py.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/python-web2py/python-web2py.hash
> b/package/python-web2py/python-web2py.hash
> index b100a1fec8..fd16d50cc9 100644
> --- a/package/python-web2py/python-web2py.hash
> +++ b/package/python-web2py/python-web2py.hash
> @@ -1,3 +1,3 @@
> # sha256 locally computed
> -sha256
> b22b5c2db862cdef9e0feace1c8841741a14eb5e735b674d6ce2bd5c7f4cac64
> python-web2py-v3.1.1-git4.tar.gz
> +sha256
> 68efbfdc26a1b5a2d20bbfec9de522e7fb88d36b73ab7dac24011ae3d51b3380
> python-web2py-v3.3.3-git4.tar.gz
When I tried to download the archive, it failed with the error:
ERROR: while checking hashes from
package/python-web2py/python-web2py.hash
ERROR: python-web2py-v3.3.3-git4.tar.gz has wrong sha256 hash:
ERROR: expected:
68efbfdc26a1b5a2d20bbfec9de522e7fb88d36b73ab7dac24011ae3d51b3380
ERROR: got :
ecd2e9a0728cd469a2e24a6e5896a0b610318c22c2d28f82bb9d68de551ff856
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Could you check where this difference is coming from?
Then, fix the hash, please?
Even when fixing the source hash, the build is then
failing with the error:
AttributeError: module 'hashlib' has no attribute 'pbkdf2_hmac'
Could you have a look, please?
> sha256
> 2aae96826184a492bc799add49aed7b29036e7aba2d2294fb65053bd30fe55fe
> LICENSE.web2py.txt
> diff --git a/package/python-web2py/python-web2py.mk
> b/package/python-web2py/python-web2py.mk
> index 68847a2385..27777e3430 100644
> --- a/package/python-web2py/python-web2py.mk
> +++ b/package/python-web2py/python-web2py.mk
> @@ -4,7 +4,7 @@
> #
>
> ################################################################################
>
> -PYTHON_WEB2PY_VERSION_UPSTREAM = 3.1.1
> +PYTHON_WEB2PY_VERSION_UPSTREAM = 3.3.3
> PYTHON_WEB2PY_VERSION = v$(PYTHON_WEB2PY_VERSION_UPSTREAM)
> PYTHON_WEB2PY_SITE = https://github.com/web2py/web2py.git
> PYTHON_WEB2PY_SITE_METHOD = git
> --
> 2.34.1
Could you send an updated patch addressing those comments, please?
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-30 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 11:53 [Buildroot] [PATCH] package/python-web2py: bump to version 3.3.3 Angelo Compagnucci
2026-10-30 20:26 ` Julien Olivain via buildroot [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3957c004d011e7f2f9bfe4924dd340d@free.fr \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=ju.o@free.fr \
/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