Bug#944227: transition: prompt-toolkit

2020-02-12 Thread Gordon Ball
On Tue, Feb 11, 2020 at 08:56:43PM -0500, John Scott wrote:
> It appears that bugs haven't been filed to get reverse dependencies depending 
> on version 1 out of testing.
> 
> Britney [1] says
> > trying: prompt-toolkit
> > skipped: prompt-toolkit (39, 2, 91)
> > 
> > got: 26+0: a-1:a-0:a-0:a-0:i-17:m-0:m-7:p-0:s-1
> > * mipsel: caffe-cpu, python3-caffe-cpu, python3-guiqwt,
> > python3-line-profiler, python3-pyraf, python3-sfepy, python3-yt
> and so since these binaries are still in Bullseye, prompt-toolkit isn't going 
> to be migrating until they're removed.

I think this is the wrong line to look at.

Just above is

trying: python-softlayer prompt-toolkit jupyter-console ipython
skipped: python-softlayer prompt-toolkit jupyter-console ipython (39, 0,
90)
got: 20+0: a-1:a-0:a-0:a-0:i-18:m-0:m-0:p-0:s-1
* i386: mycli
- splitting the component into single items and retrying
  them

Which is the set of packages which _should_ migrate together. They're
currently blocked because while a compatible version of mycli has been
uploaded to unstable, it was uploaded prebuilt, which is no longer
allowed to migrate to testing. I've communicated with the maintainer
about this (getting a new upload should be quicker than getting the old
version autoremoved).

The block you picked above shows what happens if, having failed to
migrate those four packages together, it tries instead to migrate
prompt-toolkit only - which results in ipython being removed from
testing, and most of the listed packages are rdepends of ipython.
> 
> I'm only an interested user and may be misunderstanding. Could you file these 
> bugs or help me understand what I'm overlooking?
> [1] https://release.debian.org/britney/update_output.txt



Bug#944227: transition: prompt-toolkit

2020-02-11 Thread John Scott
It appears that bugs haven't been filed to get reverse dependencies depending 
on version 1 out of testing.

Britney [1] says
> trying: prompt-toolkit
> skipped: prompt-toolkit (39, 2, 91)
> 
> got: 26+0: a-1:a-0:a-0:a-0:i-17:m-0:m-7:p-0:s-1
> * mipsel: caffe-cpu, python3-caffe-cpu, python3-guiqwt,
> python3-line-profiler, python3-pyraf, python3-sfepy, python3-yt
and so since these binaries are still in Bullseye, prompt-toolkit isn't going 
to be migrating until they're removed.

I'm only an interested user and may be misunderstanding. Could you file these 
bugs or help me understand what I'm overlooking?
[1] https://release.debian.org/britney/update_output.txt

signature.asc
Description: This is a digitally signed message part.


Bug#944227: transition: prompt-toolkit

2019-11-14 Thread Graham Inggs

Control: tags -1 moreinfo

Hi Gordon

Please file bugs for the affected packages that do not currently support 
ptk 2, and mark those bugs as blocking this one.


Do the affected packages have versioned Depends, or did you add Breaks 
against those packages in your package?  In either case, you can go 
ahead and file those bugs with severity Serious.


Regards
Graham



Bug#944227: transition: prompt-toolkit

2019-11-06 Thread Gordon Ball
Package: release.debian.org
Severity: normal
User: release.debian@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