($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: mark.hatle@kernel.crashing.org
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-python] obsolete distutils3-base.bbclass error
Date: Wed, 17 Apr 2024 08:11:08 +0200	[thread overview]
Message-ID: <CA+chaQehGAmMgJ8dWD8G+_Ozv6uycMD0xGE7kC_diYBh9PLAog@mail.gmail.com> (raw)
In-Reply-To: <0c3ae56b-b5f8-4371-a0ac-c1f1444264df@kernel.crashing.org>

See https://github.com/openembedded/meta-openembedded/pull/811

On Wed, Apr 17, 2024 at 12:13 AM Mark Hatle via lists.openembedded.org
<mark.hatle=kernel.crashing.org@lists.openembedded.org> wrote:
>
> In scarthgap/master, I still have a couple of recipes that haven't been moved to
> using the proper setuptools3-base class yet.  However, including distutils3-base
> fails.
>
> The code meta-python/classes/distutils3-base.bbclass is missing the close "}".
>
> --Mark
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#109986): https://lists.openembedded.org/g/openembedded-devel/message/109986
> Mute This Topic: https://lists.openembedded.org/mt/105566562/3617156
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [martin.jansa@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      reply	other threads:[~2024-04-17  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 22:12 [meta-python] obsolete distutils3-base.bbclass error Mark Hatle
2024-04-17  6:11 ` Martin Jansa [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=CA+chaQehGAmMgJ8dWD8G+_Ozv6uycMD0xGE7kC_diYBh9PLAog@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=mark.hatle@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).