net/mtr broken without ipv6
Hi. I build my custom kernel without IPv6 since I'm not going to be using it any time soon. The mtr port doesn't work anymore, no matter what I try. It was built with and without the IPv6 option checked in 'make config' and I tried with the -4 option so it shouldn't even be using IPv6. I always get: Unable to allocate IPv6 socket for nameserver communication: Protocol not supported What can I do to fix this without enabling a useless (to me) option in my kernel and rebuilding? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
On Fri, May 24, 2013 at 2:47 PM, wrote: > Hi. I build my custom kernel without IPv6 since I'm not going to be using > it any time soon. The mtr port doesn't work anymore, no matter what I try. > It was built with and without the IPv6 option checked in 'make config' and > I tried with the -4 option so it shouldn't even be using IPv6. I always > get: > > Unable to allocate IPv6 socket for nameserver communication: Protocol not > supported > > What can I do to fix this without enabling a useless (to me) option in my > kernel and rebuilding? > > This sounds like a potential bug in upstream software. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
> I build my custom kernel without IPv6 since I'm not going to be using > it any time soon. The mtr port doesn't work anymore > What can I do to fix this without enabling a useless (to me) option in my > kernel and rebuilding? Downgrade the mtr port to mtr-nox11-0.82_1. I update ports tree with `portsnap` and use `svn export` (devel/subversion port) for downgrading a single port. How to learn the revision for downgrading: svn log svn://svn0.us-east.freebsd.org/ports/head/net/mtr | less How to downgrade: rm -rf /usr/ports/net/mtr svn export -r r300897 svn://svn0.us-east.freebsd.org/ports/head/net/mtr /usr/ports/net/mtr portupgrade -f mtr\* ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
On Sat, May 25, 2013 at 5:21 AM, wrote: > > I build my custom kernel without IPv6 since I'm not going to be using > > it any time soon. The mtr port doesn't work anymore > > > What can I do to fix this without enabling a useless (to me) option in my > > kernel and rebuilding? > > Downgrade the mtr port to mtr-nox11-0.82_1. > I update ports tree with `portsnap` and use `svn export` > (devel/subversion port) for downgrading a single port. > How to learn the revision for downgrading: > > svn log svn://svn0.us-east.freebsd.org/ports/head/net/mtr | less > > How to downgrade: > > rm -rf /usr/ports/net/mtr > svn export -r r300897 > svn://svn0.us-east.freebsd.org/ports/head/net/mtr/usr/ports/net/mtr > portupgrade -f mtr\* > I don't see how downgrading will fix it unless this is a newly introduced bug, however you can also use ports-mgmt/portdowngrade. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
> > > I build my custom kernel without IPv6 since I'm not going to be using > > > it any time soon. The mtr port doesn't work anymore > > Downgrade the mtr port to mtr-nox11-0.82_1. > > I update ports tree with `portsnap` and use `svn export` > > (devel/subversion port) for downgrading a single port. > I don't see how downgrading will fix it unless this is a newly introduced > bug It is. 0.82 works, 0.84 doesn't. https://bugs.launchpad.net/mtr/+bug/1130561 > however you can also use ports-mgmt/portdowngrade. portdowngrade also uses subversion, but not "export". I suspect that combination of portdowngrade with portsnap can cause problems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
On Sat, May 25, 2013 at 9:32 AM, wrote: > > > > I build my custom kernel without IPv6 since I'm not going to be using > > > > it any time soon. The mtr port doesn't work anymore > > > > Downgrade the mtr port to mtr-nox11-0.82_1. > > > > I update ports tree with `portsnap` and use `svn export` > > > (devel/subversion port) for downgrading a single port. > > > I don't see how downgrading will fix it unless this is a newly introduced > > bug > > It is. 0.82 works, 0.84 doesn't. > https://bugs.launchpad.net/mtr/+bug/1130561 > > Good to see they are aware of it, and seeking a fix. > > however you can also use ports-mgmt/portdowngrade. > > portdowngrade also uses subversion, but not "export". > I suspect that combination of portdowngrade with portsnap can cause > problems. > > Nothing has changed between cvs and svn. It is my understanding, and findings, that portsnap doesn't care either way and will clobber any changes that don't match the distributed portsnap snapshots. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
(I'm not subscribed to this list so keep me CC'd) Re: http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083766.html I've already discussed this before -- with you in fact -- and did the full analysis. Users should read it in full: http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/082144.html I also CC'd the port maintainer on that Email, who did not respond. Proof of that: > From: Jeremy Chadwick > To: s...@tormail.org > Date: Fri, 15 Mar 2013 21:32:14 -0700 > Cc: sunp...@freebsd.org, freebsd-ports@freebsd.org > Subject: Re: net/mtr failed to build I am now CC'ing portmgr@ due to negligence. FreeBSD Ports Management Team: Please read my analysis (March mail above). TL;DR version: This port needs to be reverted to 0.82. I will not mince words: mtr 0.84 is a complete clusterfuck on all BSDs, including OS X. It should be nuked from orbit. As stated in my March Email, while there are fixes in the official mtr github repo for all of this nonsense, but figuring out which fixes/commits is time-consuming and honestly not worth it given the massive scale of breakage (as I said, it affects all BSDs). Please see that this port is rolled back to 0.82 (specifically reverting r213277). I believe PORTREVISION should also be set to 2 when rolling back, because there have been other Makefile changes between 0.82 PORTREVISION=1 and now (specifically r316355). Verification: http://svnweb.freebsd.org/ports/head/net/mtr/Makefile?r1=300897&r2=314277 http://svnweb.freebsd.org/ports/head/net/mtr/Makefile?r1=314277&r2=316355 Thank you. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/mtr broken without ipv6
On Sat, May 25, 2013 at 11:40:05PM -0700, Jeremy Chadwick wrote: > Please see that this port is rolled back to 0.82 (specifically reverting > r213277). I believe PORTREVISION should also be set to 2 when rolling > back, because there have been other Makefile changes between 0.82 > PORTREVISION=1 and now (specifically r316355). Verification: You know what pisses me off more than the mtr authors not properly testing their software on all platforms before release? When I somehow completely botch SVN revision numbers. :/ The first line of my quoted paragraph SHOULD have read: "Please see that this port is rolled back to 0.82 (specifically reverting r314277 / rolling back to r300897)." -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
