Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #12206 > unrolled thread

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

Started bypeter green <plugwash@p10link.net>
First post2020-01-18 03:50 +0100
Last post2020-01-18 10:20 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition peter green <plugwash@p10link.net> - 2020-01-18 03:50 +0100
    Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition Julien Puydt <julien.puydt@laposte.net> - 2020-01-18 10:20 +0100

#12206 — Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

Frompeter green <plugwash@p10link.net>
Date2020-01-18 03:50 +0100
SubjectBug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition
Message-ID<zpMlr-3ek-1@gated-at.bofh.it>
I just took a look at the "add python3.8 transition tracker", and split the remaining "bad" packages into categories.

Key package, rc bug with patch.
* gpgme1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944774

Not key package, but not marked for autoremoval from testing
* macs version in unstable FTBFS on most architectures, version in testing seems to build fine
   with 3.8 according to reproducible builds, but afaict binnmus are not currently possible in testing

Builds only against default python3 version
* libcap-ng https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943627
* fontforge https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948016
* pcp can't find a bug report for this one.
* getfem++ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948016
* uhd https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943636
* stimfit https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020

Marked for autoremoval from testing
* subvertpy https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942678
* beancount https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943608
* python-thinc https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947111

Not in testing (and not mentioned already)
* libyang build timesouts on mipsel/mips64el , probablly heavy swap use
* python-tesserocr https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943501
* pyfai https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945411
* veusz https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945467

[toc] | [next] | [standalone]


#12207

FromJulien Puydt <julien.puydt@laposte.net>
Date2020-01-18 10:20 +0100
Message-ID<zpSqR-73a-1@gated-at.bofh.it>
In reply to#12206
Le samedi 18 janvier 2020 à 02:38 +0000, peter green a écrit :
> I just took a look at the "add python3.8 transition tracker", and
> split the remaining "bad" packages into categories.

There's another kind of issue ; here is an example :

- sagemath builds only for Python 3.7, so some of this subpackages
don't load under Python 3.8 : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949023

- which means that for brial, autopkgtest fails : 
https://ci.debian.net/data/autopkgtest/testing/amd64/b/brial/3988637/log.gz

I haven't found the time to investigate things further in sagemath ; I
was wondering if I wouldn't disable the Python 3.8 test in brial... not
ideal...



Cheers,

JP

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web