All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>,
	richard.purdie@linuxfoundation.org
Cc: andriy.danylovskyy@streamunlimited.com, poky@yoctoproject.org
Subject: Re: [thud] [PATCH 0/2] opkg and BAD_RECOMMENDATIONS in thud 2.6.2
Date: Thu, 17 Oct 2019 16:07:26 +0200	[thread overview]
Message-ID: <023f1747-3ee9-227f-b2cb-223fe40e6c47@geanix.com> (raw)
In-Reply-To: <20191017085458.ugvi7vaaidhqnica@qschulz>



On 17/10/2019 10.54, Quentin Schulz wrote:

..

>> Would someone be able to confirm which patches we need to revert
>> please? It may also help narrow down the problem if we could figure out
>> which patches specifically need to be reverted to fix it.
>>
> 
> @Sean, please confirm so I don't mess up twice in a row :)
> 
> e8cd30ba6cec854d85c7ad47edc208107858a5d7 ("OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS")
> is the one which should be reverted. This commit cannot work without the
> one mentioned below because it relies on opkg supporting
> --add-ignore-recommends on the command line.

I can comfirm it works as expected when:

e8cd30ba6cec854d85c7ad47edc208107858a5d7 ("OpkgPM: use 
--add-ignore-recommends to process BAD_RECOMMENDATIONS")

is reverted :-)

But had to wipe my `tmp` to prove it. Seems like some changes are not 
picked up properly.

/Sean


      reply	other threads:[~2019-10-17 14:08 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
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 [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=023f1747-3ee9-227f-b2cb-223fe40e6c47@geanix.com \
    --to=sean@geanix.com \
    --cc=andriy.danylovskyy@streamunlimited.com \
    --cc=poky@yoctoproject.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=richard.purdie@linuxfoundation.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.