From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [TINDERBOX] A round with dev-lang/python-exec[-native-symlinks]
Date: Sun, 31 Jan 2021 20:49:13 +0100 [thread overview]
Message-ID: <ea4476ef22ccaa9db1ae7fd8cdc6940352147dd1.camel@gentoo.org> (raw)
In-Reply-To: <64a4e52babc0b8cc7d8f9a5496cc53a7e2206933.camel@gentoo.org>
On Sun, 2021-01-31 at 20:09 +0200, Mart Raudsepp wrote:
> Ühel kenal päeval, T, 29.12.2020 kell 13:33, kirjutas Agostino Sarubbo:
> > On martedì 29 dicembre 2020 13:03:07 CET Michał Górny wrote:
> > > @ago, could you make sure that the tinderbox tells people to read
> > > up
> > > on the tracker?
> >
> > I added the note.
> >
> > However the first thing I would to do in reports like this is at
> > least click
> > on the tracker bug
>
> It seems like right now I will get a bug about this every time I make
> some sort of a version bump, as that triggers it on the tinderbox.
>
> That's because most of the packages I touch use meson and have the
> post-install hook written in python with a python3 shebang, while the
> ebuild usually doesn't even inherit any python eclasses, as this is all
> considered handled by meson, and having to go and add python-any-r1
> inherits and python_fix_shebang all over the place would be rather
> awful.
You don't have to add python_fix_shebang.
--
Best regards,
Michał Górny
prev parent reply other threads:[~2021-01-31 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 11:51 [gentoo-dev] [TINDERBOX] A round with dev-lang/python-exec[-native-symlinks] Agostino Sarubbo
2020-12-29 11:57 ` Joonas Niilola
2020-12-29 12:03 ` Michał Górny
2020-12-29 12:33 ` Agostino Sarubbo
2021-01-31 18:09 ` Mart Raudsepp
2021-01-31 19:49 ` Michał Górny [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=ea4476ef22ccaa9db1ae7fd8cdc6940352147dd1.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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