All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [RFC][PATCH] package/nfs-utils: bump version to 2.9.2
Date: Sun, 16 Aug 2026 09:16:58 +0200	[thread overview]
Message-ID: <5588dc00d19f533a6e87325c19d92330@free.fr> (raw)
In-Reply-To: <a89c6eb42eea4e1609f0a75dc157191e@free.fr>

Hi Petr,

On 11/08/2026 21:35, Julien Olivain wrote:
> Hi Petr,
> 
> On 11/08/2026 06:58, Petr Vorel wrote:
>> Remove patches upstreamed in this release.
>> 
>> Release announce:
>> https://lore.kernel.org/linux-nfs/dc0f6f41-84be-4a70-92db-89890bded3ab@redhat.com/
>> 
>> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
>> ---
>> [RFC] Building nfs-utils 2.9.2 with --disable-nfsdctl fails to link
>> exportfs [1]. This is a regression from 2.9.1. Buildroot uses
>> --disable-nfsdctl => we should probably wait for the fix.
> 
> I agree, we should wait for a fix before merging.
> Please, send a v2 adding the fix or including a newer version when
> available.

For info, a fix was committed in:
https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=67ed1bdb1af1c70a5fd3b377a997401b7676b827

So you either include it as a package patch, or wait for the next 
version.

>> Kind regards,
>> Petr
>> 
>> [1] 
>> https://lore.kernel.org/linux-nfs/9fec9f1b-1c10-4a20-8282-dfc9addb4ee8@est.tech/
> 
> Best regards,
> 
> Julien.

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-16  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  4:58 [Buildroot] [RFC][PATCH] package/nfs-utils: bump version to 2.9.2 Petr Vorel
2026-08-11 19:35 ` Julien Olivain via buildroot
2026-08-16  7:16   ` Julien Olivain via buildroot [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=5588dc00d19f533a6e87325c19d92330@free.fr \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ju.o@free.fr \
    --cc=petr.vorel@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.