Hello all,
I committed a change to ooo_sites and after 6h the changes are still not
visible.
Are there additional steps needed?
Thanks
Peter
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional
Maybe it is a good point to ask infra to switch to git?
On 15.01.19 08:13, Mechtilde wrote:
> the same revision buids under Debian 8 with epm version 3.7 which is
> shipped in the source code.
>
> but this doesn't work with Debian 9 and CentOS 7.
>
> Now I run it with system epm 4.2 on Debian 9.
the same revision buids under Debian 8 with epm version 3.7 which is
shipped in the source code.
but this doesn't work with Debian 9 and CentOS 7.
Now I run it with system epm 4.2 on Debian 9. In some hours I will send
the result.
Mechtilde
Am 15.01.19 um 02:12 schrieb Damjan Jovanovic:
> I
I can't see much in that output, and you're not going to like my suggestion.
Clone AOO from a Git repository, find an old version that could build debs,
and then do a regression test with "git bisect" to find the first commit
that broke building debs, so we can see where and how it went wrong and
Yeah... getting this on my CentOS7 builds as well...
Just on debs... rpms are fine.
> On Jan 14, 2019, at 4:37 PM, Mechtilde wrote:
>
> Hello,
>
> Am 10.01.19 um 07:01 schrieb Mechtilde:
>>
>>
>> Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
>>> Hi
>>>
>>> I am glad it worked.
>>>
>>>
> On Jan 14, 2019, at 12:24 PM, Damjan Jovanovic wrote:
>
> That loop happens when one or more files can't be found.
>
Ahh... that makes perfect sense. #sarcasm
-
To unsubscribe, e-mail:
Hello,
Am 10.01.19 um 07:01 schrieb Mechtilde:
>
>
> Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
>> Hi
>>
>> I am glad it worked.
>>
>> Sure, patch the whole 42x branch.
>
> As I described in the other thread it breaks at building with epm.
>
> It says I had to rebuild instsetoo_native.
I
Hallo,
> -Original Message-
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Sunday, January 13, 2019 11:22 PM
> To: dev-de@openoffice.apache.org
> Subject: Re: Saturn verkauft Open Office
>
> Interessant. Vielleicht gäbe es eine Option Verkäufer von
> OpenOffice für
> eine
Hi Dustin,
OpenOffice is an old project. The code has been touched by many people.
OpenOffice is also a multi language project.
Parts of it are written in c, c++ or a mix of both. We got java and
python code. The build environment is written in perl and bash. We use
in parts dmake, gmake and
That loop happens when one or more files can't be found.
The problem was that the path was wrong:
bridges/source/cpp_uno/s5abi_macosx_x86_64
instead of:
bridges/source/cpp_uno/s5abi_macosx_x86-64
(the last separator is a minus, not an underscore).
Fix committed in 1851285.
Damjan
On Mon, Jan
Hi Mechtilde,
Am 14.01.19 um 17:49 schrieb Mechtilde:
> Hello,
>
> we should prepare a build for Dutch (nl) and Turkish (tr) because they
> have 100 % Ui translation and for Dutch there is the help 100 5
> translated too.
I will add Turkish to my builds... (NL is already there)
Regards,
Hello,
we should prepare a build for Dutch (nl) and Turkish (tr) because they
have 100 % Ui translation and for Dutch there is the help 100 5
translated too.
Mechtilde
Am 14.01.19 um 17:38 schrieb Jim Jagielski:
> That's great. thx
>
>> On Jan 14, 2019, at 11:28 AM, Matthias Seidel
>> wrote:
That's great. thx
> On Jan 14, 2019, at 11:28 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 14.01.19 um 16:52 schrieb Jim Jagielski:
>> This week I plan on building AOO42X on our "official" Linux
>> and macOS build platforms (VMs)... just to allow us to do a
>> quick check that all looks
Hi Jim,
Am 14.01.19 um 16:52 schrieb Jim Jagielski:
> This week I plan on building AOO42X on our "official" Linux
> and macOS build platforms (VMs)... just to allow us to do a
> quick check that all looks reasonable at this point in time.
Since I am building on a regular base [1], I can provide
+1 from me
up to the time of a beta release
Mechtilde
Am 14.01.19 um 16:46 schrieb Jim Jagielski:
> At this stage, I think just back porting (svn merge) to the AOO42X branch is
> fine.
> As we get close to a release, we'll need to either have an RM approve it
> or so something like creating a
This week I plan on building AOO42X on our "official" Linux
and macOS build platforms (VMs)... just to allow us to do a
quick check that all looks reasonable at this point in time.
-
To unsubscribe, e-mail:
Sorry... I'm not seeing in this thread any pointers to how to update it...
I see a link to the translate.a.o URL, and something about 'next upload'
and 'gsicheck' and how it isn't possible to 'do the things automatically'
but nothing that indicates how someone does the process.
This looks like
At this stage, I think just back porting (svn merge) to the AOO42X branch is
fine.
As we get close to a release, we'll need to either have an RM approve it
or so something like creating a STATUS file, with a list of proposed backports
and requiring at least 3 +1s to backport (ie: RTC)
> On Jan
Hi Jim,
Am 09.01.19 um 21:54 schrieb Jim Jagielski:
>
>> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>>
>> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
>> thinking...
How is the process to get commits merged from trunk to AOO42X?
I adjusted some pointers for
Hello Jim,
Am 14.01.19 um 14:54 schrieb Jim Jagielski:
> How does one update the SDF file? What's the process?
as already described yesterday in this thread.
I want to update the sdf files to have an recent translation in the beta
version. Then the next time will be befor the release.
At this
Hi Jim,
Am 14.01.19 um 14:54 schrieb Jim Jagielski:
> How does one update the SDF file? What's the process?
It is a centralized export from our Pootle server. See Mechtilde's mail,
she is documenting the process at the moment...
Regards,
Matthias
>
> tia
>
>> On Jan 11, 2019, at 5:09 PM,
=
Building module bridges
=
Entering /Users/jim/src/asf/trunk/main/bridges/prj
cd .. && make -s -r -j6 && make -s -r deliverlog
[ build PVTUNOTYPES ]
[ build PVTUNOTYPES ]
[ build CXX ] bridges/source/jni_uno/jni_bridge
[ build CXX ] bridges/source/jni_uno/jni_data
[
How does one update the SDF file? What's the process?
tia
> On Jan 11, 2019, at 5:09 PM, Matthias Seidel
> wrote:
>
> Am 11.01.19 um 23:07 schrieb Marcus:
>> Am 11.01.19 um 23:02 schrieb Jim Jagielski:
>>> Just noticed this... not sure if it's just happening during my
>>> macOS builds or with
23 matches
Mail list logo
