avahi-common: update avahi to resolve issue with 'invalid service type'
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @neheb @thess
Environment:
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='22.03.4'
DISTRIB_REVISION='r20123-38ccc47687'
DISTRIB_TARGET='ath79/nand'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 22.03.4 r20123-38ccc47687'
DISTRIB_TAINTS='busybox'
Packages were provided via gli-net
root@GL-XE300:~# opkg install avahi-utils
Installing avahi-utils (0.8-7) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/avahi-utils_0.8-7_mips_24kc.ipk
But I've now added https://downloads.openwrt.org/releases/22.03.4/packages/mips_24kc/packages/Packages.gz into the distfeeds which gets 0.8-8 (and has same issue)
Description:
There is a bug in avahi if it detects an invalid service then it (avahi-browse -a -r) just stops running with error:
avahi_service_browser_new() failed: Invalid service type
Issue: https://github.com/avahi/avahi/issues/212
PR: https://github.com/avahi/avahi/pull/523
It would be greatly appreciated if at least the fix above could be backported into Openwrt package. The main change is in avahi-common, but avahi-core is also changed.
Note there is a tag 0.9-rc1 Jan 30 2024, which includes other fixes.
https://github.com/avahi/avahi/commits/v0.9-rc1/
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the upstream Avahi issue #212 and pull request #523, then compare the requested changes in avahi-common with the related avahi-core changes. Check the OpenWrt package version and its 0.8-8 behavior; done means the invalid service type no longer stops avahi-browse -a -r, with the upstream fix appropriately backported.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100