mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Lars Pedersen <lapeddk@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] python3-urllib3 version 2.2.2 broken
Date: Sun, 27 Oct 2024 15:09:08 +0100	[thread overview]
Message-ID: <Zx5JhLO1hfSYlmlU@pengutronix.de> (raw)
In-Reply-To: <CAKd8=Gu75TqGcoMYG=CY-n-w33xFKYo_VDZtcd10=-=rYc1BUQ@mail.gmail.com>

Hi,

On Sun, Oct 27, 2024 at 01:45:36PM +0100, Lars Pedersen wrote:
> I have got patch set to get hatchling and python3-urllib working. I'll
> try to send it on Tuesday.

Right, I may revert the package for the November release instead. I'm not
sure yet. It depends a bit in the timing.

> On a side note. Can anyone explain the difference been "host" and
> host-system" package definition?

For Python packages that is a bit fuzzy. In general, 'host-system' means
that PTXdist does not actually built the package, but simply check that the
relevant stuff is available on the build host. The 'host' packages are
actually built by PTXdist.

For Python, things are a bit more complex. 'host-python3' and all
'host-python3-*' packages are there for one specific use-case: To build the
target Python.

'host-system-python3' ensures that Python 3.x is available on the build
host, so it can be used by build scripts written in Python.
At some point, it also checked to ensure that all required Python modules
are also available. But with the growing number of such required modules,
that became unfeasible.
So now, 'host-system-python3-*' are packages that use the Python from the
build host but are built by PTXdist and installed into a virtualenv.

Regards,
Michael

> On Fri, 25 Oct 2024 at 14:17, Lars Pedersen <lapeddk@gmail.com> wrote:
> >
> > python3-urllib3 is broken after the 1.26.6 -> 2.2.2 version bump.
> > Version 2.2.2 requires hatchling as build backend.
> >
> > ptxdist is still able to compile a half built package that could be
> > imported in python on target,
> >
> > /Lars Pedersen
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2024-10-27 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 12:17 Lars Pedersen
2024-10-27 12:45 ` Lars Pedersen
2024-10-27 14:09   ` Michael Olbrich [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=Zx5JhLO1hfSYlmlU@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=lapeddk@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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