Hi,
due to a wrong version string in 3.6.4.2, Fridrich just created the
libreoffice-3.6.4.3 tag (aka rc3). The corresponding official builds
will be available within next few days.
Now, you might switch your current 3-6 source tree to it using:
./g fetch --tags
./g checkout -b
On 11/27/2012 11:31 PM, Cor Nouws wrote:
Petr Mladek wrote (27-11-12 17:54)
We listen :-) Well, the testing can be done even with Dev builds. I
installed the daily build from
http://dev-builds.libreoffice.org/daily/Linux-x86_64_11-Release-Configuration/master/current/
and did the following
Hi Norbert
Norbert Thiebaud wrote
I count 3 out of 13 that seems to have their '@' sign gobbled up that
a far cry from 'most'...
that being said it would be best indeed to ping the owner of these box
to get them to fix that...
And another 2 (named W2008R2) refer to the host OS not the
Stephan Bergmann-2 wrote
If LOdev versions indeed store their user profiles centrally (at
~/.config/lodev/{3,4} ? correct me if I'm wrong), then the scenario of
reusing an existing user profile from a previous LOdev version N1 in a
new LOdev version N2, where N2 = N1 and N1 and N2 are
Pedro píše v Út 27. 11. 2012 v 09:10 -0800:
Another solution would be to build 4.0-betas with release
configuration. I guess that it can be installed in parallel with LO-3
even on Windows because it uses another prefix, ... How does that
sound?
What do you mean release configuration?
Hi Petr
Petr Mladek wrote
I mean to do the official beta builds with --enable-release-build
configure option. It will produce LibreOffice product instead of LODev
= it will act as an official release = you will be able to test
configuration migration exactly the same as for final build.
Open invite to anyone wanting to join QA call. Approximately 1 hour long.
All information including call in #'s and prototype agenda can be found
here, additional items welcome, either email me or edit the wiki directly.
http://wiki.documentfoundation.org/QA_Call_Current_Agenda
Regards,
Joel
Stephan Bergmann wrote (28-11-12 11:23)
On 11/28/2012 10:40 AM, Cor Nouws wrote:
Stephan Bergmann wrote (24-11-12 11:40)
Given that testing migration from existing user profiles generally
requires manual activity anyway (to remove potentially existing MIGRATED
flag files from existing user
