Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] wiringpi: bump to version 2.44
Date: Sun, 19 Mar 2017 22:24:09 +0100	[thread overview]
Message-ID: <20170319222409.205633ad@gmx.net> (raw)
In-Reply-To: <20170318141428.0c4b6d36@free-electrons.com>

Hello Thomas,

On Sat, 18 Mar 2017 14:14:28 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Wed, 15 Mar 2017 22:08:28 +0100, Peter Seiderer wrote:
> > - rebase 0001-Adjust-for-buildroot-build.patch
> > - delete 0002-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
> >   (all changes are incorporated into wiringpi-2.44)
> > - remove useless hash file (git download)
> 
> Git downloads now generate reproducible tarballs, so we in fact want to
> add hashes for them as well. However, it is true that the hash is not
> checked currently. This has been on the TODO-list for a while.

Mhhh, tried several times, every time I get a different checksum:

	$ sha256sum dl/wiringpi-2.44.tar.gz 
5324ed452b7adfb77d049ea49dfe8878605c6198cb5c706ae2b285a70fb9d096  dl/wiringpi-2.44.tar.gz

	$ sha256sum dl/wiringpi-2.44.tar.gz 
65e6b3a916b940eec085222a28a5859b09e79e0020de2f2b07563d910426180c  dl/wiringpi-2.44.tar.gz

Regards,
Peter


> 
> So I've kept the hash file (after updating it).
> 
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> >  .../wiringpi/0001-Adjust-for-buildroot-build.patch | 26 +++++-----
> >  ...de-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch | 60 ----------------------
> >  package/wiringpi/wiringpi.hash                     |  2 -
> >  package/wiringpi/wiringpi.mk                       |  2 +-
> >  4 files changed, 14 insertions(+), 76 deletions(-)
> >  delete mode 100644 package/wiringpi/0002-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
> >  delete mode 100644 package/wiringpi/wiringpi.hash
> 
> Applied to master, thanks.
> 
> Thomas

  reply	other threads:[~2017-03-19 21:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 21:08 [Buildroot] [PATCH v1] wiringpi: bump to version 2.44 Peter Seiderer
2017-03-18 13:14 ` Thomas Petazzoni
2017-03-19 21:24   ` Peter Seiderer [this message]
2017-03-19 22:14     ` Yann E. MORIN
2017-03-19 22:28     ` Arnout Vandecappelle
2017-03-19 22:31       ` Arnout Vandecappelle
2017-03-20 19:27         ` Peter Seiderer
2017-03-20 20:39           ` Arnout Vandecappelle
2017-03-20 21:32             ` Peter Seiderer

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=20170319222409.205633ad@gmx.net \
    --to=ps.report@gmx.net \
    --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