Bug#929954: [Python-apps-team] Bug#929954: what about just uploading relevant patch for now?

2019-12-29 Thread Yaroslav Halchenko


On Fri, 09 Aug 2019, Elena ``of Valhalla'' wrote:

> Yaroslav Halchenko  wrote:
> > If new version building is problematic, why not to upload just a patched
> > version?

> That would only delay the removal a bit: I'm sure that the current
> version doesn't work with python3, so it's going to be removed sooner or
> later from the archive.

> Uploading the new upstream would also be python2 only, at least at the
> beginning, but at least there is hope that it can be made to work also
> with python3.

> I don't expect the new version to be problematic, but it will involve a
> bit of yak shaving, and and see #876681 (RFH: rst2pdf) on how this
> package is pretty low on my priorities.

Hi Elena et al

I wonder if anything could be done to have this package fixed, so
dependent packages (e.g. nuitka) aren't blocked awaiting for the
resolution.

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



Bug#929954: what about just uploading relevant patch for now?

2019-08-09 Thread Elena ``of Valhalla''
Yaroslav Halchenko  wrote:
> If new version building is problematic, why not to upload just a patched
> version?

That would only delay the removal a bit: I'm sure that the current
version doesn't work with python3, so it's going to be removed sooner or
later from the archive.

Uploading the new upstream would also be python2 only, at least at the
beginning, but at least there is hope that it can be made to work also
with python3.

I don't expect the new version to be problematic, but it will involve a
bit of yak shaving, and and see #876681 (RFH: rst2pdf) on how this
package is pretty low on my priorities.

-- 
Elena ``of Valhalla''



Bug#929954: what about just uploading relevant patch for now?

2019-07-29 Thread Yaroslav Halchenko
Package: rst2pdf
Version: 0.93-7
Followup-For: Bug #929954

If new version building is problematic, why not to upload just a patched
version?  I have verified that adding import reportlab to
/usr/lib/python2.7/dist-packages/rst2pdf/flowables.py addresses the issue

I ran into this one while building new version of nuitka, so its new version
upload blocked by this one.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rst2pdf depends on:
ii  python2.7.16-1
ii  python-docutils   0.14+dfsg-4
ii  python-pdfrw  0.4-2
ii  python-pkg-resources  40.8.0-1
ii  python-pygments   2.3.1+dfsg-1
ii  python-reportlab  3.5.13-1
ii  python-setuptools 40.8.0-1
ii  python-simplejson 3.16.0-1
ii  python3-pygments  2.3.1+dfsg-1

rst2pdf recommends no packages.

Versions of packages rst2pdf suggests:
pn  python-aafigure  
ii  python-matplotlib2.2.3-6
ii  python-pil   5.4.1-2
ii  python-sphinx1.8.4-1
ii  python-uniconvertor  1.1.5-4

-- debconf-show failed