mDNSResponder has released way newer releases than our current port. see: https://github.com/apple-oss-distributions/mDNSResponder/tags Maybe one is willing to upgrade the port to mDNSResponder-1790.80.10? regards
Hi, maintainer here, Yeah, I was kind of hoping to get some feedback on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256955 to transform this port in a pseudo-slave port to avoid running behind net/mDNSResponder like that... If this looks too much to review, let's just bump again the version number, the base mdns code is quite stable, as is FreeBSD nsswitch api, so it's always just PORTVERSION/distinfo update.
(In reply to Matthieu Volat from comment #1) Let's wait for sunpoet@ opinion on slave port #256955 Cheers
dns/mDNSResponder does not exist in the tree, should this report be for dns/mDNSResponder_nss or for net/mDNSResponder?
This is for dns/mDNSResponder_nss, the base port is up to date. Maybe let's have a timeout for progress on #256955 to 2023/02/26? #256955 can still happen on a more up-to-date port.
Ho... Since things went without an update to 256955, I went on to create a patch simply updating dns/mDNSResponder_nss... Which when I finaly realized that net/mDNSResponder is *not* up to date (Apple went on a release frenzy it seems). Here's my proposal: I can post patches to update dns/mDNSResponder_nss to 1790.80.10. Since this module do not need any newer API than the last one, it even works against current port net/mDNSResponder. We can enlarge the scope of this PR to include net/mDNSResponder, if sunpoet@ has no time, I can have a pass at proposing also a patch for this one. When net/mDNSResponder patch is submitted/approved, I can optionaly run another dns/mDNSResponder_nss test, but I'm 99.999% confident it's not needed. Then both ports can be updated. Slave port issue can wait for a bit. Would that be a good way to proceed?
Created attachment 240500 [details] dns/mDNSResponder_nss : update to 1790.80.10
Created attachment 240501 [details] dns/mDNSResponder_nss : poudriere testport log
Created attachment 240808 [details] net/mDNSResponder : update to 1790.80.10 Hi, Sorry this took more than a week, but I rebased the current patches on top of mDNSResponder 1790.80.10 and added a new one to handle a objective-c declaration that slipped in the code. From my usage of this ports, things works -- both for the base usage and in conjonction with dns/mDNSResponder_nss for direct hostname resolution, for ipv4 and ipv6. This patch must be accepted by sunpoet@ (maintainer), if done both patchs can be included at the same time. Regards,
Created attachment 240809 [details] net/mDNSResponder : poudriere testport log Poudriere testport log file.