linux/poky.git/meta/recipes-connectivity/avahi, branch warrior

avahi: fix CVE-2017-6519

2019-04-03T13:50:13+00:00

Backport patch to fix CVE-2017-6519. CVE: CVE-2017-6519 (From OE-Core rev: 979e3f4ac1e12228d368315169a32d5ab0209e91) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

avahi: avoid depending on skipped package

2018-12-08T17:17:01+00:00

When built without D-Bus, libavahi-client is not build: Building libavahi-client: no (You need avahi-daemon and D-Bus!) which causes avahi-dev RDEPENDS failing when creating an image containing development-tools: * - nothing provides libavahi-client = 0.7-r0 needed by avahi-dev-0.7-r0.cortexa8hf-neon (From OE-Core rev: 319532792435be73e96c8319e90336e1298ac2a1) Signed-off-by: Jens Rehsack Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: fix error at boot time for avahi-daemon.service

2018-06-27T12:55:21+00:00

The following error messages appear now and then at boot time. avahi-daemon/chroot.c: open() failed: No such file or directory Failed to open /etc/resolv.conf: Invalid argument The problem is about /etc/resolv.conf. In Yocto's systemd based systems, it's a symlink to /etc/resolv-conf.systemd which in turn is a symlink to /run/systemd/resolve/resolv.conf. The systemd-resolved service handles creation of /run/systemd/resolve/resolv.conf file. So if avahi-daemon is started before systemd-resolved, the error messages appear. Fix this problem by making avahi-daemon start after systemd-resolved. (From OE-Core rev: 647db1d9eb65b225ffbb6953f796232026bfa935) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: reorganize codes

2018-06-27T12:55:21+00:00

This patch does nothing but reorganizing codes. avahi.inc is shared by avahi and avahi-ui recipes. Move common things into it, and move uncommon things out of it. (From OE-Core rev: 75529d384bfeaf52befccb892cf41f22dc02668b) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: refresh patches

2018-03-11T13:27:00+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 6c0329389ffd82552c9302d70c8b2a1dfc94ce00) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: remove explicit avahi-dev RDEPENDS

2018-01-11T10:26:06+00:00

These were added to the avahi-dev package back in 2011 before avahi-ui existed at all. The problem of GTK+ being pulled in via avahi-dev was finally solved with the avahi-ui split, so these explicit (and by being manually maintained, incomplete) dependencies can be removed. This also results in gettext-dev being removed from the dependency tree (the gettext library API is provided by glibc/musl), which means that for a standard image we don't need to build target gettext at all anymore. (From OE-Core rev: 00ae3e03185f1044f3610dc7ba7da7bd3beb868a) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: upgrade to 0.7

2018-01-02T17:24:37+00:00

Delete the unneeded patch, because the upstream contains the needed changes. The new version of avahi 0.7 use "/run" directory to place some run-time variable data, not /var/run, so in avahi.inc, we should remove the "/run" not "/var/run". Remove PACKAGECONFIG for pygtk which already dropped in upstream. (From OE-Core rev: 80b408ae48eb091fc2af8b1570a7aac3cdc0b009) Signed-off-by: Dengke Du Signed-off-by: Yi Zhao Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi-ui: reduce local pending patches

2017-07-06T13:38:15+00:00

[Yocto #11548] (From OE-Core rev: 9e18fc1aa4aa0ead854bb4e02eb3af2e7909f597) Signed-off-by: Dengke Du Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: Drop remnants of uclibc support

2017-06-22T08:16:00+00:00

uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd) Signed-off-by: Richard Purdie

avahi: Don't remove users/groups in postrm

2016-11-04T12:50:54+00:00

There's no way to ensure that files owned by the users aren't left on the system at postrm time: Removing the user would mean those files are now owned by a non-existing user, and later may be owned by a completely unrelated new user. [YOCTO #10442] (From OE-Core rev: c1be2196e7ffb23b7b243ecd8aca1827cbdfa443) Signed-off-by: Jussi Kukkonen Signed-off-by: Richard Purdie