Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 23:41:40 +0200	[thread overview]
Message-ID: <20200509234140.54562aba@windsurf.home> (raw)
In-Reply-To: <CADYdroP1VRGH5DcZMgO5ON_JK8+UVMHMyS6JpAJxdPyUJZ=BmQ@mail.gmail.com>

On Sat, 9 May 2020 23:29:22 +0200
Norbert Lange <nolange79@gmail.com> wrote:

> > What happened to 0002-communicate-check-return-status-of-msgrcv.patch ?
> > It is removed by your patch. Why?  
> 
> Cause its included in that version

OK.

> > 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 ?  
> 
> issue exist with both, could certainly be fixed in 1.20 separately,
> I just don't take much interest in fixing ~ 4 year versions by default.

In the general case, I agree. But here we have already tagged -rc1, and
we try to not merge version bumps so close to the release. And in the
context of Buildroot, fakeroot is used by *everybody*, so any
regression can cause issues to a significant number of users.

So I'd prefer to see the problem fixed for 1.20, so that we can apply
the fix on master, and then have the version bump to 1.24 in next.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-05-09 21:41 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
2020-05-09 21:29     ` Norbert Lange
2020-05-09 21:41       ` Thomas Petazzoni [this message]
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=20200509234140.54562aba@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