From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] package/python-bitstring: add missing runtime dependency
Date: Fri, 01 Mar 2024 11:10:39 +0100 [thread overview]
Message-ID: <875xy69s9s.fsf@48ers.dk> (raw)
In-Reply-To: <20240207084503.11109-2-romain.naour@smile.fr> (Romain Naour's message of "Wed, 7 Feb 2024 09:45:03 +0100")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
> python-bitstring require python-bitarray and python-zlib at runtime
> since 4.1.0 release [1][2].
> python-zlib is now needed for the "Experimental support for two 8-bit
> float types" [2].
> Fixes:
> https://gitlab.com/kubu93/buildroot/-/jobs/6114047821
> [1] https://github.com/scott-griffiths/bitstring/releases/tag/bitstring-4.1.0
> [2] https://github.com/scott-griffiths/bitstring/commit/70c8af4d8bef557bc7d96f809d37e2c241587dd0
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> Cc: James Hilliard <james.hilliard1@gmail.com>
> ---
> v2: fix commit log about python-bitstring release (Marcus Hoffmann)
> reproduce the issue on gitlab-ci and update the Fixes tag url.
Committed to 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-01 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 8:45 [Buildroot] [PATCH v2 1/2] package/python-bitarray: new package Romain Naour
2024-02-07 8:45 ` [Buildroot] [PATCH v2 2/2] package/python-bitstring: add missing runtime dependency Romain Naour
2024-02-07 10:01 ` Marcus Hoffmann via buildroot
2024-03-01 10:10 ` Peter Korsgaard [this message]
2024-03-01 10:10 ` [Buildroot] [PATCH v2 1/2] package/python-bitarray: new package Peter Korsgaard
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=875xy69s9s.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=romain.naour@smile.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