Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: 5eeb04142bb69426d593aecf5d78aebbf45fc110
https://github.com/tribe29/checkmk/commit/5eeb04142bb69426d593aecf5d78aebbf…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2019-07-24 (Wed, 24 Jul 2019)
Changed paths:
M tests/static/Pipfile.lock
M virtual-envs/2.7/Pipfile.lock
M virtual-envs/3.7/Pipfile.lock
Log Message:
-----------
Regenerated Pipfile.lock files because of PyPI breakage.
PyParsing 2.4.1 has been REMOVED(!) from PyPI, causing our builds to fail.
While it is totally OK that a release has a few bugs, even horrible ones,
removing a release from a public package repository is an idiotic move,
causing breakage in the ecosystem which can easily be avoided: The right way
would have been quickly uploading the contents of PyParsing 2.4.0 with the
version number 2.4.2, effectively retracting 2.4.1 without any widespread
breakage. PyPI should really, really disallow package removal... >:-/
Change-Id: Ida8dce96ad53d809d32b24ce062002d181e7eeb8