All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hongxu" <hongxu.jia@eng.windriver.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH 3/4] python3-propcache: support reproducible
Date: Fri, 19 Sep 2025 17:01:03 -0700	[thread overview]
Message-ID: <19647.1758326463539423995@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sqJm2aZsrinVihyfHnZ74D1JznhzhGYqanZkwobLJBZpA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

On Fri, Sep 19, 2025 at 12:25 PM, Khem Raj wrote:

> 
> 
>> +SRC_URI += " \
>> + file://0001-build-wheel-in-place.patch \
>> +"
> 
> This patch file is missing

The patch locates in meta-python/recipes-devtools/python/files/0001-build-wheel-in-place.patch
which shared with [meta-python][PATCH 2/4] python3-frozenlist: support reproducible [1]

[1] https://lists.openembedded.org/g/openembedded-devel/message/119531?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3ACreated%2C%2Csupport+reproducible%2C20%2C2%2C0%2C115306109

//Hongxu

> 
> 
>> +
>> DEPENDS += " \
>> python3-expandvars-native \
>> "
> 
>

[-- Attachment #2: Type: text/html, Size: 3089 bytes --]

  reply	other threads:[~2025-09-20  0:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  7:15 [meta-python][PATCH 1/4] python3-pyzmq: set cmake build dir to support reproducible Hongxu Jia
2025-09-18  7:15 ` [meta-python][PATCH 2/4] python3-frozenlist: " Hongxu Jia
2025-09-19  4:01   ` [oe] " Khem Raj
2025-09-21  2:34     ` hongxu
2025-09-18  7:15 ` [meta-python][PATCH 3/4] python3-propcache: " Hongxu Jia
2025-09-19 19:24   ` [oe] " Khem Raj
2025-09-20  0:01     ` hongxu [this message]
2025-09-20  0:06       ` Khem Raj
2025-09-18  7:15 ` [meta-python][PATCH 4/4] python3-yarl: " Hongxu Jia
2025-09-19 19:24   ` [oe] " Khem Raj
2025-09-20  0:01     ` hongxu
2025-09-20  0:01     ` hongxu

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=19647.1758326463539423995@lists.openembedded.org \
    --to=hongxu.jia@eng.windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.