Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	Matt Weber <matthew.weber@collins.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/rng-tools: bump to version 6.16
Date: Wed, 1 Feb 2023 18:45:15 +0100	[thread overview]
Message-ID: <20230201184515.0e6a9a53@gmx.net> (raw)
In-Reply-To: <CAPi7W82--bdBw2xRnVq+gVwnfrzcbUzmpQT24FbRAaZWqkDu4w@mail.gmail.com>

Hello *,

On Wed, 1 Feb 2023 18:35:17 +0100, Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Hi Yann,
> 
> Le lun. 30 janv. 2023 à 21:56, Yann E. MORIN <yann.morin.1998@free.fr> a
> écrit :
> 
> > Fabrice, All,
> >
> > On 2023-01-14 17:10 +0100, Fabrice Fontaine spake thusly:  
> > > https://github.com/nhorman/rng-tools/releases/tag/v6.16  
> > [--SNIP--]  
> > > diff --git a/package/rng-tools/rng-tools.hash  
> > b/package/rng-tools/rng-tools.hash  
> > > index be2ee13969..4c86791267 100644
> > > --- a/package/rng-tools/rng-tools.hash
> > > +++ b/package/rng-tools/rng-tools.hash
> > > @@ -1,3 +1,3 @@
> > >  # Locally computed
> > > -sha256  
> > bff0c58dff90ec10bd61f672e48618e045155eabd60b32d63a9c4ffbdad05f3a
> > rng-tools-6.15.tar.gz  
> > > +sha256  
> > 17666c4745fb635d91df293be188daf94b9e465d51d8503c0195fa3beb390894
> > rng-tools-6.16.tar.gz
> >
> > This hash does not match here, and we've had a report on IRC that it
> > does not work either. In both cases, we get this hash instead:
> >     8e518d45be68f42d0873732a9ac3ecfe0f10c4a9bd5d5f44180a49be8ebda96f
> >
> > Can you check on your side, how you ended up with 17666...90894?
> >  
> 
> I see that there is, only, one autobuilder failure.
> However, I retested again on a fresh tarball and
> 17666c4745fb635d91df293be188daf94b9e465d51d8503c0195fa3beb390894 is the
> correct sha256 for
> https://github.com/nhorman/rng-tools/archive/v6.16/rng-tools-6.16.tar.gz.

See https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/
for an possible explanation for the download hash diffs...

Regards,
Peter


> 
> 
> > Regards,
> > Yann E. MORIN.
> >  
> > >  sha256  
> > 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  COPYING  
> > > diff --git a/package/rng-tools/rng-tools.mk b/package/rng-tools/  
> > rng-tools.mk  
> > > index f736193a23..3e565103e4 100644
> > > --- a/package/rng-tools/rng-tools.mk
> > > +++ b/package/rng-tools/rng-tools.mk
> > > @@ -4,14 +4,14 @@
> > >  #
> > >  
> > ################################################################################  
> > >
> > > -RNG_TOOLS_VERSION = 6.15
> > > +RNG_TOOLS_VERSION = 6.16
> > >  RNG_TOOLS_SITE = $(call  
> > github,nhorman,$(RNG_TOOLS_NAME),v$(RNG_TOOLS_VERSION))  
> > >  RNG_TOOLS_LICENSE = GPL-2.0
> > >  RNG_TOOLS_LICENSE_FILES = COPYING
> > >  RNG_TOOLS_CPE_ID_VENDOR = rng-tools_project
> > >  RNG_TOOLS_SELINUX_MODULES = rngd
> > >
> > > -RNG_TOOLS_DEPENDENCIES = host-pkgconf openssl
> > > +RNG_TOOLS_DEPENDENCIES = host-pkgconf libcap openssl
> > >  # From git
> > >  RNG_TOOLS_AUTORECONF = YES
> > >
> > > @@ -45,6 +45,13 @@ else
> > >  RNG_TOOLS_CONF_OPTS += --without-nistbeacon
> > >  endif
> > >
> > > +ifeq ($(BR2_PACKAGE_RNG_TOOLS_QRYPT),y)
> > > +RNG_TOOLS_DEPENDENCIES += jansson libcurl
> > > +RNG_TOOLS_CONF_OPTS += --with-qrypt
> > > +else
> > > +RNG_TOOLS_CONF_OPTS += --without-qrypt
> > > +endif
> > > +
> > >  define RNG_TOOLS_INSTALL_INIT_SYSV
> > >       $(INSTALL) -D -m 755 package/rng-tools/S21rngd \
> > >               $(TARGET_DIR)/etc/init.d/S21rngd
> > > --
> > > 2.39.0
> > >
> > > _______________________________________________
> > > buildroot mailing list
> > > buildroot@buildroot.org
> > > https://lists.buildroot.org/mailman/listinfo/buildroot  
> >
> > --
> >
> > .-----------------.--------------------.------------------.--------------------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> > conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___
> >      |
> > | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is
> > no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v
> >  conspiracy.  |
> >
> > '------------------------------^-------^------------------^--------------------'
> >  
> 
> Best Regards,
> 
> Fabrice

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-02-01 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 16:10 [Buildroot] [PATCH 1/1] package/rng-tools: bump to version 6.16 Fabrice Fontaine
2023-01-28 23:07 ` Thomas Petazzoni via buildroot
2023-01-30 20:56 ` Yann E. MORIN
2023-02-01 17:35   ` Fabrice Fontaine
2023-02-01 17:45     ` Peter Seiderer [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=20230201184515.0e6a9a53@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=matthew.weber@collins.com \
    --cc=yann.morin.1998@free.fr \
    /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