Debian 6.0.6 Updates Choke on *unoconv*

CRhode's picture
AttachmentSize
Plain text icon *apt* log1.07 KB

Forums: 

I gather that accommodating all possible *python* versions is a developmental headache. The security update to *soffice*, which includes *unoconv* and *python-uno*, runs into an error with my python version. See the attached, redacted *apt* log.

First, let me say I *always* apply Debian updates as soon as they are available, and I *never* have a problem with them ... up to now. Second, I aver that I use the vanilla *python* and don't fool around with version levels. On my system:

/usr/bin/python --> /etc/alternatives/python --> /usr/bin/python2.6

... so I don't see how the update installation could have screwed up, and I doubt I am the first or only one to experience this error. I have production requirements for both *unoconv* and *python*.

QUESTION: How can I escalate this problem with *soffice* and Debian development?

> How can I escalate this

IntnsRed's picture

> How can I escalate this problem with *soffice* and Debian development?

Have you filed a bug on the relevant package? The bug system has an option to denote the priority of a bug.

How to File Bug

CRhode's picture

I'm not sure what the relevant package is. *python*, *unoconv*, *soffice*, and *apt* all work fine. I just can't apply the latest Linux update from Debian. -ccr-

Re: How to File Bug

IntnsRed's picture

Yes, I know what you mean about the "software package" that is in reality a sea of dependencies of other packages.

Typically, the programmers and Debian maintainers know the intricacies of the various packages and dependencies, but normal humans certainly do not. In these cases, just look for an error message or take a shot and guess at one of the packages. If you add in a disclaimer in the bug report text that you're not sure exactly what package this pertains to, the Debian maintainers are usually very good about reassigning the bug to the proper package.

In your specific case, the log is whining about python-uno. I'd file the bug on the python-uno package.

FWIW, one strategy to deal with this -- you shouldn't have to do this, but it will usually work -- is to "purge" (completely remove the package) the python-uno package and then to reinstall it. This almost always works since it was just some bizarre glitch in the upgrade and the "new install" works fine and was tested better. This can often cause a dependency "cascade" and prompt you to uninstall/purge other packages too, but if you haven't customized them they're pretty trivial to reinstall.

Like I said, you shouldn't have to do this, but it's one way of dealing with it. Filing the bug report is the foolproof method of dealing with this and it'll solve the problem at the source.