From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] monit: bump to version 3.12.2
Date: Thu, 16 Apr 2015 06:25:40 +0300 [thread overview]
Message-ID: <20150416032540.GH30380@tarshish> (raw)
In-Reply-To: <1429129390-28278-1-git-send-email-sebastien.bourdelin@savoirfairelinux.com>
Hi Sebastien,
On Wed, Apr 15, 2015 at 04:23:10PM -0400, Sebastien Bourdelin wrote:
> Also add hash file and remove the m4 directory creation from the monit.mk
> which is now in the source tree.
>
> Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
> ---
> package/monit/monit.hash | 6 ++++++
> package/monit/monit.mk | 8 +-------
> 2 files changed, 7 insertions(+), 7 deletions(-)
> create mode 100644 package/monit/monit.hash
>
> diff --git a/package/monit/monit.hash b/package/monit/monit.hash
> new file mode 100644
> index 0000000..9313c7a
> --- /dev/null
> +++ b/package/monit/monit.hash
> @@ -0,0 +1,6 @@
> +# From https://mmonit.com/monit/dist/monit-5.12.2.tar.gz.sha256:
> +sha256 8ab0296d1aa2351b1573481592d7b5e06de1edd49dff1b5552839605a450914c monit-5.12.2.tar.gz
> +
> +# Locally calculated:
> +md5 5f5cf4c18b42e8091b49b4e07cf972ce monit-5.12.2.tar.gz
> +sha1 5ffdcc0c5dfbc12bfe2e35dd33d2626a038771fc monit-5.12.2.tar.gz
Since we have an upstream hash that is also sha256, there is no need to add
locally calculated hashes.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-04-16 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 20:23 [Buildroot] [PATCH 1/1] monit: bump to version 3.12.2 Sebastien Bourdelin
2015-04-16 3:25 ` Baruch Siach [this message]
2015-04-16 5:59 ` Thomas Petazzoni
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=20150416032540.GH30380@tarshish \
--to=baruch@tkos.co.il \
--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