[Debian-med-packaging] Bug#707341: upgrade to important, python-uno should go away
Karsten Hilbert
Karsten.Hilbert at gmx.net
Mon Jun 30 19:18:26 UTC 2014
On Sat, Jun 14, 2014 at 10:07:24PM +0200, Rene Engelhard wrote:
> On Sat, Jun 14, 2014 at 04:23:20PM +0200, Rene Engelhard wrote:
> > still supporting python-uno gives much headache (for example it's build is
> > a big hack and right now it's broken for wizard/lightproof usage inside LO.
> > I am trying to fix it but if I don't succeed we should make -common force
> > python3-uno. Which would mean it conflicted against python-uno...)
> [...]
> > Anyway: I'll try to fix python-uno for LO 4.2.x but I have just decided to
>
> It was easier than it looked after some tries with the build - a simple
> missing file :) [1]
>
> > disable building it with LO 4.3 (which IS still planned for jessie).
> [...]
> > So expect python-uno going away without further notice once dovert is fixed,
> > or removed - breaking whatever functionality you need it for. As said,
> > you can make it work again by switching to python3-un
>
> Now that it's fixed: Maybe also only after jessie release because I do
> acknowledge that it's not much time until the freeze.
>
> Which would means 4.4 or newer, which I already have changed
> to remove the option alltogether [2]
>
> Still your package must be changed to support python3. ASAP.
Well, since ATM there is neither any python-wxgtk3 (which
would also mean having to port from wxp2 to wxp3)
nor any python-wxgtk2.8-for-python3 this assertion
seems of little use ?
Or am I missing something ?
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
More information about the Debian-med-packaging
mailing list