[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#944227: marked as done (transition: prompt-toolkit)

Your message dated Wed, 19 Feb 2020 21:14:05 +0100
with message-id <00d9501b-7bef-d78c-9ce4-dfd960fbe8a0@debian.org>
and subject line Re: Bug#944227: marked as done (transition: prompt-toolkit)
has caused the Debian Bug report #944227,
regarding transition: prompt-toolkit
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.)


-- 
944227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944227
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

(please explain about the transition: impacted packages, reason, ...
 for more info see: https://wiki.debian.org/Teams/ReleaseTeam/Transitions)

We would like to update prompt_toolkit from major version 1 to 2.

This was originally requested in #914698 (blocker for upgrading
pymodbus), but is also now a blocker for a number of other python
package updates (eg, ipython).

Prompt-toolkit 2.x was released in mid-2018 (the 1.x branch is
considered deprecated by upstream, but some fixes are still made to it).

Without patching the library name and the import path of all
dependencies, co-installation of both branches would not be possible.

I have upload 2.0.10 to experimental (concurrently dropping python 2
support, #937326, but this does not appear to affect many packages).

Upstream documentation on upgrading:
https://python-prompt-toolkit.readthedocs.io/en/master/pages/upgrading/2.0.html


Affected packages:

aws-shell: does not appear to support ptk 2; issue
           https://github.com/awslabs/aws-shell/issues/209
gitsome: unversioned d/control dependency, setup.py for 0.8 (unstable)
         already requires ptk 2
ipython: 5.8 (unstable) requires ptk 1, upgrade to 6 or later blocked on
         ptk 2
jupyter-console: 5.2 (unstable) requires ptk 1, upgrade to 6 or later
                 blocked on ptk 2
mlbstreamer: unversioned dependency in both d/control, setup.py
mycli: 1.16 (unstable) requires ptk 1, 1.19 or later supports ptk 2
pgcli: 1.9.1 (unstable) requires ptk 1, 2.0 or later supports ptk 2
python-softlayer: 5.7.2 (unstable) requires ptk 1, 5.8 or later supports
                  ptk 2
sagemath: unversioned d/control dependency,
          https://git.sagemath.org/sage.git/tree/build/pkgs/prompt_toolkit/package-version.txt
          suggests ptk 1 required
xonsh: current version supports both ptk 1, 2

Ben file:

title = "prompt-toolkit";
is_affected = .build-depends /python3?-prompt-toolkit/ | .depends ~ /python3?-prompt-toolkit/;
is_good = true;
is_bad = .build-depends ~ "python-prompt-toolkit" | .depends ~ "python-prompt-toolkit";


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-1-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Gordon,

On 07-01-2020 21:16, Paul Gevers wrote:
> Hence, I reopen the bug.
> 
> I notice that python-softlayer needs to be updated for your package to
> migrate, but I am not aware that the maintainer has been warned about
> it. ginggs asked you to file the bug, but I didn't spot it. Please do so
> ASAP and mark it blocking this bug.

prompt-toolkit migrated and the rest went together with it. Hence,
closing this bug.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: