From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>, Seebs <seebs@seebs.net>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pseudo: Update to gain key bugfixes
Date: Wed, 17 Apr 2019 14:12:19 +0000 [thread overview]
Message-ID: <5bc0e9c882a24ddcb08d922e290d3dad@XBOX04.axis.com> (raw)
In-Reply-To: <2cf8ada8df82cb38252db3ff4c45b9f85294c63e.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org <openembedded-
> core-bounces@lists.openembedded.org> On Behalf Of
> richard.purdie@linuxfoundation.org
> Sent: den 12 april 2019 10:18
> To: Seebs <seebs@seebs.net>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] pseudo: Update to gain key bugfixes
>
> On Wed, 2019-04-10 at 18:59 -0500, Seebs wrote:
> > On Thu, 11 Apr 2019 00:12:54 +0100
> > Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> >
> > > -SRCREV = "6294b344e5140f5467e6860f45a174440015304e"
> > > +SRCREV = "6ebc7d6bc8ab973d0ba949eeb363821811ce8dc5"
> >
> > I would sort of recommend one of the two commits since then -- one
> > may
> > fix the .NET startup failures, and the other fixes warnings that this
> > one introduced and I forgot to fix. But I'm also okay with this one.
>
> That is good news. I've tested and updated to the later revision,
> thanks!
>
> Cheers,
>
> Richard
One of our developers, who has been especially affected by this
problem, reported that he was still having problems building a
couple of recipes even with the latest version of pseudo. After
some debugging it was determined that the problem was due to the
Debian version of coreutils that he was using. When he downgraded
from 8.30-3 to 8.30-1 the problems he was seeing went away. The
changelog for the reverted changes indicate that pseudo will
need to be made aware about what they are doing:
,----
| coreutils (8.30-3) unstable; urgency=medium
|
| * Fix renameat2 patch (Closes: #923420)
|
| -- Michael Stone <mstone@debian.org> Thu, 28 Feb 2019 10:30:31 -0500
|
| coreutils (8.30-2) unstable; urgency=medium
|
| * Use renameat2 glibc function that can be intercepted by fakechroot
| (Closes: #915559)
| * Above requires autoreconf turned on again
|
| -- Michael Stone <mstone@debian.org> Tue, 26 Feb 2019 07:15:19 -0500
`----
//Peter
prev parent reply other threads:[~2019-04-17 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 23:12 [PATCH] pseudo: Update to gain key bugfixes Richard Purdie
2019-04-10 23:27 ` Otavio Salvador
2019-04-10 23:59 ` Seebs
2019-04-12 8:17 ` richard.purdie
2019-04-13 8:03 ` Andreas Müller
2019-04-13 14:41 ` Seebs
2019-04-17 14:12 ` Peter Kjellerstedt [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=5bc0e9c882a24ddcb08d922e290d3dad@XBOX04.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=seebs@seebs.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox