All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: buildroot@buildroot.org,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/python-pydal: needs python xml module at runtime
Date: Mon, 10 Aug 2026 20:31:53 +0200	[thread overview]
Message-ID: <6e608820fd7573c7acfe09e92deda3e6@free.fr> (raw)
In-Reply-To: <a8a63d9b-fdc3-4e44-aeed-846d1406af93@mind.be>

Hi Titouan,

On 07/08/2026 13:53, Titouan Christophe wrote:
> On 26/07/26 11:27, Julien Olivain via buildroot wrote:
>> pyDAL is using xmlrpc at runtime. See:
>> https://github.com/web2py/pydal/blob/v20260313.1/pydal/_compat.py#L114
>> 
>> Signed-off-by: Julien Olivain <ju.o@free.fr>
> 
> Applied to 2025.02.x and 2026.05.x, thanks

I saw you included other new runtime tests in maintenance branches,
but you skipped the pydal one:
https://gitlab.com/buildroot.org/buildroot/-/commit/67d6e6602fec095084f64560050cb1195dff7765

Is there a specific reason, or did you just missed it?

Best regards,

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

      reply	other threads:[~2026-08-10 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26  9:27 [Buildroot] [PATCH 1/2] package/python-pydal: needs python xml module at runtime Julien Olivain via buildroot
2026-07-26  9:27 ` [Buildroot] [PATCH 2/2] support/testing: python-pydal: new runtime test Julien Olivain via buildroot
2026-08-02 20:29 ` [Buildroot] [PATCH 1/2] package/python-pydal: needs python xml module at runtime Julien Olivain via buildroot
2026-08-07 11:53 ` Titouan Christophe via buildroot
2026-08-10 18:31   ` Julien Olivain 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=6e608820fd7573c7acfe09e92deda3e6@free.fr \
    --to=buildroot@buildroot.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=titouan.christophe@mind.be \
    /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.