[Debian-med-packaging] Bug#936630: Aw: Bug#936630: gnumed-client: upstream has (unreleased) py3 support
Karsten Hilbert
Karsten.Hilbert at gmx.net
Thu Jan 30 20:14:35 GMT 2020
It's done, there's even a release 1.8.rc3.
I need to convince myself to release 1.8.0 proper :-)
Karsten
> Gesendet: Donnerstag, 30. Januar 2020 um 17:25 Uhr
> Von: "Scott Talbert" <talbert at techie.net>
> An: "Moritz Mühlenhoff" <jmm at inutil.org>
> Cc: "Karsten Hilbert" <karsten.hilbert at gmx.net>, "Debian Bug Tracking System" <936630 at bugs.debian.org>
> Betreff: Bug#936630: gnumed-client: upstream has (unreleased) py3 support
>
> On Tue, 17 Dec 2019, Moritz Mühlenhoff wrote:
>
> >> Package: gnumed-client
> >> Version: 1.7.6+dfsg-1
> >> Followup-For: Bug #936630
> >>
> >> Has been ported to py3 upstream but not released yet because:
> >>
> >> Would like to be able to get bugfix-only 1.7.x py2 packages
> >> into the deb package pool until very late before bullseye
> >> so people running 1.7/py2/stable/testing can get bug fixes
> >> from the pool.
> >
> > That's unfortunately not possible:
> > The Python 2 removal operates a very complex of packages which
> > many inter dependencies, so it's not possible to keep some
> > packages around until late in the freeze cycle.
> >
> > In fact, the bug for gnumed-client got already bumped to release-critical
> > state because of reverse depencies (which triggered it's removal
> > from testing), so that's not possible.
>
> Hi Karsten,
>
> How is the Python 3 port of gnumed-client coming?
>
> Scott
More information about the Debian-med-packaging
mailing list