n
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core][PATCH] package_manager/ipk: do not pipe stderr to
> > stdout
> >
> > Thanks for the information - perhaps this should be added to the commit
> > message?
> >
> > Does this cha
acceptable?
Shruthi
> -Original Message-
> From: Alexander Kanavin
> Sent: Thursday, June 30, 2022 1:47 AM
> To: Shruthi Ravichandran
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH] package_manager/ipk: do not pipe stderr to
> stdo
nd
> itself failing.
>
> Hope that helps,
> Shruthi
>
> > -Original Message-
> > From: Alexander Kanavin
> > Sent: Tuesday, June 28, 2022 1:33 PM
> > To: Shruthi Ravichandran
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re:
helps,
Shruthi
> -Original Message-
> From: Alexander Kanavin
> Sent: Tuesday, June 28, 2022 1:33 PM
> To: Shruthi Ravichandran
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH] package_manager/ipk: do not pipe stderr to
> stdout
>
> This ne
This needs additional justification. What are the error messages, why are
they harmless and why the solution is to suppress them instead of
addressing the reasons they appear?
Alex
On Tue 28. Jun 2022 at 23.13, Shruthi Ravichandran <
shruthi.ravichand...@ni.com> wrote:
> When parsing the output
When parsing the output of a command, do not pipe stderr to stdout.
Opkg sometimes prints harmless error messages even when the opkg
command succeeds. When stderr is piped to stdout, these error
messages may clobber the stdout and cause unexpected results while
parsing the output.
Signed-off-by: S
