net/mDNSResponder fails to install package Fix: --------- http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/net/mDNSResponder/files/ I request MAINTAINER= sunpoet@FreeBSD.org to please review this patch. I dont know if it is correct from a run time view, as I don't know mDNSResponder, for me its just a dependency built by kdirstat. Without this patch, on a src=9.0-RELEASE based system, with ports both from 9.0-RELEASE & current (2012-06-16) mDNSResponder will not even make install package. Before my jhs patch: ls -l /usr/local/etc/rc.d/mdn* Just: /usr/local/etc/rc.d/mdnsd* How-To-Repeat: cd /usr/ports/net/mDNSResponder ; make install package /usr/local/etc/rc.d/mdns.sh: not found
Responsible Changed From-To: freebsd-ports-bugs->sunpoet Over to maintainer (via the GNATS Auto Assign Tool)
State Changed From-To: open->feedback I can't reproduce the problem. I just built this port successfully on my 9-STABLE amd64. You can see the log at [1]. ${PREFIX}/etc/rc.d/mdnsd was not installed by the port itself. It was done by bsd.port.mk via USE_RC_SUBR=mdnsd knob. The code is around bsd.port.mk line 5812 to 5819. And the rc.d script should not end with .sh now. Please recheck your ports tree, esp. bsd.port.mk. Thanks. [1] http://people.freebsd.org/~sunpoet/mDNSResponder-333.10.log http://www.freebsd.org/cgi/query-pr.cgi?pr=169109 Date: Sat, 16 Jun 2012 02:29:57 +0200
Hi sunpoet@, Ref: http://www.freebsd.org/cgi/query-pr.cgi?pr=169109 http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/net/mDNSResponder/files/ http://people.freebsd.org/~sunpoet/mDNSResponder-333.10.log > To: sunpoet@FreeBSD.org > Subject: net/mDNSResponder /usr/local/etc/rc.d/mdns.sh: not found > From: "Julian H. Stacey" <jhs@berklix.com> > Date: Fri, 15 Jun 2012 15:02:17 +0200 > > Hi > I keep seeing > /usr/local/etc/rc.d/mdns.sh: not found > from > cd /usr/ports/net/mDNSResponder ; make install package > also with current ports > src=8.3-RELEASE > Any ideas ? > Cheers, > Julian > From: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> > Date: Sat, 16 Jun 2012 00:14:09 +0800 > Subject: Re: patch as net/mDNSResponder fails to install > To: "Julian H. Stacey" <jhs@berklix.com> > Cc: FreeBSD-gnats-submit@FreeBSD.org > > Hi, > > I can't reproduce the problem. > I just built this port successfully on my 9-STABLE amd64. > You can see the log at [1]. > ${PREFIX}/etc/rc.d/mdnsd was not installed by the port itself. > It was done by bsd.port.mk via USE_RC_SUBR=mdnsd knob. > The code is around bsd.port.mk line 5812 to 5819. > And the rc.d script should end with .sh now. > Please recheck your ports tree, esp. bsd.port.mk. > Thanks. > [1] http://people.freebsd.org/~sunpoet/mDNSResponder-333.10.log > Regards, > sunpoet > From sunpoet@FreeBSD.org Fri Jun 15 20:15:08 2012 > Date: Fri, 15 Jun 2012 18:10:11 GMT > To: jhs@berklix.com, sunpoet@FreeBSD.org, sunpoet@FreeBSD.org > From: sunpoet@FreeBSD.org > Subject: Re: ports/169109: patch as net/mDNSResponder fails to install > Synopsis: patch as net/mDNSResponder fails to install > State-Changed-From-To: open->feedback > State-Changed-By: sunpoet > State-Changed-When: Fri Jun 15 18:00:19 UTC 2012 > State-Changed-Why: > I can't reproduce the problem. I just built this port successfully on > my 9-STABLE amd64. You can see the log at [1]. > ${PREFIX}/etc/rc.d/mdnsd was not installed by the port itself. It was > done by bsd.port.mk via USE_RC_SUBR=mdnsd knob. The code is around > bsd.port.mk line 5812 to 5819. And the rc.d script should not end with > sh now. > Please recheck your ports tree, esp. bsd.port.mk. Thanks. > [1] http://people.freebsd.org/~sunpoet/mDNSResponder-333.10.log > http://www.freebsd.org/cgi/query-pr.cgi?pr=169109 > To: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> > cc: FreeBSD-gnats-submit@FreeBSD.org > Subject: Re: patch as net/mDNSResponder fails to install > From: "Julian H. Stacey" <jhs@berklix.com> > Date: Sat, 16 Jun 2012 02:29:57 +0200 > > Hi sunpoet > Thanks for your quick reply. > > Please recheck your ports tree, esp. bsd.port.mk. > OK. Sorry but that may take a minimum of 2 days, > as on rebooting, my host had some confusion between partitions > with 8.3 & 9.0 (I think I had a temporary 9.0 kernel on my 8.3 > based partition, & uname -r may have led to a ports install of 9.0 > I'm doing a rebuild of that host's 8.3 Then I can rebuild the > hosts other partition with 9.0 again. So it'll take a little while > to report back, Sorry ! > Meantime I saw no problem on another 8.3 box. > Cheers, > Julian OK, discarding errors I saw from my previously confused system ( An inadvertent 9 kernel, on an 8.3 base, now rectified ) I've been done tests on various hosts on unpatched ports/ With these I see no errors: 8.2-RELEASE src based & 8.2-RELEASE generic unpatched ports/ laph.js.berklix.net 8.3-RELEASE src based & 8.3-RELEASE generic unpatched ports/ blak.js.berklix.net 8.3-RELEASE src based & Current generic unpatched ports/ jhs@blak.js.berklix.net These errror: 9.0-RELEASE src based, + 9.0-RELEASE ports/ or current ports/ lapr.js.berklix.net 9 From make deinstall ; make clean ; make all ; make install Errors: /usr/local/etc/rc.d/mdns.sh: not found gmake: *** [/usr/local/sbin/mdnsd] Error 127 Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/
Hi, I cannot reproduce this error on a 9.0-RELEASE/amd64 tinderbox jail (w/ up-to-date ports tree). You can download the tinderbox log from http://people.FreeBSD.org/~sunpoet/tb-9-RELEASE-mDNSResponder-333.10.log. Since the script was installed by USE_RC_SUBR knob (defined in bsd.port.mk), please re-check your bsd.port.mk to see if it's unmodified. It would be great to provide build log from lapr.js.berklix.net. Thanks. Regards, sunpoet
Hi Sunpoet, Thanks for your response, sorry for delay, I (not machine) a bit ill (so if I've missed something in log, please say). > I cannot reproduce this error on a 9.0-RELEASE/amd64 tinderbox jail > (w/ up-to-date ports tree). To see the problem reported, you could also try the first environment send-pr reported, ie with src And ports tagged 9.0-RELEASE. http://www.freebsd.org/cgi/query-pr.cgi?pr=169109&cat=ports "Without this patch, on a src=9.0-RELEASE based system, with ports both from 9.0-RELEASE & current" However I today see it on both, thought seems to come & go, can't pin it down *** Differences exist between 9.0-RELEASE & today's ports current as listed http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/net/mDNSResponder/files/mail/2012_07_15.diffs Basically: < rcvar=`set_rcvar` > rcvar=mdnsd_enable However with latest current today I see the problem. It seems to be some sort of state machine problem. *** Something is or should be installing & not recognising something. ... but make rmconfig does nothing, so not that > You can download the tinderbox log from > http://people.FreeBSD.org/~sunpoet/tb-9-RELEASE-mDNSResponder-333.10.log. > > Since the script was installed by USE_RC_SUBR knob (defined in > bsd.port.mk), please re-check your bsd.port.mk to see if it's > unmodified. It would be great to provide build log from > lapr.js.berklix.net. Thanks. On lapr.js.berklix.org running based on src/ from 9.0-RELEASE, I installed new virginal trees of ports/ from both 9.0-RELEASE & current. I attach log at http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/net/mDNSResponder/files/mail/2012_07_15_log.txt Please let me know what extra commands you'd like me to run to chase this down. PS I had previously moved aside a whole load of stuff, after building many ports, so I had ls /usr/local/etc/rc.d MV/ apache22* htcacheclean* ls /usr/local/etc/rc.d/MV apache22* gkrellmd* nut_upsmon* avahi-daemon* gpsd* rsyncd* avahi-daemon.sh* hald* saned* avahi-dnsconfd* healthd* smartd* avahi-dnsconfd.sh* htcacheclean* snmpd* cupsd* linux_adobe* snmptrapd* dbus* mailman* svnserve* fetchmail* mbmon* vboxheadless* ffserver* mdnsd* vboxnet* fusefs* nut* wwwoffled* git_daemon* nut_upslog* & I can see there's a mdnsd in MV/ However: even though the name varies between mdnsd & mdnsd.sh /var/db/pkg Grep mdnsd ./mDNSResponder-333.10/+CONTENTS:sbin/mdnsd ./mDNSResponder-333.10/+CONTENTS:man/man8/mdnsd.8.gz ./mDNSResponder-333.10/+CONTENTS:@unexec rm -f %D/man/cat8/mdnsd.8.gz %D/man/cat8/mdnsd.8 %D/man/cat8/mdnsd.8.gz %D/man/cat8/mdnsd.8.gz.gz %D/man/cat8/mdnsd.8.gz.bz2 ./mDNSResponder-333.10/+CONTENTS:etc/rc.d/mdnsd ie no other port has anything to do with it, (not supplying or using) so it should be, but is not, self fixing after clean deinstall Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/
I have the same problem on 10-CURRENT r235528 with up-to-date ports tree. WITH_PKGNG=yes is set in /etc/make.conf. The proposed patch didn't fix the issue, while `touch /usr/local/etc/rc.d/mdns.sh && chmod +x /usr/local/etc/rc.d/mdns.sh` did. I had no time to investigate so the workaround was enough for me, but I'm ready to test anything you'll propose.
State Changed From-To: feedback->closed mDNSResponder has been updated to 379.38.1. Feel free to reopen PR if the problem persists. Thanks!