All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	 openembedded-core@lists.openembedded.org
Cc: Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH][dunfell] coreutils: don't split stdbuf to own package with single-binary
Date: Fri, 03 Jul 2020 10:19:13 +0100	[thread overview]
Message-ID: <64b8f2c4fbc20ea866a83844d117816de59082dc.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200703073631.16530-1-rasmus.villemoes@prevas.dk>

On Fri, 2020-07-03 at 09:36 +0200, Rasmus Villemoes wrote:
> Commit 992cec44 (coreutils: Move stdbuf into an own package
> coreutils-stdbuf) breaks package-qa when the single-binary
> PACKAGECONFIG is used:
> 
> ERROR: coreutils-8.31-r0 do_package_qa: QA Issue: /usr/bin/stdbuf
> contained in package coreutils-stdbuf requires /usr/bin/coreutils,
> but no providers found in RDEPENDS_coreutils-stdbuf? [file-rdeps]
> ERROR: coreutils-8.31-r0 do_package_qa: QA run found fatal errors.
> Please consider fixing them.
> ERROR: Logfile of failure stored in:
> /mnt/ext4/projects/deif/pdsystems/yocto/tmp-glibc/work/ppce300c3-oe-
> linux/coreutils/8.31-r0/temp/log.do_package_qa.5594
> ERROR: Task (/mnt/ext4/projects/deif/pdsystems/yocto/meta-
> poky/meta/recipes-core/coreutils/coreutils_8.31.bb:do_package_qa)
> failed with exit code '1'
> 
> With that PACKAGECONFIG, /usr/bin/stdbuf is just a simple "script"
> containing the single line
> 
>   #!/usr/bin/coreutils --coreutils-prog-shebang=stdbuf
> 
> Since there's no point splitting stdbuf to its own package when all
> the functionality is in the single big coreutils binary anyway, fix
> this by not creating the separate stdbuf package for the single-
> binary
> case.
> 
> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> ---
> The same issue exists in master, which has been bumped to 8.32, but
> other than that the patch should apply cleanly there as well.

Does this problem exist for other packages in coreutils? I'd suspect it
does in which case why is stdbuf special? Whilst I realise there is a
problem here is the correct fix not:

RDEPENDS_coreutils-stdbuf_class-target += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils', d)}"

?

As Alex says, this would need to be merged in master before we can even
consider it for dunfell.

Cheers,

Richard


  parent reply	other threads:[~2020-07-03  9:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  7:36 [PATCH][dunfell] coreutils: don't split stdbuf to own package with single-binary Rasmus Villemoes
2020-07-03  8:17 ` [OE-core] " Alexander Kanavin
2020-07-03  9:19 ` Richard Purdie [this message]
2020-07-03  9:29   ` Rasmus Villemoes
2020-07-03 10:48     ` Richard Purdie
2020-07-03 11:51       ` Rasmus Villemoes
2020-07-04 21:10       ` Adrian Bunk
2020-07-06  7:49         ` Rasmus Villemoes
2020-07-09  7:06 [PATCH] [dunfell] " Rasmus Villemoes

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=64b8f2c4fbc20ea866a83844d117816de59082dc.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rasmus.villemoes@prevas.dk \
    /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.