From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Christophe Vu-Brugier <cvubrugier@fastmail.fm>
Subject: Re: [Buildroot] [PATCH 1/3] package/python-configshell-fb: bump to version 2.0.3
Date: Tue, 13 Oct 2026 23:32:17 +0200 [thread overview]
Message-ID: <as6jQzgKTJylsBJa@windsurf> (raw)
In-Reply-To: <20261013212037.2419515-1-james.hilliard1@gmail.com>
On Tue, Oct 13, 2026 at 03:20:35PM -0600, James Hilliard wrote:
> Switch to hatchling with hatch-vcs and use the PyPI source distribution,
> which includes the version metadata needed by hatch-vcs.
>
> Restore the compatibility symlink omitted from the PyPI archive so the
> wheel continues to provide the configshell_fb module.
>
> Drop the obsolete six and urwid runtime dependencies. Select curses
> explicitly, since it was previously pulled in by urwid.
>
> Update the license hash for the removal of a trailing blank line:
> https://github.com/open-iscsi/configshell-fb/commit/36306fd6f839b66e958d692230ead8d49883abd8
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Could you report to upstream the issue of the missing symlink in the
Pypi archives?
Otherwise: series applied, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-13 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 21:20 [Buildroot] [PATCH 1/3] package/python-configshell-fb: bump to version 2.0.3 James Hilliard
2026-10-13 21:20 ` [Buildroot] [PATCH 2/3] package/python-rtslib-fb: bump to version 2.2.4 James Hilliard
2026-10-13 21:20 ` [Buildroot] [PATCH 3/3] package/targetcli-fb: bump to version 3.0.2 James Hilliard
2026-10-13 21:32 ` Thomas Petazzoni 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=as6jQzgKTJylsBJa@windsurf \
--to=buildroot@buildroot.org \
--cc=cvubrugier@fastmail.fm \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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