Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-17 Thread Thomas Goirand
On 10/17/19 1:26 AM, Norbert Preining wrote: > Hi Thomas, > >> Closer to the release means that all the reverse dependencies of your >> package will have to get somehow fixed. If everyone does like this, then >> that's too much work. If possible, it'd be best if that could happen > > I agree,

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Norbert Preining
Hi Thomas, > Closer to the release means that all the reverse dependencies of your > package will have to get somehow fixed. If everyone does like this, then > that's too much work. If possible, it'd be best if that could happen I agree, but let us look at reality: - bullseye will be released

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Thomas Goirand
On 10/16/19 3:45 PM, Norbert Preining wrote: > Hi Thomas, > > The switch to Py3 is ready and can be done any time, any second. The > experimental branch of my repo contains the code, and I have ready built > packages here. > > That said, I don't see any urgency to switch as long upstream does

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Norbert Preining
Hi Thomas, The switch to Py3 is ready and can be done any time, any second. The experimental branch of my repo contains the code, and I have ready built packages here. That said, I don't see any urgency to switch as long upstream does not switch, and we are still in bulleyes preparation. I

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Thomas Goirand
On 10/16/19 3:41 PM, Thomas Goirand wrote: > Norbert, > > No worries for cherrypy3 py2 revival. > > Though I still have a concern that you wrote your plan is to get Calibre > to use Py2 for how long as possible. IMO that shouldn't be the plan. > Your plan should be to try to fix the situation as

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Thomas Goirand
Norbert, No worries for cherrypy3 py2 revival. Though I still have a concern that you wrote your plan is to get Calibre to use Py2 for how long as possible. IMO that shouldn't be the plan. Your plan should be to try to fix the situation as early as possible, rather than as late as possible. I

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-16 Thread Norbert Preining
severity 936270 important thanks Hi Stuart, hi Thomas, @Thomas, thanks for reintroducing python-cherrypy3! On Mon, 14 Oct 2019, Stuart Prescott wrote: > bullseye would currently fail because there would be no Python 2 module for > cherrypy3 available. > > While python-cherrypy3 should not yet

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-10-14 Thread Stuart Prescott
Control: severity -1 serious On Wednesday, 25 September 2019 22:44:11 AEDT Norbert Preining wrote: > As long as the rdepends is in place the p2 version will not be removed from > unstable nor testing, and thus the package still builds and works, nothing > serious here but the fact that cherrypi

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-09-25 Thread Norbert Preining
severity 936270 normal thanks As long as the rdepends is in place the p2 version will not be removed from unstable nor testing, and thus the package still builds and works, nothing serious here but the fact that cherrypi maintainers didn't consider rdepends. Adjusting severity. Thanks On

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-09-25 Thread Norbert Preining
clone 936270 -1 reassign -1 src:python-cherrypy3 retitle -1 removal of p2 version breaks rdepends thanks Dear cherrypi maintainers, I strongly recommend checking on rdepends before dropping packages, thanks. Norbert On September 25, 2019 8:31:25 PM GMT+09:00, peter green wrote: >severity

Bug#936270: calibre: Python2 removal in sid/bullseye

2019-09-25 Thread peter green
severity 936270 serious thanks calibre depends on python-cherrypy3 which has already been dropped by the cherrypy3 source package.