From: Chris Packham <judge.packham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/syslog-ng: Update has for COPYING
Date: Thu, 19 Mar 2020 21:12:28 +1300 [thread overview]
Message-ID: <20200319081228.26547-1-judge.packham@gmail.com> (raw)
Some of the text was updated in syslog-ng-3.26.1. Update the hash
accordingly.
Fixes:
- http://autobuild.buildroot.net/results/4e0768a5aae0f77e1382108b1ca06d0ad78f4da4
- http://autobuild.buildroot.net/results/7430550dfce0bcb1bc5c9361033e26651883685a
- http://autobuild.buildroot.net/results/56afedff96d17ab4800845d7777dd151cb431acf
- http://autobuild.buildroot.net/results/2cac7eeaeabf8d77724ff283d3cb9026e778635c
- http://autobuild.buildroot.net/results/a8189eab2a14cc5d04d90d8f1fa058b86889cc21
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
package/syslog-ng/syslog-ng.hash | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/syslog-ng/syslog-ng.hash b/package/syslog-ng/syslog-ng.hash
index a752db0016..edb7efe195 100644
--- a/package/syslog-ng/syslog-ng.hash
+++ b/package/syslog-ng/syslog-ng.hash
@@ -1,5 +1,5 @@
# Locally computed
sha256 90214223864df252cea80dbb35c88a2464edcbbb2c9fbc6f6f6c13ee60cb62cd syslog-ng-3.26.1.tar.gz
-sha256 835219c8ca76156e6337236d1bcb8e617c0b1c2783b4a8bc478e18a86743d607 COPYING
+sha256 e912cf1e1c09b81d61c0154eb6c179588622c31ad07bfb4a90c612d07ff09d9b COPYING
sha256 ce3324c9f22299cfc7c281e5a6ab40fbe9c2ea1a67cee87226cb8cd39db1e1d2 GPL.txt
sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LGPL.txt
--
2.25.1
next reply other threads:[~2020-03-19 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 8:12 Chris Packham [this message]
2020-03-20 8:59 ` [Buildroot] [PATCH] package/syslog-ng: Update has for COPYING Chris Packham
2020-03-20 18:55 ` 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=20200319081228.26547-1-judge.packham@gmail.com \
--to=judge.packham@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