Thursday, May 2, 2024
 Popular · Latest · Hot · Upcoming
10
rated 0 times [  10] [ 0]  / answers: 1 / hits: 17975  / 2 Years ago, sun, october 16, 2022, 2:29:30

I had a script, it is working with the package python-uno on Ubuntu 12.04 lts. The script is in python language and work with OOo to edit XLS files.



Now I upgraded to 13.10 and it seems the uno not working on this release.



Is there any other solution that work like python-uno? Or how can I know when the uno will be available for 13.10 ?!



UPDATE:
i upgraded this ubuntu server with 'do-release-upgrade' and after update i got 'cant import uno package' in logs
so tried to install python-uno from command line and i show this message :



peiman@digidoc:~$ sudo apt-get install python-uno
[sudo] password for peiman:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package python-uno is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libreoffice-script-provider-python

E: Package 'python-uno' has no installation candidate

More From » apt

 Answers
2

If you read the message it says:




Package python-uno is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libreoffice-script-provider-python



Hence, what to do, instead of python-uno install libreoffice-script-provider-python instead:



sudo apt-get install libreoffice-script-provider-python


This will install python3-uno package, and the interface for LO to use UNO.



python-uno package was removed:



libreoffice (1:4.1.0-2ubuntu1) saucy; urgency=low

* unfuzz Ubuntu palette patch
* remove sessioninstaller for wizards patch -- they are all python now
* remove python-uno (Python 2 bridge)
* trying to remove the workdir before installing on ppa builds to squeeze in
size requirements
* smaller src-tarballs
* do not run subsequentchecks in build anymore, as we can run them as an
autopkgtest, which is better, and eases distress caused by PPA buildds
being storage contrained
* use system orcus for real
* remove double echo
* merge with upstream
* use system lpsolve and graphite
* kill of csh stuff for good
* clean up dupes in -core breaks against -evolution
* remove dbghelp.dll binary from tarball creation
* silence lintian on the copyright file
* make -dbg use python3-uno proper
* fix build against poppler 0.23/0.24

-- Bjoern Michaelsen Thu, 01 Aug 2013 20:17:26 +0200

[#27087] Monday, October 17, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
oleard

Total Points: 344
Total Questions: 105
Total Answers: 113

Location: Bonaire
Member since Tue, Sep 20, 2022
2 Years ago
;