All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
	Qorin Qorinna <qorin.qorinna@nl.abb.com>
Cc: Qorin Wu <qorin.wu@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH] add missing normalize-resolvconf file since it has been moved to a separate file since version 1.90
Date: Mon, 20 Jun 2022 10:55:40 +0000	[thread overview]
Message-ID: <5a4ce3d633c64756aab5e3987b1668ea@axis.com> (raw)
In-Reply-To: <20220620114955.61d67615@booty>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Luca Ceresoli via
> lists.openembedded.org
> Sent: den 20 juni 2022 11:50
> To: Qorin Qorinna <qorin.qorinna@nl.abb.com>
> Cc: Qorin Wu <qorin.wu@gmail.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] add missing normalize-resolvconf file since it has been moved to a separate file since version 1.90

It is expected that the subject line is prefixed with the recipe name.
It is also a very long subject line. Better would be to move half of 
it to the commit message body, e.g.:

resolvconf: Install missing normalize-resolvconf file

It was moved to a separate file in version 1.90.

> Hi Qorin,
> 
> On Mon, 20 Jun 2022 09:24:22 +0000
> Qorin Qorinna <qorin.qorinna@nl.abb.com> wrote:
> 
> > Hi Luca,
> >
> > it's because the normalize-resolvconf requires sed.
> >
> > These are the error messages that I got when I built the package w/o sed
> > ERROR: resolvconf-1.91-r0 do_package_qa: QA Issue: /lib/resolvconf/normalize-resolvconf contained in package resolvconf requires /bin/sed, but no providers found in RDEPENDS:resolvconf? [file-rdeps]
> > ERROR: resolvconf-1.91-r0 do_package_qa: Fatal QA errors were found, failing task.
> 
> I see. In this case it would be nice to add either a line to the commit
> message or a comment in the .bb file, just to avoid others to wonder
> why sed is needed.

The problem here is that sed is provided by busybox and in almost all 
cases you do not want an explicit dependency on sed as that instead will 
install the sed program from the sed recipe. 

In this case I would recommend to add something like this:

# The normalize-resolvconf sed script uses /bin/sed on the shebang line.
# Ignore the file-rdeps test to avoid having to add a runtime dependency on sed.
INSANE_SKIP:${PN} += "file-rdeps"

> I added a line to the commit message on my branch that I'm going to
> test. It would be great if you could do so for future patches. Thanks!
> 
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

//Peter



  reply	other threads:[~2022-06-20 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  8:08 [PATCH] add missing normalize-resolvconf file since it has been moved to a separate file since version 1.90 Qorin
2022-06-20  9:20 ` [OE-core] " Luca Ceresoli
     [not found]   ` <AM0PR06MB4625172F0F099B35BB980A7BD9B09@AM0PR06MB4625.eurprd06.prod.outlook.com>
2022-06-20  9:49     ` Luca Ceresoli
2022-06-20 10:55       ` Peter Kjellerstedt [this message]
2022-06-20 13:15         ` Qorin Wu
2022-06-21  8:11 ` Luca Ceresoli

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=5a4ce3d633c64756aab5e3987b1668ea@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=qorin.qorinna@nl.abb.com \
    --cc=qorin.wu@gmail.com \
    /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.