Date: Tue, 27 Aug 2013 06:39:49 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: ports-announce@FreeBSD.org, FreeBSD Ports <ports@FreeBSD.org> Subject: [FreeBSD-Ports-Announce] [HEADS UP] Maintainers will receive emails about their ports failing to build Message-ID: <521C9005.10209@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QGSNTgsVt3P4W7KeAcBaP6r8qNSx6sIP5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi porters, FreeBSD 10 is fast approaching and many ports fail to build due to clang and other changes in HEAD. Not all maintainers are aware their ports fail to build. In the past we have manually sent failing build logs to maintainers and committers. Starting September 4th, we will start automatically sending weekly failing port build logs directly to maintainers. The emails are trimmed in the middle so you do not receive multi-MB emails. It will have a link at the top for the full log. Mailing list maintainers will not be receiving these emails. If you do not want to maintain a port anymore, please just open a PR to release it at http://www.freebsd.org/send-pr.html, but we encourage you to stay involved :) You can get ahead of this by fixing your ports before September 4th by checking http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/2013-August/thread= =2Ehtml We are building up the infrastructure and tools to handle weekly automated builds of PkgNG packages. Part of this effort has been to increase visibility of broken ports by posting failed build logs to pkg-fallout@FreeBSD.org. This only works if you are following the list and happen to see your port fly by in the flood of emails. The advantage of the FreeBSD build cluster is that we have the scope of testing the port on all supported FreeBSD branches and multiple architectures. You can do this yourself as well with www.redports.org. If a port is failing on an architecture that it is not designed for, use ONLY_FOR_ARCHS/NOT_FOR_ARCHS to exclude it from building on that arch. It is reasonable to open a PR to mark a port as BROKEN as well as you seek a solution. Preferably only BROKEN on the release/arch it fails to build on. It is also reasonable to poke ports@ if your PR is not getting enough attention. Thank you for all your work, Bryan Drewery on behalf of portmgr@ --QGSNTgsVt3P4W7KeAcBaP6r8qNSx6sIP5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSHJAFAAoJEG54KsA8mwz5r60P/AjrJLJ4+37skIazIg5Gd6Ek 3Zlx8r0n2KUpgJOR2K/AsW2MMr5n1ioafM2RYWTaSEsSjr2M6Os7eRj7CuM/GXhR qKAh95so9CK+1Dq9Zx7h9WxdZn19tSBzC0phL9XMSnC4cH8BbOjup2Xdq+Id+tBv wLVdRdRiyZIOV+OBduEKGhhS5ghWTTQvLeUIDg5iCu0LYyB7YNlSz8QgssqdQhuu 0MbJ3YppOVbsWXPtLf8/ZhLjC8GZQSN5Hq6kmWf5jgtLdtIpyyF4vPgqQvabkEGv 88+TYyLMKlNgXmbLag2yzL5hZbltIbUMw2VjNEOiorbrWv2X2exguwj8AS+bOrYB k9tm+ApjO6nS01nbFzv25y4oMkZo53sCTKt5Ayi2RnC1L6d9ve+AO2bdlG+5zFJq YYVXNqMYd7v71eH+HzNFvhy2/vl2YTmYDLer1S8AaDQAsNbFAPc7dWw3X4iJ78Lz 6Z+UkItvToMNdL/+p5OYnhUNyPPavGbEgfAKJwwPfdmdsaG4NJRF0SP7u+eyAzi1 cSInrJjSJ3YRcNnqH5RncdU9HF3yS2l2S7rpDS7sdFk0f9Vke1XrCPdxgfQWLjGj lXyo31Lvu5ZlaAMIrv+ScjBlawMDNGvN16rOhAcCXSgIpQOL1j7iYurA9/BBYAst QVp11MmSE6BxYDAoOuKd =dNoG -----END PGP SIGNATURE----- --QGSNTgsVt3P4W7KeAcBaP6r8qNSx6sIP5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?521C9005.10209>