Commit Graph

3 Commits

Author SHA1 Message Date
Heiko Thiery
8a3a5a27c1 package/j*: add license file hashes
Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-03 14:44:53 +01:00
Victor Huesca
69808c7536 package: remove 'v' prefix from github-fetched packages
On Github, a large number of projects name their tag vXYZ (i.e v3.0,
v0.1, etc.). In some packages we do:

 <pkg>_VERSION = v0.3
 <pkg>_SITE = $(call github foo,bar,$(<pkg>_VERSION))

And in some other packages we do:

 <pkg>_VERSION = 0.3
 <pkg>_SITE = $(call github foo,bar,v$(<pkg>_VERSION))

I.e in one case we consider the version to be v0.3, in the other case
we consider 0.3 to be the version.

The problem with v0.3 is that when used in conjunction with
release-monitoring.org, it doesn't work very well, because
release-monitoring.org has the concept of "version prefix" and using
that they drop the "v" prefix for the version.

Therefore, a number of packages in Buildroot have a version that
doesn't match with release-monitoring.org because Buildroot has 'v0.3'
and release-monitoring.org has '0.3'.

Since really the version number of 0.3, is makes sense to update our
packages to drop this 'v'.

This commit only addresses the (common) case of github packages where
the prefix is simply 'v'. Other cases will be handled by separate
commits. Also, there are a few cases that couldn't be handled
mechanically that aren't covered by this commit.

Signed-off-by: Victor Huesca <victor.huesca@bootlin.com>
[Arnout: don't change flatbuffers, json-for-modern-cpp, libpagekite,
 python-scapy3k, softether]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-06-19 22:27:55 +02:00
Peter Korsgaard
d3af1257fc jquery-keyboard: add .hash file
Fixes:
http://autobuild.buildroot.org/results/d75/d7500f7e063b94e9991bacfd1df9fa5aa1967db0/
http://autobuild.buildroot.org/results/f48/f485ee75ec4c9b87f17b8b8dc1898590045474b4/

For some odd reason, the file on the autobuilder ended up getting prefixed
by these 7 bytes:

00000000  31 62 30 31 61 0d 0a 1f  8b 08 00 00 00 00 00 00  |1b01a...........|

And suffixed by these 7 bytes:

0001b020  00 0d 0a 30 0d 0a 0d 0a

Which then caused gzip to fail to extract it. It is not clear to me how this
could happen (Github glitz?  It looks suspiciously like HTTP/1.1 chunked
encoding going wrong, E.G.  0x1b01a = 110618 = tarball size) - but adding a
.hash file fixes it as the corruption gets detected and we fall back to our
s.b.o mirror.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-06-15 20:20:39 +02:00