Hi Andreas, On 08-01-2020 00:03, Andreas Beckmann wrote: [...] > So let's rebuild all rdepends of libboost-python1.67.0 and friends to > tighten the dependencies and properly document which python support is > being used. That should help with the python2 removal (and a future > removal of python3.7 as a supported version). > > I don't know how to express something like > "depends on libboost-python1.67.0 > AND NOT depends on libboost-python1.67.0-py.*" I used this: .depends ~ /\blibboost-(mpi-python|python|numpy)[0-9.]*\b/ & !.depends ~ /\blibboost-(mpi-python|python|numpy)[0-9.]*-py[0-9]*\b/ > in ben, so the below ben file will only generate "unknown" and "good" > states. (Is ".false" the correct syntax for that?) > You can exclude src:boost1.67 and src:boost1.71 if you want. > Please binNMU the remaining "unknown" packages once, hopefully they > should all turn green. Since this is not a real transition, all could be > scheduled at the same time. [...] All rebuilds have been scheduled. There are 2 packages (python-escript (sid only) and pythonmagick) that FTBFS now, but didn't before. Can you please check? Especially pythonmagick looks suspicious to my untrained eyes. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature