From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: [Buildroot] [PATCH v2 0/2] package/python-web2py: bump to version 3.3.3
Date: Sat, 31 Oct 2026 15:36:15 +0100 [thread overview]
Message-ID: <20261031143617.445438-1-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20261030115313.3112716-1-angelo.compagnucci@gmail.com>
web2py 3.3.3 stores binaries/*.zip with Git LFS, so the archive
generated by the git download method depends on git-lfs being installed
on the build host. This is why the hash didn't match for Julien: without
git-lfs the archive contains the LFS pointers (68efbfdc...), with it the
actual zip files.
v2 downloads the release tag archive with the github helper, which is
the same on every host, and uses the python-pydal, python-yatl and new
python-rocket3 packages instead of the git submodules, which are not
part of that archive.
About the "module 'hashlib' has no attribute 'pbkdf2_hmac'" failure: I
couldn't reproduce it with a clean build, with the admin panel enabled
(the default), which selects BR2_PACKAGE_HOST_PYTHON3_SSL. It may come
from a host-python3 built before python-web2py was enabled, as changing
that option doesn't rebuild host-python3.
Changes v1 -> v2:
- use the comparison between the tags as changelog [Julien]
- download the release tag archive and add the python-rocket3
package, as the git archive hash depended on git-lfs [Julien]
- update the list of files not installed on the target
Angelo Compagnucci (2):
package/python-rocket3: new package
package/python-web2py: bump to version 3.3.3
DEVELOPERS | 1 +
package/Config.in | 1 +
package/python-rocket3/Config.in | 8 +++++
package/python-rocket3/python-rocket3.hash | 5 +++
package/python-rocket3/python-rocket3.mk | 15 ++++++++
package/python-web2py/Config.in | 1 +
package/python-web2py/python-web2py.hash | 2 +-
package/python-web2py/python-web2py.mk | 40 ++++++++++++++++------
8 files changed, 61 insertions(+), 12 deletions(-)
create mode 100644 package/python-rocket3/Config.in
create mode 100644 package/python-rocket3/python-rocket3.hash
create mode 100644 package/python-rocket3/python-rocket3.mk
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-31 14:36 UTC|newest]
Thread overview: 5+ 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
2026-10-31 14:36 ` Angelo Compagnucci [this message]
2026-10-31 14:36 ` [Buildroot] [PATCH v2 1/2] package/python-rocket3: new package Angelo Compagnucci
2026-10-31 14:36 ` [Buildroot] [PATCH v2 2/2] package/python-web2py: bump to version 3.3.3 Angelo Compagnucci
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=20261031143617.445438-1-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox