From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Markus Volk <f_l_k@t-online.de>,
Kai Kang <kai.kang@eng.windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] adwaita-icon-theme: 43 -> 45.0
Date: Fri, 22 Sep 2023 05:23:09 +0200 [thread overview]
Message-ID: <LQAD1S.UGTSIS239E9B@t-online.de> (raw)
In-Reply-To: <CANNYZj-7ZFnGg914eZ3rVd5TcpNwdPADgY8Ph5-A=fftsYr3AA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Thu, Sep 21 2023 at 10:35:13 PM +02:00:00, Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
> Please read again what I said about task signatures because the
> problem with allarch compatibility is there.
I read it and also looked at the signatures. But it didn't tell me as
much as it would have told you. At least it pointed me in the right
direction. But I needed more research to get a handle on it. In my
case, it was a combination of two problems. In the case of the original
recipe, it's just the first one.
- allarch must be last in inherit
'inherit gnomebase gtk-icon-cache allarch'
- you should not set GTK_IC = "4", as I had previously assumed
[-- Attachment #2: Type: text/html, Size: 935 bytes --]
next prev parent reply other threads:[~2023-09-22 3:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 6:47 [PATCH v2] adwaita-icon-theme: 43 -> 45.0 kai.kang
2023-09-21 7:06 ` Alexander Kanavin
2023-09-21 8:16 ` Kai
2023-09-21 8:34 ` [OE-core] " Markus Volk
2023-09-21 8:40 ` Alexander Kanavin
2023-09-21 9:45 ` Markus Volk
2023-09-21 9:51 ` Alexander Kanavin
2023-09-21 11:37 ` Markus Volk
2023-09-21 15:16 ` Markus Volk
2023-09-21 15:36 ` Alexander Kanavin
2023-09-21 15:51 ` Markus Volk
2023-09-21 17:36 ` Alexander Kanavin
2023-09-21 20:24 ` Markus Volk
2023-09-21 20:35 ` Alexander Kanavin
2023-09-22 3:23 ` Markus Volk [this message]
2023-09-22 4:02 ` Kai
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=LQAD1S.UGTSIS239E9B@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=kai.kang@eng.windriver.com \
--cc=openembedded-core@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.