From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: buildroot@buildroot.org
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Julien Olivain <ju.o@free.fr>
Subject: [Buildroot] [PATCH v3 2/2] package/python-snappy: bump version to 0.7.2
Date: Fri, 24 Jul 2026 09:50:03 +0300 [thread overview]
Message-ID: <20260724065004.217411-2-flaviu.nistor@gmail.com> (raw)
In-Reply-To: <20260724065004.217411-1-flaviu.nistor@gmail.com>
Even if there is a 0.7.3 on Pypi, there is no 0.7.3 release
on the project homepage, hence the bump to 0.7.2.
Since 0.7.0 is switched from snappy library to cramjam so
update the PYTHON_SNAPPY_DEPENDENCIES.
Add also PYTHON_SNAPPY_SOURCE for correct package on Pypi.
Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
---
Changes in v3:
- Add new package cramjam and to fix error indicated by Julien Olivain.
- Link to v2: https://lore.kernel.org/all/20260717061943.4491-1-flaviu.nistor@gmail.com/
Changes in v2:
- Fix error indicated by Julien Olivain when running make python-snappy-legal-info.
- Link to v1: https://lore.kernel.org/all/20260409152520.5894-1-flaviu.nistor@gmail.com/
package/python-snappy/Config.in | 1 +
package/python-snappy/python-snappy.hash | 4 ++--
package/python-snappy/python-snappy.mk | 7 ++++---
3 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/package/python-snappy/Config.in b/package/python-snappy/Config.in
index fd7f84050f..2853e4331c 100644
--- a/package/python-snappy/Config.in
+++ b/package/python-snappy/Config.in
@@ -1,6 +1,7 @@
config BR2_PACKAGE_PYTHON_SNAPPY
bool "python-snappy"
depends on BR2_INSTALL_LIBSTDCPP # snappy
+ select BR2_PACKAGE_PYTHON_CRAMJAM
select BR2_PACKAGE_SNAPPY
help
Python library for the snappy compression library from
diff --git a/package/python-snappy/python-snappy.hash b/package/python-snappy/python-snappy.hash
index c4dbc72077..2f40b6c531 100644
--- a/package/python-snappy/python-snappy.hash
+++ b/package/python-snappy/python-snappy.hash
@@ -1,5 +1,5 @@
# md5, sha256 from https://pypi.org/pypi/python-snappy/json
-md5 fc84cfa3526fba06d66f0d0b2e764300 python-snappy-0.6.1.tar.gz
-sha256 b6a107ab06206acc5359d4c5632bd9b22d448702a79b3169b0c62e0fb808bb2a python-snappy-0.6.1.tar.gz
+md5 04a4e58b0a932403bb285900e67c778d python_snappy-0.7.2.tar.gz
+sha256 04bf182f9d9f67b7a846dae2f1df36180ceeee8d3380e4b6799deff5272c4978 python_snappy-0.7.2.tar.gz
# Locally computed sha256 checksums
sha256 d007cb05f143d99d16d5cd0d1bf291daf037adb36800344e440ec26edb938f9a LICENSE
diff --git a/package/python-snappy/python-snappy.mk b/package/python-snappy/python-snappy.mk
index e80aa861df..5d34b6d493 100644
--- a/package/python-snappy/python-snappy.mk
+++ b/package/python-snappy/python-snappy.mk
@@ -4,11 +4,12 @@
#
################################################################################
-PYTHON_SNAPPY_VERSION = 0.6.1
-PYTHON_SNAPPY_SITE = https://files.pythonhosted.org/packages/98/7a/44a24bad98335b2c72e4cadcdecf79f50197d1bab9f22f863a274f104b96
+PYTHON_SNAPPY_VERSION = 0.7.2
+PYTHON_SNAPPY_SOURCE = python_snappy-$(PYTHON_SNAPPY_VERSION).tar.gz
+PYTHON_SNAPPY_SITE = https://files.pythonhosted.org/packages/cb/52/acd87583175fa930e4385f8a6164eb5909acd683c0e62ee01d41de8195a2
PYTHON_SNAPPY_SETUP_TYPE = setuptools
PYTHON_SNAPPY_LICENSE = BSD-3-Clause
PYTHON_SNAPPY_LICENSE_FILES = LICENSE
-PYTHON_SNAPPY_DEPENDENCIES = snappy
+PYTHON_SNAPPY_DEPENDENCIES = host-python-cramjam python-cramjam
$(eval $(python-package))
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-24 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 6:50 [Buildroot] [PATCH v3 1/2] package/python-cramjam: new package Flaviu Nistor
2026-07-24 6:50 ` Flaviu Nistor [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=20260724065004.217411-2-flaviu.nistor@gmail.com \
--to=flaviu.nistor@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@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