Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Jun 2016 16:58:46 +0200
From:      Mathieu Arnold <mat@FreeBSD.org>
To:        Dan Langille <dan@langille.org>
Cc:        FreeBSD Ports <freebsd-ports@freebsd.org>, brnrd@FreeBSD.org
Subject:   Re: 2016Q2 - no Mk/Uses/mysql.mk
Message-ID:  <988FA8093FFCEAC15BBC1315@ogg.in.absolight.net>
In-Reply-To: <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org>
References:  <EE9A3E9D-D222-41E5-95D3-31771EDA4E41@langille.org> <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--==========67672882EB9DFF985368==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+--On 28 juin 2016 10:30:10 -0400 Dan Langille <dan@langille.org> wrote:
|> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold <mat@FreeBSD.org> wrote:
|> 
|> 
|> 
|> +--On 27 juin 2016 17:22:56 -0400 Dan Langille <dan@langille.org> wrote:
|> | I've been working with the 2016Q2 branch with respect to FreshPorts.
|> | 
|> | I tried running make -V on branches/2016Q2 and it failed with:
|> | 
|> | Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk"
|> | line 1433: Cannot open /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk
|> | 
|> | It seems that recent changes to Mk also need to be backported to
|> | branches if there is a commit on that branch.
|> 
|> Well, no, people merging things are supposed to check what they are doing
|> and not commit stupid patches, which is the case here.
|> 
|> Which port has USES=mysql on 2016Q2 ?
| 
| Log:
|   MFH: r416066
| 
|   net-mgmt/cacti: 0.8.8g -> 0.8.8h
| 
| It appears to have already been fixed in Revision 416207:
| 
| - no USES=mysql allowed in the quarterly branch
| 
| re
| https://svnweb.freebsd.org/ports/branches/2016Q2/net-mgmt/cacti/Makefile?
| view=log
| <https://svnweb.freebsd.org/ports/branches/2016Q2/net-mgmt/cacti/Makefile
| ?view=log>
| 
| Ooops.  Sorry for the noise.  I'll look at the new commits on that port.
| I was analyzing commits which FreshPorts had difficulty processing.
| 
| Nothing to see here. Please move along...

Well, no, the noise is good, it should be reported to the committer that
did the commit, like other breakage are, so that said committer knows and
fixes the problem.

-- 
Mathieu Arnold
--==========67672882EB9DFF985368==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQJ8BAEBCgBmBQJXcpCmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz
QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IvS8P/2zdENc0yQYaMWDsmLlmNoru
3v8SZsmRN0fypcodrEyWXO/s//orrzhLjCf/bUgizzlPG2RLo+iQbXABg2+Vmcfb
EIhnE4YI7wIH9THoYB3Iao4MLxMSr35Bk17xx3ka/xhPpYz0M62KWfYMGX2AC898
FuCZDzebTp6ryyFpcZZKYzrA738IlkUt+UwTj70ZmhGypkrNwVcrRuZp1C/v1emY
kibSSlSJkWi1mLcLiSqaM+Acw1K3VIRoh37oY45q1DDdkKz0GRreiYOCjffpZwGl
zbkP8Nqh6D/iGzMRd7en/CLjjlYmNclneuCbPS0s2au9Uf+23VU8V7QW7TI4Q347
vmMYNmWD/4fjM1IjJXVHBpWqxF1qZJBmJ1PxJ/HbSuZ6begXN7gY2IU7CNHa/Plp
TCtxByNG8RCvb32dm9uUcBEDCD+fBmvXqVbs3jd3z6/bk4ErPplrKCIe4Vznywi+
0p3LmxsuxlNUHLKQ5jauCIT3/Y1Gw6e2jA/Admk1gIdBtT65xg/gSZxijwRRoFfz
5zqju8RxZMRgU8YZ+3lCcwd+q1eukrL4f+xXoMIBY0CIdNBTRQMFIywHcWQ7EUOD
COAkpHThcICh3003yx/wJgokmdboLBg6hlWchgZfxtKPyYpHAAXFX/vuvIjmUQnd
hGdYjWslI6LQa+OrS+qA
=9DtI
-----END PGP SIGNATURE-----

--==========67672882EB9DFF985368==========--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?988FA8093FFCEAC15BBC1315>