From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libtirpc: bump version to 1.3.1
Date: Tue, 29 Dec 2020 21:57:57 +0100 [thread overview]
Message-ID: <20201229205757.GB2801@pevik> (raw)
In-Reply-To: <20201229205012.GY1680670@scaer>
Hi Yann,
> Petr, All,
> On 2020-12-02 19:49 +0100, Petr Vorel spake thusly:
> > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> > ---
> > package/libtirpc/libtirpc.hash | 4 ++--
> > package/libtirpc/libtirpc.mk | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> > diff --git a/package/libtirpc/libtirpc.hash b/package/libtirpc/libtirpc.hash
> > index e437554285..0e77f23947 100644
> > --- a/package/libtirpc/libtirpc.hash
> > +++ b/package/libtirpc/libtirpc.hash
> > @@ -1,5 +1,5 @@
> > # From sourceforge's info on download page:
> > -sha1 f182235e32942fc0ac6b9b5b6fe7e32f69362659 libtirpc-1.2.6.tar.bz2
> > +sha1 882eaf4c13f0cafb83afd96cd2855638f978d755 libtirpc-1.3.1.tar.bz2
> > # Locally computed
> > -sha256 4278e9a5181d5af9cd7885322fdecebc444f9a3da87c526e7d47f7a12a37d1cc libtirpc-1.2.6.tar.bz2
> > +sha256 245895caf066bec5e3d4375942c8cb4366adad184c29c618d97f724ea309ee17 dl/libtirpc/libtirpc-1.3.1.tar.bz2
> ___________________________________________________________________________,^^^^^^^^^^^^
> Hmmm... bad copy-paste. ;-)
> Fixed, and applied to master, thanks.
Uh, sorry for it, thanks for fixing!
> Regards,
> Yann E. MORIN.
Kind regards,
Petr
next prev parent reply other threads:[~2020-12-29 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 18:49 [Buildroot] [PATCH 1/2] libtirpc: remove NIS patch Petr Vorel
2020-12-02 18:49 ` [Buildroot] [PATCH 2/2] package/libtirpc: bump version to 1.3.1 Petr Vorel
2020-12-02 18:51 ` Petr Vorel
2020-12-29 20:50 ` Yann E. MORIN
2020-12-29 20:57 ` Petr Vorel [this message]
2020-12-29 20:46 ` [Buildroot] [PATCH 1/2] libtirpc: remove NIS patch Yann E. MORIN
2020-12-29 21:06 ` Petr Vorel
2020-12-29 23:00 ` Yann E. MORIN
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=20201229205757.GB2801@pevik \
--to=petr.vorel@gmail.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