gstreamer1: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gst1-plugins-base: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gst1-plugins-good: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gst1-plugins-bad: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gst1-plugins-ugly: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gst1-libav: bump version

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
chrony: bump version

And add hash file.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
busybox: bump to version 1.23.0

Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
gdb: bump to 7.8.1

This commit bumps to 7.8.1, and updates the logic to use .tar.xz
tarballs so that it applies to all 7.8.x versions.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
freerdp: pass appropriate ARM ABI flags

In the line of commit 530693787b3 ("package/freerdp: do not use Neon
extensions when not available") done by Yann E. Morin, freerdp also
passes an explicit -mfloat-abi= flag, and defaults to softfp. This
obviously breaks badly when building an EABIhf system.

This commit therefore fixes freerdp.mk to pass the appropriate
ARM_FP_ABI value to freerdp's build system.

Fixes:

  http://autobuild.buildroot.org/results/6ca/6ca9de1a11c675533baa68f7a6bf7b6af7cb4345/

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/mke2img: always create sparse files

When the user specifies a number of blocks (and we do not auto-compute
them), the generated filesystem can be quite large with large zones with
only zeroes in them.

Thus, always create the filesystem as a sparse file.

Sparse files behave the same as normal files, except those long runs of
zeroes do not actually use space on the (host) filesystem. Also, this
should not break current behaviour, as neither cp nor dd nor cat preserve
sparseness by default. So users relying on the zeroed parts to actually
be written won;t see a change. Users that were expressly using cp or dd
to copy files to a sparse destination will however see a little bit of
improvements, as the zeroed out parts won't even be read from disk.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Samuel Martin <s.martin49@gmail.com>
Tested-by: Karoly Kasza <kaszak@gmail.com>
Reviewed-by: Karoly Kasza <kaszak@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>