Date: Tue, 28 Jun 2016 16:19:52 +0200 From: John Marino <freebsd.contact@marino.st> To: Ruslan Makhmatkhanov <rm@FreeBSD.org>, marino@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r416822 - head/multimedia/libmediaart Message-ID: <551e7725-b26b-21f1-1fab-4663e72e8be1@marino.st> In-Reply-To: <2892fa80-46cd-882c-01b1-b6ffbed03e0b@FreeBSD.org> References: <201606122049.u5CKnJNs048675@repo.freebsd.org> <69e47339-0d65-65f7-5cd1-81d44c3140d5@marino.st> <2892fa80-46cd-882c-01b1-b6ffbed03e0b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/28/2016 16:11, Ruslan Makhmatkhanov wrote: > I'll check it out later today. May be my tree was borked in some way at > the moment of test. As for PORTREVISION bump, AFAIK it is not required > when port is broken and it really was from my poudriere point of view. I think that's only true if the port doesn't build at all and never did. The port was building regardless of the validity of the pkg-plist. At least for DF, it wasn't broken (and in fact was perfectly correct). Hopefully some gracious third party will run this through their poudriere so we can determine if your ports tree is the culprit or not. Or maybe somebody else can confirm it was broken. I don't recall seeing any breakage on FreeBSD though. JOhn --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551e7725-b26b-21f1-1fab-4663e72e8be1>