[adam%netbsd.org@localhost: CVS commit: pkgsrc]

[Joerg Sonnenberger <joerg%bec.de@localhost>]

----- Forwarded message from Adam Ciarcinski <adam%netbsd.org@localhost> -----

Date: Wed, 6 May 2020 13:33:53 +0000
From: Adam Ciarcinski <adam%netbsd.org@localhost>
To: pkgsrc-changes%NetBSD.org@localhost
Subject: CVS commit: pkgsrc
Reply-To: adam%netbsd.org@localhost

Module Name:	pkgsrc
Committed By:	adam
Date:		Wed May  6 13:33:53 UTC 2020

Modified Files:
	pkgsrc/devel/boost-build: PLIST buildlink3.mk
	pkgsrc/devel/boost-headers: PLIST buildlink3.mk
	pkgsrc/devel/boost-jam: buildlink3.mk
	pkgsrc/devel/boost-libs: Makefile PLIST buildlink3.mk
	pkgsrc/devel/boost-mpi: PLIST buildlink3.mk
	pkgsrc/devel/py-boost: PLIST buildlink3.mk
	pkgsrc/meta-pkgs/boost: Makefile.common distinfo
	pkgsrc/meta-pkgs/boost/patches: patch-boost_archive_basic__archive.hpp
	    patch-boost_thread_pthread_thread__data.hpp
Removed Files:
	pkgsrc/meta-pkgs/boost/patches:
	    patch-boost_asio_detail_impl_kqueue__reactor.ipp

Log Message:
boost: updated to 1.73.0

----- End forwarded message -----

So this is yet another boost update breaking various packages. Can we
please adopt a pre-commit test policy for updates that HAVE A KNOWN
HISTORY OF BREAKING SHIT and prepare the necessary follow-up patches in
advance? It's really frustrating that after spending hours to remove
100+ build failures, anothers dozen+ are added without any need other
than a commit-first-fix-later behavior.

Joerg