Date: Sat, 25 May 2013 10:00:19 -0700 From: Jason Helfman <jgh@FreeBSD.org> To: Lena@lena.kiev.ua Cc: Jason Helfman <jgh@freebsd.org>, FreeBSD Ports List <freebsd-ports@freebsd.org>, sib@tormail.org Subject: Re: net/mtr broken without ipv6 Message-ID: <CAMuy=%2BiVhfN3pPiorWjezF18L6=d%2BXR4UKnojdxszS0kAMAEag@mail.gmail.com> In-Reply-To: <20130525163240.GE2499@lena.kiev> References: <mailman.1.1369483200.20460.freebsd-ports@freebsd.org> <1Ufzpx-0001gW-K7@internal.tormail.org> <20130525122108.GA2499@lena.kiev> <CAMuy=%2BhK-JtH1P0473f_q0VJPFZyAW6ASyZxxek6Vs6aZOUfZw@mail.gmail.com> <20130525163240.GE2499@lena.kiev>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 25, 2013 at 9:32 AM, <Lena@lena.kiev.ua> 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 jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMuy=%2BiVhfN3pPiorWjezF18L6=d%2BXR4UKnojdxszS0kAMAEag>