mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] rpcbind: version bump 1.2.8 -> 1.3.1
Date: Sat, 24 Oct 2026 09:16:28 +0200	[thread overview]
Message-ID: <20261024071628.2486224-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261014214034.3673839-1-s.pueschel@pengutronix.de>

Thanks, applied as 3a50758b1ffb9c6d93935f80bb97dcc60b59a015.

Michael

[sent from post-receive hook]

On Sat, 24 Oct 2026 09:16:28 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> https://sourceforge.net/projects/rpcbind/files/rpcbind/1.2.9/1.2.9-ChangeLog/download
> https://sourceforge.net/projects/rpcbind/files/rpcbind/1.3.1/1.3.1-Changelog/download
> 
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261014214034.3673839-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/rpcbind.make b/rules/rpcbind.make
> index 4ec4b48b6e63..412477d76699 100644
> --- a/rules/rpcbind.make
> +++ b/rules/rpcbind.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_RPCBIND) += rpcbind
>  #
>  # Paths and names
>  #
> -RPCBIND_VERSION	:= 1.2.8
> -RPCBIND_SHA256	:= 964132c389918e8964d7334936b6dd10ef025b300c6b29e693ba0f29550e3de5
> +RPCBIND_VERSION	:= 1.3.1
> +RPCBIND_SHA256	:= 8e551b445f5172f8ef218845af342fb2a2d741b57ce8c777c781a01ea92f92a5
>  RPCBIND		:= rpcbind-$(RPCBIND_VERSION)
>  RPCBIND_SUFFIX	:= tar.bz2
>  RPCBIND_URL	:= $(call ptx/mirror, SF, rpcbind/$(RPCBIND).$(RPCBIND_SUFFIX))



      reply	other threads:[~2026-10-24  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 21:40 [ptxdist] [PATCH] " Sven Püschel
2026-10-24  7:16 ` Michael Olbrich [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=20261024071628.2486224-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=s.pueschel@pengutronix.de \
    /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