tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: [ CVS commit: pkgsrc]

On Sat, 9 May 2020, 16:08 Joerg Sonnenberger, <> wrote:
----- Forwarded message from Adam Ciarcinski <> -----

Date: Wed, 6 May 2020 13:33:53 +0000
From: Adam Ciarcinski <>
Subject: CVS commit: pkgsrc

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

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

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.

Woule there any sense in having a comment in the boost Makefile with a list of key packages to test after an update? 

Home | Main Index | Thread Index | Old Index