From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/fakeroot: bump version to 1.24
Date: Sat, 9 May 2020 18:50:10 +0200 [thread overview]
Message-ID: <20200509185010.25c376ea@windsurf.home> (raw)
In-Reply-To: <20200506131130.410171-2-nolange79@gmail.com>
On Wed, 6 May 2020 15:11:29 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> Signed-off-by: Norbert Lange <nolange79@gmail.com>
> ---
> ...02-Select-TCP-when-lack-of-SYSV-IPC.patch} | 0
> ...nicate-check-return-status-of-msgrcv.patch | 46 -------------------
> package/fakeroot/fakeroot.hash | 6 +--
> package/fakeroot/fakeroot.mk | 6 +--
> 4 files changed, 5 insertions(+), 53 deletions(-)
> rename package/fakeroot/{0003-Select-TCP-when-lack-of-SYSV-IPC.patch => 0002-Select-TCP-when-lack-of-SYSV-IPC.patch} (100%)
> delete mode 100644 package/fakeroot/0002-communicate-check-return-status-of-msgrcv.patch
What happened to 0002-communicate-check-return-status-of-msgrcv.patch ?
It is removed by your patch. Why?
Also, your PATCH 1/2 is a version bump, but PATCH 2/2 is a bug fix.
Since Buildroot 2020.05-rc1 has now been released, we normally don't
merge version bumps in master.
Could you clarify if the fchownat/fchmodat issue happens with the
current version of fakeroot in Buildroot (1.20) ? Or only with the
updated version 1.24 ? Can it be fixed with fakeroot 1.20 ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-05-09 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:11 [Buildroot] (no subject) Norbert Lange
2020-05-06 13:11 ` [Buildroot] [PATCH v2 1/2] package/fakeroot: bump version to 1.24 Norbert Lange
2020-05-09 16:50 ` Thomas Petazzoni [this message]
2020-05-09 21:29 ` Norbert Lange
2020-05-09 21:41 ` Thomas Petazzoni
2020-05-06 13:11 ` [Buildroot] [PATCH v2 2/2] package/fakeroot: fix for fchownat/fchmodat Norbert Lange
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=20200509185010.25c376ea@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