summaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity/avahi/avahi_0.7.bb
AgeCommit message (Collapse)Author
2021-05-14avahi: Exclude CVE-2021-26720 from cve-checkRichard Purdie
Issue only affects Debian and SUSE. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 72522fa1a5f3b9b2855043fe6b421886d641385f) Signed-off-by: Steve Sakoman <steve@sakoman.com>
2020-07-13avahi: Fix typo in recipeChristian Eggers
According to the PACKAGES variable, LICENSE_avahi-client is misspelled. Additionally, the libavahi-client package actually only includes LGPLv2.1+ software (as opposed to the global LICENSE variable). Signed-off-by: Christian Eggers <ceggers@arri.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d8837b4735b5e96ae0f5542319e711dbda8c3849) Signed-off-by: Steve Sakoman <steve@sakoman.com>
2020-03-29avahi: add LICENSE for individual packagesMatthew
Fixes [YOCTO #13609] avahi_0.7.bb defines 9 PACKAGES. However, avahi.inc generically sets LICENSE to "GPLv2+ & LGPLv2.1+". The library specific packages should be LGPLv2.1+ only. Signed-off-by: Matthew Zeng <matthew.zeng@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-08avahi: avoid depending on skipped packageJens Rehsack
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 Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-27avahi: fix error at boot time for avahi-daemon.serviceChen Qi
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. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-06-27avahi: reorganize codesChen Qi
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. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-01-02avahi: upgrade to 0.7Dengke Du
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. Signed-off-by: Dengke Du <dengke.du@windriver.com> Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>