[Debian-med-packaging] Bug#707341: upgrade to important, python-uno should go away

[Rene Engelhard]

severity 707338 important
severity 707339 important
severity 707340 important
severity 707341 important
severity 707342 important
retitle 707338 recommends obsolete python-uno (for python2) which should go away
retitle 707339 recommends obsolete python-uno (for python2) which should go away
retitle 707340 depends on obsolete python-uno (for python2) which should go away
retitle 707341 recommends obsolete python-uno (for python2) which should go away
retitle 707342 suggests obsolete python-uno (for python2) which should go away
thanks

Hi,

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...)

docvert is fixed upstream, but I see no sign for the rest (but I didn't
actively check them, maybe they are as unmaintained upstream or in Debian
as docvert and there actually are new releases...)

Anyway: I'll try to fix python-uno for LO 4.2.x but I have just decided to
disable building it with LO 4.3 (which IS still planned for jessie).

Thus I am upgrading those bugs to important.

I asked the release team and they are OK with dropping python-uno, too:

15:33 < _rene_> is Recommends: a Depends: for britney?
15:34 < _rene_> aka if I remove a package from LO which is "just" recommended, 
                will it block migration because the stuff is considered 
                uninstallable?
15:36 < KiBi> those are different things
15:39 < _rene_> ok
15:40 < _rene_> would the RT scream if I did a QA upload for docvert with a new 
                upstream release supporing python3-uno and removed python-uno 
                in LO 4.3? (divert Depends: on it, the others just 
                recommend/suggest it)
15:41 < _rene_> it's broken right now inside LO even though it Depends: 
                python3-uno | python-uno. tring to fix it but supporting it is 
                a hack and python-uno is obsolete (anything supporting LO must 
                support python3 anyway as that's the only one supported by LOs 
                "packages")
15:47 < pochu> _rene_: as long as LO still migrates, I think it's fine
[...]
15:51 < _rene_> pochu: yeah, but it will break the functionality of what those 
                stuff (thankfully one isn't in testing) uses python-uno for
15:51 < KiBi> that was my first impression, but then mischecked the ood binaries
15:51 < pochu> but mod-gnutls would potentially break if its decrufted, I 
               guess...
15:51 < _rene_> pochu: I am just seding a ping to those bugs, with making 
                whishlist -> important and retitling
15:51 < pochu> _rene_: sounds good
15:51 < _rene_> let's see
15:52 < _rene_> now someone needs to fix dovert (orphaned, "maintained" by QA) 
                or it should be removed
15:52 < _rene_> dovert
15:52 < _rene_> argh
15:52 < _rene_> docvert
15:52 < pochu> _rene_: and if you want to remove it, you can do it, if those 
               packages only have python-uno in recommends or suggests... and 
               then bump the severity as you're saying, telling them to switch 
               to py3uno if they want it back

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-uno.

As said in my initial bug filing - ANYTHING which expects to work with
stock LO as provided on www.libreoffice.org MUST support python3 anyway
as that one's the _only_ potion available there, python-uno was just
a Debian-hack for its reverse-dependencies...

Regards,

Rene