buildroot/package/libseccomp/libseccomp.hash, branch 2016.08

libseccomp: bump version to 2.3.1

2016-08-02T19:38:52+00:00

Bump libseccomp version to 2.3.1 to enable power architectures. Signed-off-by: Judd Meinders Signed-off-by: Matt Weber Signed-off-by: Thomas Petazzoni

libseccomp: add .hash file

2016-06-16T06:40:35+00:00

Fixes: http://autobuild.buildroot.org/results/07f/07fecbce8ca4b0a69e86b93021df80dbc2c45497/ Similar to jquery-keyboard, it seems the libseccomp tarball on the autobuilder is corrupt. Fix it by adding a .hash file so it falls back to our s.b.o mirror. Signed-off-by: Peter Korsgaard

package/libseccomp: bump version to 2.2.0

2015-03-30T21:14:11+00:00

- change upstream URL, project moved to github - removed patches not needed anymore since project switched to autoconf - add newly supported platforms to Config.in [Thomas: - remove hash file, since we're fetching from github now.] Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

package: add hashes for SourceForge-hosted packages

2014-12-28T21:21:16+00:00

Since SourceForge sometimes serves us faulty tarballs, we can tons of autobuild failures: http://autobuild.buildroot.org/results/9fb/9fba5bf086a4e7a29e5f7156ec43847db7aacfc4/ http://autobuild.buildroot.org/results/6c8/6c837b244c45ac3b3a887734a371cd6d226cf216/ ... Fix that by adding hash files for all SourceForge-hosted packages (thos etht did not already have it). We normally prefer to use hashes published by upstream, but hunting them all one by one is a tedious task, so those hashes were all locally computed with a script that searched for SF-hosted packages, downloades the associated tarball, computed the hash, and stored it in the corresponding .hash file. Also, SF publishes sha1 hashes, while I used the stronger sha256, since sha1 is now considered to be relatively weak. Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Thomas Petazzoni Cc: Maxime Hadjinlian Cc: Richard Braun Cc: Nathaniel Roach Signed-off-by: Thomas Petazzoni