From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [autobuild] package/bwm-ng: fix build failures with gcc-5
Date: Sun, 16 Aug 2015 12:14:42 +0200 [thread overview]
Message-ID: <20150816101442.GC3650@free.fr> (raw)
In-Reply-To: <20150816100409.GD7325@sapphire.tkos.co.il>
Baruch, All,
On 2015-08-16 13:04 +0300, Baruch Siach spake thusly:
> On Sun, Aug 16, 2015 at 11:35:10AM +0200, Yann E. MORIN wrote:
> > On 2015-08-14 16:45 +0200, Yann E. MORIN spake thusly:
> > > On 2015-08-14 17:15 +0300, Baruch Siach spake thusly:
> > > > On Thu, Aug 13, 2015 at 11:07:58PM +0200, Yann E. MORIN wrote:
> > > > > diff --git a/package/bwm-ng/bwm-ng.hash b/package/bwm-ng/bwm-ng.hash
> > > > > +sha1 9445885d05e2430ca174739e3aba343afce94076 bwm-ng-0.6.1.tar.gz
> > > >
> > > > Why sha1?
> > > http://sourceforge.net/projects/bwmng/files/bwmng/0.6/
> > Now that I think about it, we are no longer downloading from DF.net, but
> > directly from the new official location:
> > http://www.gropp.org/?id=projects&sub=bwm-ng
> >
> > And this new location does not provide a hash... :-(
> >
> > But the file is also available on SF.net which provides this sha1.
> >
> > So I wonder: should we point to the SF.net provided sha1, even though
> > we're not downloading from there?
>
> Since the new bwm-ng website explicitly states that sf.net "will not be used
> anymore", and provided the dubious reputation of sf.net as of late, I don't
> think we can rely on their hashes in the long run, at least for this project.
> I vote for locally computed sha256 in this case.
Ack, thanks! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-08-16 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 21:07 [Buildroot] [PATCH] [autobuild] package/bwm-ng: fix build failures with gcc-5 Yann E. MORIN
2015-08-14 14:15 ` Baruch Siach
2015-08-14 14:45 ` Yann E. MORIN
2015-08-16 9:35 ` Yann E. MORIN
2015-08-16 10:04 ` Baruch Siach
2015-08-16 10:14 ` Yann E. MORIN [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=20150816101442.GC3650@free.fr \
--to=yann.morin.1998@free.fr \
--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