Bug#954804: release.debian.org: Need release team intervention to disentagle python-pip from python3.8 as default

[Scott Kitterman <debian@kitterman.com>]

Package: release.debian.org
Severity: normal

Python-pip is actually ready to migrate, but there are problems that
will take manual intervention to address:

1.  Autopkgtest regressions marked against doit and logbook:

Both tests are RC buggy (and bugs filed).  It's true that updating pip
unmasked the bugs, but they were RC buggy before due to using packages
downloaded from the internet to run tests.  Also, logbook can't be fixed
in Testing until after the python3.8 as default (python3-defaults)
transition is complete.

2.  Python-pip needs python-msgpack to migrate:

Python-msgpack is trapped behind waiting for borgbackup to migrate and
it's stuck behind python3.8 as default.  The Unstable python-msgpack
will break the borgbackup in Testing, so merely force updating
python-msgpack may not be a great idea.  This could be unblocked either
by forcing python-msgpack or a temporary removal of borgbackup from
Testing.

This will also enable python-virtualenv to migrate in a few days after
the updated Tox is in testing.  

Thanks,

Scott K