All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br025@umbiko.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libnfs: update version to 7.0.0
Date: Fri, 28 Aug 2026 21:14:33 +0200	[thread overview]
Message-ID: <apHdyUUu88PQur7A@windsurf> (raw)
In-Reply-To: <20260827040513.3903-1-br025@umbiko.net>

On Thu, Aug 27, 2026 at 06:05:12AM +0200, Andreas Ziegler wrote:
> New version contains all current patches, plus one that fixes
> "undefined reference to 'gnutls_*'" if libnfs was built with
> GnuTLS support
> 
> Change log:
> https://github.com/sahlberg/libnfs/compare/libnfs-6.0.2...libnfs-7.0.0
> 
> Fixes:
> https://autobuild.buildroot.net/results/b07/b070248b2bceaceaaed8e826b1247ccfba1ba9fb
> https://autobuild.buildroot.net/results/e14/e1461b76121addd8f04f08819b2e3e453a12c679
> https://autobuild.buildroot.net/results/87c/87c79193d2ea86f47e36232fe514837ad99c5f30
> 
> Signed-off-by: Andreas Ziegler <br025@umbiko.net>

Thanks for the patch, I was precisely investigating this build issue.

However, we need more than a version bump: we need to understand since
when the problem exists, so that we can understand whether the issue
needs to be fixed in one of our maintained branches (most notably
2025.02.x). And if that's the case, rather than a version bump, we'd
prefer to have a fix backport, unless of course the fix is massive
and/or difficult to backport.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-28 19:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  4:05 [Buildroot] [PATCH 1/1] package/libnfs: update version to 7.0.0 Andreas Ziegler
2026-08-28 19:14 ` Thomas Petazzoni 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=apHdyUUu88PQur7A@windsurf \
    --to=buildroot@buildroot.org \
    --cc=br025@umbiko.net \
    --cc=thomas.petazzoni@bootlin.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.