Bug#954804: marked as done (release.debian.org: Need release team intervention to disentagle python-pip from python3.8 as default)
Your message dated Fri, 27 Mar 2020 13:18:37 +0100
with message-id <f3b0cd52-fc95-4852-543e-47de7a731a52@debian.org>
and subject line Re: Bug#954804: release.debian.org: Need release team intervention to disentagle python-pip from python3.8 as default
has caused the Debian Bug report #954804,
regarding release.debian.org: Need release team intervention to disentagle python-pip from python3.8 as default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
954804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954804
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On 23/03/2020 19:08, Scott Kitterman wrote:
> 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.
python3-defaults has now migrated, and python-pip with it. So I think we can
close this.
Cheers,
Emilio
--- End Message ---
Reply to: