Control: reopen -1 Control: reassign -1 libboost-python1.67.0 1.67.0-14 Control: retitle -1 libboost-python1.67.0 must not drop the Python 2.7 library
When a library package renames or drops a library it has to be removed. In practice this will happen in the boost case with the transition to 1.71. One real-world problem is that right now upgrading in a stable installation to the libboost-python1.67.0 package in unstable would cause runtime breakage in stable, and it would be even worse if the broken boost would enter testing. Dimitri already agreed in a private discussion that this change was bogus. Are there any objections against an NMU reverting the bogus Python 2 removal in boost1.67? cu Adrian
