From: Quentin Schulz <quentin.schulz@streamunlimited.com>
To: akuster808 <akuster808@gmail.com>
Cc: poky@yoctoproject.org, andriy.danylovskyy@streamunlimited.com
Subject: Re: [thud] [PATCH 0/2] opkg and BAD_RECOMMENDATIONS in thud 2.6.2
Date: Thu, 25 Jul 2019 11:14:31 +0200 [thread overview]
Message-ID: <20190725091431.44qkrjtqjvkpjkka@qschulz> (raw)
In-Reply-To: <20190701153545.l7d6zo5gp5q526ds@qschulz>
Hi all,
On Mon, Jul 01, 2019 at 05:35:45PM +0200, Quentin Schulz wrote:
> Hi all,
>
> On Wed, Jun 12, 2019 at 09:25:45AM +0200, Quentin Schulz wrote:
> > Hi Armin,
> >
> > On Tue, Jun 11, 2019 at 10:24:20AM -0700, akuster808 wrote:
> > >
> > >
> > > On 6/11/19 7:46 AM, Quentin Schulz wrote:
> > [...]
> > > > I took me a while to find out that it's an issue with opkg itself and
> > > > nothing could be done in Yocto to fix it but I found the three following
> > > > patches in yocto-2.7:
> > > >
> > > > https://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d8e12f2bfc4deaa0dc7530cf3af905e18e8037f6
> > > > https://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c76c50df6498d85e7a6254002ff8f5e0ef3e67f7
> > > > https://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5bcb626cf49d2295ccca45d6fc7e1617cca932d6
> > >
> > > You mentioned 3 git commits but i only see 2 patches on the list.
> > >
> > > please clarify.
> > >
> >
> > Ugh, yes. Sorry :)
> >
> > These patches are the outcome of a discussion with Richard Purdie[1]
> > where he suggested that the upgrade commit is probably not a backport
> > candidate so I just went by it and removed it.
> >
>
> Kindly pinging so that this patch does not get lost at the bottom of the
> inbox :)
>
I haven't seen the patches in thud or thud-next nor in the latest series
of patches to be reviewed for thud and there isn't an ongoing discussion
on those two patches, so kindly pinging.
Let me know if there's anything I can do,
Quentin
--
StreamUnlimited Engineering GmbH
High Tech Campus Vienna, Gutheil-Schoder-Gasse 10, 1100 Vienna, Austria
quentin.schulz@streamunlimited.com, www.streamunlimited.com
next prev parent reply other threads:[~2019-07-25 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 14:46 [thud] [PATCH 0/2] opkg and BAD_RECOMMENDATIONS in thud 2.6.2 Quentin Schulz
2019-06-11 14:46 ` [thud] [PATCH 1/2] opkg: add --ignore-recommends flag Quentin Schulz
2019-06-11 14:46 ` [thud] [PATCH 2/2] OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS Quentin Schulz
2019-06-11 17:24 ` [thud] [PATCH 0/2] opkg and BAD_RECOMMENDATIONS in thud 2.6.2 akuster808
2019-06-12 7:25 ` Quentin Schulz
2019-07-01 15:35 ` Quentin Schulz
2019-07-25 9:14 ` Quentin Schulz [this message]
2019-08-14 7:10 ` Quentin Schulz
2019-10-16 8:27 ` Sean Nyekjaer
2019-10-17 8:15 ` Quentin Schulz
2019-10-17 8:23 ` richard.purdie
2019-10-17 8:54 ` Quentin Schulz
2019-10-17 14:07 ` Sean Nyekjaer
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=20190725091431.44qkrjtqjvkpjkka@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=akuster808@gmail.com \
--cc=andriy.danylovskyy@streamunlimited.com \
--cc=poky@yoctoproject.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.