mhenriday wrote
2014-12-11 20:34 GMT+01:00 edo1 <
edagro12@
>:
On a Win_x86 machine on my LAN I'm asked to update LO ver 4.3.1, which I
did
to 4.3.4.1. But on a Win_x64 machine running ver 4.2.6-secfix, LO says
it's
up to date.
So I'm confused. Which is the latest version? Should I update the secfix
version even though LO isn't asking for one?
If I understand matters aright, edo1 - and someone is sure to correct me
otherwise -
LibreOffice updates *within*
each series. Thus 4.3.1 will update to 4.3.4.1, but r.2.6 will not jump
to
the 4.3 series....
As to whether you should update the latter to the former, after comparing
the two on your two respective machines, which do you prefer working with
?...
Thanks for your reply, I believe you're correct. As it turns out, just
*asking* the secfix version to update renders it unopenable. I just deleted
it and installed a fresh ver. 4.3.4.1. Hope I'm now back on the main fork.
--
View this message in context:
http://nabble.documentfoundation.org/LO-vers-4-2-6-3-vs-4-3-4-1-tp4132307p4132327.html
Sent from the Users mailing list archive at Nabble.com.
--
To unsubscribe e-mail to: users+unsubscribe@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
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.