, On 07/28/2011 12:53 AM, Tom Cloyd wrote:
On 07/28/2011 12:44 AM, Alexander Thurgood wrote:
Le 27/07/11 18:14, Tom Cloyd a écrit :
That command appears to have cut 5 seconds off the record pointer move
test, and also off the full db search test I ran previously.
Well better than nothing I suppose, but I do sympathise. Did the JDK/JRE
change suggested by someone else help any further ?
Alex
Am just about to make the switch - will let you know asap! I'm very
hopeful. And I've decided to switch to sqlite when I'm not so rushed.
Have heard that that's where LO's going anyway.
Tom
Ug. This is getting ugly really fast. I'm really not on home ground
here at all.
After 15 minutes of trying to make sense of what I found at
http://archive.canonical.com/ubuntu/pool/partner/s/sun-java6/, I downloaded
sun-java6-bin_6.22-0ubuntu1~10.04_i386.deb and
sun-java6-jre_6.22-0ubuntu1~10.04_all.deb, following the thread at
http://www.oooforum.org/forum/viewtopic.phtml?t=125253&postdays=0&postorder=asc&start=0
<http://www.oooforum.org/forum/viewtopic.phtml?t=125253&postdays=0&postorder=asc&start=0>.
Then I did this at a console, with the following result:
tomc@LDT:~/software_archive$ sudo dpkg --unpack
sun-java6-bin_6.22-0ubuntu1~10.04_i386.deb
[sudo] password for tomc:
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 38010
package 'amaya':
error in Version string 'wx-11.3.1-1': version number does not start
with digit
dpkg: warning: parsing file '/var/lib/dpkg/available' near line 40706
package 'amaya':
error in Version string 'wx-11.3.1-1': version number does not start
with digit
dpkg: warning: downgrading sun-java6-bin from 6.26-1natty1 to
6.22-0ubuntu1~10.04.
(Reading database ... 190655 files and directories currently installed.)
Preparing to replace sun-java6-bin 6.26-1natty1 (using
sun-java6-bin_6.22-0ubuntu1~10.04_i386.deb) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend requires a screen at least 13 lines tall and
31 columns wide.)
debconf: falling back to frontend: Readline
sun-dlj-v1-1 license has already been accepted
Unpacking replacement sun-java6-bin ...
Processing triggers for desktop-file-utils ...
Processing triggers for menu ...
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 38010
package 'amaya':
error in Version string 'wx-11.3.1-1': version number does not start
with digit
Most of this is just garble to me,
THIS is scary: "dpkg: warning: downgrading sun-java6-bin from
6.26-1natty1 to 6.22-0ubuntu1~10.04."
I said UNPACK, not INSTALL. What's this "downgrading" nonsense? Then
this: "Preparing to replace sun-java6-bin 6.26-1natty1" Huh? All this on
an "unpack". This is beyond scary. This is nuts. What's up with this???
Then, and this is the main problem - where's the result of the command?
I expected the unpack to put files in a dir, in the same dir as the DEB
file. Isn't this usually what happens when one unpacks a file? But
there's nothing there.
I'm in freefall right now. Don't know what just happened, don't know
what to do next. Can anyone help?
Guess I'm not going to get any db work done tonight, after all. Not a
good day.
Tom
--
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Re: Base record access unacceptably slow (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.