All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/rpcbind: bump to version 1.2.8
Date: Sun, 17 Aug 2025 12:27:22 +0200	[thread overview]
Message-ID: <20250817102722.GA89579@pevik> (raw)
In-Reply-To: <20250816193255.1429450-1-thomas.petazzoni@bootlin.com>

Hi Thomas, all,

> List of commits between 1.2.7..1.2.8:

> f979f1b8fa202cd0d6c352de0f2b64361ce5ea33 (HEAD -> master, tag: rpcbind-1_2_8, origin/master, origin/HEAD) Release: 1.2.8
> a9ecbb81940b23a4bb9814e126c1c1ae1db93b69 (tag: rpcbind-1_2_8-rc3) rpcinfo: Removed a number of "old-style function definition" warnings
> 8cc10d038c361f296b0a8e068c173acc33568997 rpcbind: Add -v flag to print version and config
> 8ef2e504df6e5ec3321c0804a8c6684d781e7a84 man/rpcbind: Update list of options
> 74da58dde5b1a1a7e54df1fb16315845195a69c0 (tag: rpcbind-1_2_8-rc2) Comment out ListenStream=@/run/rpcbind.sock
> b78689b8f1df42eb593dc3412698aa1b8aaa3532 [nfs/nfs-utils/rpcbind] rpcbind: avoid dereferencing NULL from realloc()
> fd1d5387de8078530d51eccf876afe6e6182b975 (tag: rpcbind-1_2_8-rc1) Move rpbind's default configuration to /run verses /var/run
> 7a6b1c58eee2e5fa74e3e4045c4950fbb4f8af0a Move rpcbind.lock to /run
> be63348bd3dd9e69e151ff83f08f09e1a9df82bf systemd/rpcbind.service.in: Want/After systemd-tmpfiles-setup
> 626fd801a13cecd8eb79ac6e979c248d7214aad4 systemd/rpcbind.service.in: Add various hardenings options
> 511fc4f4bc5ca7b7c8dac877d590d0634e570e6d man/rpcbind: Add Files section to manpage
> 31157ba6e60b0a8c4989010df8b1cf2aa673a86c systemd/rpcbind.service.in: Add few default EnvironmentFile

First, thank you for doing the update.

> So really not much.

FYI the motivation was 1) to print version and compile time options to fix RPC
tests on disabled remote calls 2) upstream more distro patches (mostly Debian
and openSUSE specific).

BTW I thought that old Buildroot specific patch 0001-Remove-yellow-pages-support.patch
was already upstreamed, but obviously not. Patch was added by you in 2012-11-04
in 8bc245da21 ("rpcbind: new package"), rpcbind was at the time 0.2.0, libtirpc
0.2.2.

When I get the time, I'll check if it's really needed. If yes there could be
libtirpc compile option to disable it (and have it disabled by default, who
needs yellow pages nowadays).

> While we're at it, let's add a sha1 hash provided directly by
> Sourceforge, in addition to the locally calculated sha256.

+1

I hate having to look at sourceforge web page (I wish the upstream upload
libtirpc and rpcbind archives also to kernel.org [1], as they do for nfs-utils
[2], then there would much easier to update the hash.

[1] https://www.kernel.org/pub/linux/utils/
[2] https://www.kernel.org/pub/linux/utils/nfs-utils/

Kind regards,
Petr
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-08-17 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 19:32 [Buildroot] [PATCH] package/rpcbind: bump to version 1.2.8 Thomas Petazzoni via buildroot
2025-08-16 20:12 ` Peter Korsgaard
2025-08-17 10:27 ` Petr Vorel [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=20250817102722.GA89579@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot@buildroot.org \
    --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.