Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy J. Peper" <jeremy@jeremypeper.com>
To: buildroot@buildroot.org, Arnout Vandecappelle <arnout@mind.be>
Cc: Christophe Vu-Brugier <cvubrugier@fastmail.fm>,
	James Hilliard <james.hilliard1@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/3] package/targetcli-fb: bump version to 2.1.58
Date: Mon, 18 Mar 2024 10:45:26 -0500	[thread overview]
Message-ID: <15933709.O9o76ZdvQC@earth> (raw)
In-Reply-To: <9df182fa-a743-4df8-a160-9a6341837c19@mind.be>

On Saturday, March 16, 2024 2:21:35 PM CDT Arnout Vandecappelle wrote:
> On 15/03/2024 23:21, Jeremy J. Peper wrote:
> > On Friday, March 15, 2024 3:31:09 PM CDT Arnout Vandecappelle wrote:
> >>    Hi Jeremy,
> >> 
> >> On 12/03/2024 20:35, Jeremy J. Peper wrote:
> >>> bump to latest version because previous version did not work with python
> >>> 3.11 corrected version mismatch with my first submission
> >>> 
> >>    I unfortunately already pushed before I noticed: you shouldn't include
> >> 
> >> "personal comments" or references to the patch history in the commit
> >> message itself - that belongs under the --- line. So it should have
> >> been:
> >> 
> >> package/targetcli-fb: bump version to 2.1.58
> >> 
> >> Bump to latest version because previous version did not work with python
> >> 3.11
> >> 
> >> Signed-off-by: ...
> >> ---
> >> v2: correct version mismatch
> > 
> > Sorry about that, I will endeavour to do that properly in the future.
> 
>   No worries. I made this comment so you could learn.
> 
> >>    And another thing: we've had Python 3.11 for more than a year, so this
> >>    has
> >> 
> >> been broken for quite some time. To make sure we notice in the future, it
> >> would be good to have a runtime test that detects the situation.
> >> 
> >>    Regards,
> >>    Arnout
> > 
> > I believe you are correct, it appears to have been broken for at least the
> > past few stable releases.
> > 
> > Adding the test sounds like a good idea and I'd be interested in setting
> > that up at some point but I'm not sure when I'll get a chance to work
> > through that learning curve.
> 
>   For a Python package, the test is usually quite simple: just import it,
> and if there's a C library linked with it, make sure you make a call into
> the C library. See e.g. support/testing/tests/package/test_python_click.py
> 
>   A slightly more complicated test can import a Python script to do the
> actual test. See e.g. support/testing/tests/package/test_python_gnupg.py
> which runs support/testing/tests/package/sample_python_gnupg.py
> 
> [snip]
> 
> > Are there any other changes that I need to make before this is suitable to
> > be committed?
> 
>   I apparently didn't make my self clear enough: it is already committed
> (that's why I said "I already pushed"). In fact, the entire series is
> committed.
> 
> 
>   Regards,
>   Arnout
> 
> > Thanks again for all your feedback and guidance.
> > -Jeremy

Excellent, is it possible to get this fix added to the next release of 
2024.02.x ?



_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-03-18 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 19:35 [Buildroot] [PATCH v2 1/3] package/targetcli-fb: bump version to 2.1.58 Jeremy J. Peper
2024-03-12 19:35 ` [Buildroot] [PATCH v2 2/3] package/python-configshell-fb: bump version to 1.1.30 Jeremy J. Peper
2024-03-21 21:00   ` Peter Korsgaard
2024-03-12 19:35 ` [Buildroot] [PATCH v2 3/3] package/python-rtslib-fb: 2.1.76 Jeremy J. Peper
2024-03-21 21:01   ` Peter Korsgaard
2024-03-15 20:31 ` [Buildroot] [PATCH v2 1/3] package/targetcli-fb: bump version to 2.1.58 Arnout Vandecappelle via buildroot
2024-03-15 22:21   ` Jeremy J. Peper
2024-03-16 19:21     ` Arnout Vandecappelle via buildroot
2024-03-18 15:45       ` Jeremy J. Peper [this message]
2024-03-21 20:59         ` 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=15933709.O9o76ZdvQC@earth \
    --to=jeremy@jeremypeper.com \
    --cc=arnout@mind.be \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=cvubrugier@fastmail.fm \
    --cc=james.hilliard1@gmail.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