Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-aiohttp: add aiosignal runtime dependency
Date: Wed, 26 Jan 2022 19:36:16 +0100	[thread overview]
Message-ID: <87sftafiov.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CADvTj4rOqP1pZnp4hz=xb3Y5wBK2eJO7v9EMsd2VGcgRScAu2w@mail.gmail.com> (James Hilliard's message of "Wed, 26 Jan 2022 10:44:40 -0700")

>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:

 > On Wed, Jan 26, 2022 at 7:36 AM Peter Korsgaard <peter@korsgaard.com> wrote:
 >> 
 >> >>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
 >> 
 >> > Fixes:
 >> >   File "/usr/lib/python3.10/site-packages/aiohttp/__init__.py", line 6, in <module>
 >> >   File "/usr/lib/python3.10/site-packages/aiohttp/client.py", line 88, in <module>
 >> >   File "/usr/lib/python3.10/site-packages/aiohttp/tracing.py", line 5, in <module>
 >> > ModuleNotFoundError: No module named 'aiosignal'
 >> 
 >> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
 >> 
 >> When was this introduced? Do we need to backport this to 2021.02.x /
 >> 2021.11.x?

 > Looks like it's required for aiohttp v3.8.0 and newer, so we shouldn't
 > need to backport.

Ok, great. It is quite helpful to mention such things in the commit
messages.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-26 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01  0:04 [Buildroot] [PATCH 1/1] package/python-aiohttp: add aiosignal runtime dependency James Hilliard
2022-01-01  9:49 ` Yann E. MORIN
2022-01-26 14:36 ` Peter Korsgaard
2022-01-26 17:44   ` James Hilliard
2022-01-26 18:36     ` Peter Korsgaard [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=87sftafiov.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --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