From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sysrepo: fix host/staging install steps
Date: Mon, 11 Nov 2019 15:27:32 +0100 [thread overview]
Message-ID: <20191111152732.43c195c1@windsurf.home> (raw)
In-Reply-To: <CAEyMn7Zm+7k+Mwugu-oxRGUjfsyV3btam3DCdR+8mrenzdCzug@mail.gmail.com>
Hello,
On Mon, 11 Nov 2019 15:07:31 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > > Your defconfig shows the problem not while building rather in the install step.
> >
> > Hu? When I said "build", it of course means a Buildroot build, so it
> > does both the build and installation of all packages.
> >
> > The autobuilder failures happens at Buildroot build time, and I was not
> > able to reproduce it, and therefore not able to check that your patch
> > solves it.
>
> Hmm, now I'm a little bit confused. Do you mean with autobuilder
> failure the results of the buildroot CI?
> I think this issues was already solves with the patch provided by
> Fabrice Fontaine:
>
> http://lists.busybox.net/pipermail/buildroot/2019-October/265043.html
> http://lists.busybox.net/pipermail/buildroot/2019-October/265044.html
>
> And currently there should'nt be any autobuilder failures!?
Is your patch https://patchwork.ozlabs.org/patch/1188504/ fixing any
autobuilder failure ? I was assuming it was there to fix the build
issue at
http://autobuild.buildroot.net/results/bcd/bcd9bdd3bc83c1f2ab0b24348d51de27d88649b4/build-end.log.
http://lists.busybox.net/pipermail/buildroot/2019-October/265043.html
fixes
http://autobuild.buildroot.net/results/d80/d807f3dc922a61e099a66de3bc340c018a86e150/build-end.log,
which is a different failure.
http://lists.busybox.net/pipermail/buildroot/2019-October/265044.html
fixes
http://autobuild.buildroot.net/results/f0e/f0e4368977f257d76aedff335af3068deafaf28f/build-end.log
which another different issue.
> And this patch fixes some "new" issues with wrongly installed files in
> wrong locations.
Yes, which is exactly what is reported at
http://autobuild.buildroot.net/results/bcd/bcd9bdd3bc83c1f2ab0b24348d51de27d88649b4/build-end.log,
but I was not able to reproduce this failure with a simple configuration.
Hence my question: do you have a simple configuration that reproduces
the "wrongly installed files in wrong locations" issue ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-11 14:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 6:01 [Buildroot] [PATCH 1/1] package/sysrepo: fix host/staging install steps Heiko Thiery
2019-11-04 21:38 ` Thomas Petazzoni
2019-11-05 8:03 ` Heiko Thiery
2019-11-05 8:09 ` Thomas Petazzoni
2019-11-05 8:19 ` Heiko Thiery
2019-11-08 21:58 ` Thomas Petazzoni
2019-11-10 16:00 ` Heiko Thiery
2019-11-11 13:53 ` Thomas Petazzoni
2019-11-11 14:07 ` Heiko Thiery
2019-11-11 14:27 ` Thomas Petazzoni [this message]
2019-11-11 14:35 ` Heiko Thiery
2019-11-11 14:40 ` Thomas Petazzoni
2019-11-11 14:43 ` Heiko Thiery
2019-11-11 14:59 ` Thomas Petazzoni
2019-11-11 15:04 ` Heiko Thiery
2019-11-11 15:12 ` Thomas Petazzoni
2019-11-11 19:22 ` Heiko Thiery
2019-11-12 7:53 ` Heiko Thiery
2019-11-17 5:32 ` Heiko Thiery
2019-12-02 8:15 ` Heiko Thiery
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=20191111152732.43c195c1@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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