Some of them forgot to update MIRROR_HASH on version change, others
updated with wrong hash value. The new values were generated from
tarballs prepared by the newly introduced github-tarball download
methoded and confirmed consistent with those from sources.openwrt.org
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
Maybe we should use something other than -Os for this code anyway; it's
generally quite CPU-intensive.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Prometheus introduced some new conventions on how to name metrics.
Read here https://prometheus.io/docs/practices/naming/
This PR breaks compatibility with past versions, just like the officials
node exporter! 💥
Signed-off-by: Paul Spooren <mail@aparcar.org>
libusb-compat was still required by package but sane was already
builing and linking libusb-1.0. It was working because libusb-compat
requires libusb-1.0.
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
The files in ozwcp/ shouldn't be compressed as there's no gzip handling
for those.
Also enable Python support — since it can dynamically link with
libpython optionally, it's harmless to enable it. Those who want Python
plugins can use it. I still want lua-based hardware plugins though.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
qemu-nbd is used to 'mount' images to /dev/nbdX block devices, for
example, to manipulate a qcow2 image as a disk device
Signed-off-by: Mathew McBride <matt@traverse.com.au>
qemu-img is used for converting between different VM image types,
such as qcow2 to raw and vice versa.
Signed-off-by: Mathew McBride <matt@traverse.com.au>
gptfdisk is a gpt-aware disk partitioning tool. It can be used to
convert mbr partitioned disk to gpt and vice versa.
It supports reading GPT, MBR, and BSD disklabels.
Signed-off-by: Alif M. Ahmad <alive4ever@live.com>
Some releases may have non letters in it's name currently resulting in
an empty ("") output which is then discarded, resulting in *missing*
labels in the metric.
Now it uses `.-` to catch as little as possible, but anything.
Signed-off-by: Paul Spooren <mail@aparcar.org>
The configure scripts for lvm2 guess defaults for run/lock based on if
/run exists on the build host. Use explicit values for the defaults
for consistency across build hosts.
Signed-off-by: Jeremiah McConnell <miah@miah.com>
By default bluez allows the printing subsystem to communicate
via dbus. This refers to the group lp which isn't available
on OpenWrt and makes dbus fail to start.
Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
crconf hasn't released any new version since 2012 or so.
And there are quite a few updates in the repo, including newer kernel
support.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Dotnet module added as a compile time option.
The dotnet module allows you to create more fine-grained rules
for .NET files by using attributes and features of the .NET file format.
http://yara.readthedocs.io/en/latest/modules/dotnet.html
Signed-off-by: Ashkan Jazayeri <ashkan@jazayeri.net>
Libmagic dependency replaced with File so Yara magic module can
make use of magic patterns.
magic.mgc is installed on the target only when the File package
is selected.
Signed-off-by: Ashkan Jazayeri <ashkan@jazayeri.net>
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
This makes quite a significant difference to the executable size:
text data bss dec hex filename
7921421 87804 31692 8040917 7ab1d5 domoticz
5862321 86180 31212 5979713 5b3e41 domoticz-lto
As an added bonus, it still seems to work.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
