2016Q2 - no Mk/Uses/mysql.mk

[Bernard Spil]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2016-06-28 16:58, Mathieu Arnold wrote:
> +--On 28 juin 2016 10:30:10 -0400 Dan Langille <dan at langille.org> wrote:
> |> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold <mat at FreeBSD.org> wrote:
> |>
> |>
> |>
> |> +--On 27 juin 2016 17:22:56 -0400 Dan Langille <dan at 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.

Just lucky that it wasn't me. Good thing to keep in mind with these
kinds of changes! Usually only the actual update is committed, not a
check for these kinds of changes to the ports framework!

I've got some Python patches in review that now have USES= ssl which
would break in Q2 as well! Luckily no security fixes in there afaik.

Cheers,

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

iQIcBAEBAgAGBQJXctaeAAoJEHT7/r+FArC0rzsP/jx32UsjVtA8dgYHCf+gM7mt
gz55FCOT7XI+m13nAZWpI3VfsW2MuA99j/B/npXMfDSqixGSDfZyFq0Xr+MPP9UU
b48TGrXbEUVQvkG4dRy5WK/J0XcqwO2x+ajD29lJtHZE/2aTMrBoXRYYifQkx0ew
iDftQDlauGp8usNjgAVrZffRkj0q0v2cQGcepL8iqHuKXA63b9dsxV65BeIUFLPE
hnL+AneFqiaXa9zSc72/o3PS173Y8d3XaSxPjw4pRBBuD4mDDadAdebUz/ZCVwug
k6g+LsVs+iqjn8nq1O6wgqJHh7LKLU04WGSPYHSUl7ErzmBOlxKJleFM3gOur2Og
9qy/dLwvftlNtEZ/8aI00ZVcKd4kzyoYZxa215g3A+vd+zDOTSPOWE3VgNoyf4KK
NHrKkrKH3f7/5um4RBuJf69lFs1X7RNuPPCXONnO1t3xDDOeOFAseKrQodDqfTo2
nC9X/Kf1cHi/wU9aF0DqttJj10fXdjbkthcKlSZ+dwk6p+wEEwLorbXrGI00f/aG
R6UFa5XhdQxkBYGiBKwPaNTEsNoGo0BhK48z5oknt9rv6Psm8C7Sa99euCVFMxqY
FftKkp3Iy731AnrApWkzaDd9CNtkvomhYZklx1rG/cqOq+0Xz+clFV1BADSZS2T1
Bd+0Wkqzm5WA7FDgjNOP
=WchY
-----END PGP SIGNATURE-----