[Pkg-electronics-devel] Bug#936792: kicad: Python2 removal in sid/bullseye

Carsten Schoenert c.schoenert at t-online.de
Mon Oct 28 18:50:52 GMT 2019


Hello Andreas,

Am 28.10.19 um 15:31 schrieb Andreas Henriksson:
> It seems the kicad package has already (mostly) been switched over
> to python3. The only python2 related things I could spot is the
> libpython-stdlib build-dependency. This seems to be something lingering
> from a long time ago which maybe just isn't relevant anymore.
> 
> I tried to find the original reason it was introduced and in
> debian/changelog entry for 4.0.2+dfsg1-3 I found the following
> pretty cryptic message:
> 
>    * added a build-dependency on libpython-stdlib, which should not harm
>      for most architectures, and might be necessary on a few ones.
> 
> Maybe this should be switched over to libpython3-stdlib now that
> everything else uses python3, but I also wouldn't be surprised if
> it should just be dropped because the cryptic description kind of
> smells like a bogus excuse to me.
> 
> Could kicad maintainers please comment on what you think?

I'm back from the miniDebConf Vaumarcus just right now. :)

For a long time I was now able to work also on various other parts of 
the packaging of KiCad while the mDC. So I can answer your question 
hopefully.

I also don't now why George has added this dependency and it was 
probably really not needed and I will simply just remove it.

The src:kicad package has a dependency on python3-all since January 2019 
which is pulling in python3.7 (currently). This then is depending on 
libpython3.7-dev so this library is installed and pulled anyway.

Removing libpython-dev will as far I see remove the only direct 
dependency on Python2. But there are more indirect dependencies on 
Python2 e.g by dblatex and asciidoc.

-- 
Regards
Carsten Schoenert



More information about the Pkg-electronics-devel mailing list