Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Marcus 

Am 22.10.2018 um 18:34 schrieb Jim Jagielski:

All done. hash-sign-512 removed as a consequence.


wow, that was fast. :-)

Thanks

Marcus




On Oct 22, 2018, at 12:28 PM, Matthias Seidel  
wrote:

Hi Peter,

Am 22.10.18 um 02:10 schrieb Peter kovacs:

Stupid question where is the script?


https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/

  - hash-sign.sh generates ASC, MD5 and SHA256

  - hash-sign-512.sh generates ASC, MD5 and SHA512

We must not provide MD5 anymore and Marcus would prefer to offer ASC,
SHA256 and SHA512 on our download page.

So we would need a modified script now.

Regards,

Matthias



Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
:

Am 21.10.18 um 23:55 schrieb Marcus:

Am 21.10.2018 um 23:27 schrieb Matthias Seidel:

Am 21.10.18 um 22:43 schrieb Peter kovacs:

When the year issue has been fixed, I think we can call it an RC1.

I

check tomorrow evening. Sorry had no energy for stuff on the

weekend.

How do we want to sign the builds?

"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and

SHOULD

NOT supply MD5 or SHA-1" [1]

My suggestion would be to only supply SHA512.

I don't see a problem to support also SHA256. And it's less work to
re-write the download scripting.

OK, then someone has to work on the signing script... ;-)

Matthias


Marcus




Signatures and checksums could be generated with:


https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh


[1] https://www.apache.org/dev/release-distribution#sigs-and-sums


Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
:

Am 21.10.18 um 20:08 schrieb Marcus:

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.

copyright years are always forgotten to update. Every year the

same.

;-)

In fact I *did* update it for trunk in January... ;-)

hm, OK. Are you sure that you have updated it everywhere it is

needed?

Even here the script could be helpful.

I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should

get

some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias


Marcus




But my test build are always with --with-vendor in configure, so

I

didn't realize that it was missing from branch 4.1.6.

Matthias


We now have a script to update version numbers; somewhere in

the

devtools I think.

What about to create a new script to list all the code lines

with a

the year number. Then someone can have a look and compare it

with

the

current calendar year and if needed create a patch to update

all

affected year numbers at ones.

Maybe a good first step because no year number is forgotten.

The

next

one would be to automate this update. But I've not yet an idea

how

to

do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!

Fixed in r1844422 and r1844423

That means, when using --vendor it is updated automatically,
otherwise not?


On Oct 20, 2018, at 10:54 AM, Jim Jagielski



wrote:

Are we sure that that part of the splash screen isn't

hardcoded

in

(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice

Community

Build" \' for macOS and I am guessing the buildbots also

use

that

configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino



wrote:

That is probably because your OS is named Darwin (more
evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski



wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org >

wrote:

 But even if I wanted, I can not change the

copyright

year...

 That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



 BTW: Can you confirm 2017 as copyright year in

Jim's

Linux

builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Kay Schenk 
Installed the Linux 64-bit, en-US rpm version (yes, I've FINALLY 
switched over). So far, so good. Thanks.


On 10/19/2018 01:14 PM, Jim Jagielski wrote:

Builds for macOS and Linux 64bit (CentOS5) can be found at:

 http://home.apache.org/~jim/AOO-builds/

32bit CentOS will either be over the weekend or Monday. If I didn't upload your 
lang of choice, let me know!


On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
wrote:

Hi Jim,

Am 19.10.18 um 18:17 schrieb Jim Jagielski:

My macOS builds are almost done; next up CentOS5 (Linux) ones.

Which langs would people like? I'll upload to my Apache people space.


It would be great if you could provide German for Linux.

I'd like to test it on a daily base...

Matthias



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Matthias Seidel 
Am 22.10.18 um 18:34 schrieb Jim Jagielski:
> All done. hash-sign-512 removed as a consequence.

Thanks!

>
>> On Oct 22, 2018, at 12:28 PM, Matthias Seidel  
>> wrote:
>>
>> Hi Peter,
>>
>> Am 22.10.18 um 02:10 schrieb Peter kovacs:
>>> Stupid question where is the script?
>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/
>>
>>  - hash-sign.sh generates ASC, MD5 and SHA256
>>
>>  - hash-sign-512.sh generates ASC, MD5 and SHA512
>>
>> We must not provide MD5 anymore and Marcus would prefer to offer ASC,
>> SHA256 and SHA512 on our download page.
>>
>> So we would need a modified script now.
>>
>> Regards,
>>
>>Matthias
>>
>>> Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
>>> :
 Am 21.10.18 um 23:55 schrieb Marcus:
> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>> Am 21.10.18 um 22:43 schrieb Peter kovacs:
>>> When the year issue has been fixed, I think we can call it an RC1.
 I
>>> check tomorrow evening. Sorry had no energy for stuff on the
 weekend.
>> How do we want to sign the builds?
>>
>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
 SHOULD
>> NOT supply MD5 or SHA-1" [1]
>>
>> My suggestion would be to only supply SHA512.
> I don't see a problem to support also SHA256. And it's less work to
> re-write the download scripting.
 OK, then someone has to work on the signing script... ;-)

 Matthias

> Marcus
>
>
>
>> Signatures and checksums could be generated with:
>>
 https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>>
>>> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
>>> :
 Am 21.10.18 um 20:08 schrieb Marcus:
> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>> Am 21.10.18 um 19:59 schrieb Marcus:
>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
 That's what it looks like, yeah.
>>> copyright years are always forgotten to update. Every year the
 same.
>>> ;-)
>> In fact I *did* update it for trunk in January... ;-)
> hm, OK. Are you sure that you have updated it everywhere it is
 needed?
> Even here the script could be helpful.
 I did update it where we always(TM) updated it:
 https://svn.apache.org/viewvc?view=revisionrevision=1780015

 But there are several parts (ODK, Linux packaging) which should
 get
 some
 attention.
 In 4.1.x they were not updated in all these years...

 So +1 for a script from me!

 Matthias

> Marcus
>
>
>
>> But my test build are always with --with-vendor in configure, so
 I
>> didn't realize that it was missing from branch 4.1.6.
>>
>> Matthias
>>
>>> We now have a script to update version numbers; somewhere in
 the
>>> devtools I think.
>>>
>>> What about to create a new script to list all the code lines
 with a
>>> the year number. Then someone can have a look and compare it
 with
 the
>>> current calendar year and if needed create a patch to update
 all
>>> affected year numbers at ones.
>>>
>>> Maybe a good first step because no year number is forgotten.
 The
 next
>>> one would be to automate this update. But I've not yet an idea
 how
 to
>>> do this.
>>>
>>> What do you think?
>>>
>>> Marcus
>>>
>>>
>>>
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>  wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>> Fixed in r1844422 and r1844423
> That means, when using --vendor it is updated automatically,
> otherwise not?
>
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski
 
>>> wrote:
>>>
>>> Are we sure that that part of the splash screen isn't
 hardcoded
 in
>>> (ie: the Copyright part)?
>>>
>>> I know that I use '--with-vendor="Apache OpenOffice
 Community
>>> Build" \' for macOS and I am guessing the buildbots also
 use
 that
>>> configure option, so maybe that's a clue.
>>>
 On Oct 20, 2018, at 9:45 AM, Pedro Lino
 
 wrote:

 That is probably because your OS is named Darwin (more
 evolved?) :)



 



> On

Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Jim Jagielski 
All done. hash-sign-512 removed as a consequence.

> On Oct 22, 2018, at 12:28 PM, Matthias Seidel  
> wrote:
> 
> Hi Peter,
> 
> Am 22.10.18 um 02:10 schrieb Peter kovacs:
>> Stupid question where is the script?
> 
> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/
> 
>  - hash-sign.sh generates ASC, MD5 and SHA256
> 
>  - hash-sign-512.sh generates ASC, MD5 and SHA512
> 
> We must not provide MD5 anymore and Marcus would prefer to offer ASC,
> SHA256 and SHA512 on our download page.
> 
> So we would need a modified script now.
> 
> Regards,
> 
>Matthias
> 
>> 
>> Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
>> :
>>> Am 21.10.18 um 23:55 schrieb Marcus:
 Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
> Am 21.10.18 um 22:43 schrieb Peter kovacs:
>> When the year issue has been fixed, I think we can call it an RC1.
>>> I
>> check tomorrow evening. Sorry had no energy for stuff on the
>>> weekend.
> How do we want to sign the builds?
> 
> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>>> SHOULD
> NOT supply MD5 or SHA-1" [1]
> 
> My suggestion would be to only supply SHA512.
 I don't see a problem to support also SHA256. And it's less work to
 re-write the download scripting.
>>> OK, then someone has to work on the signing script... ;-)
>>> 
>>> Matthias
>>> 
 Marcus
 
 
 
> Signatures and checksums could be generated with:
> 
>>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
> 
> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
> 
>> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
>> :
>>> Am 21.10.18 um 20:08 schrieb Marcus:
 Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
> Am 21.10.18 um 19:59 schrieb Marcus:
>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>>> That's what it looks like, yeah.
>> copyright years are always forgotten to update. Every year the
>>> same.
>> ;-)
> In fact I *did* update it for trunk in January... ;-)
 hm, OK. Are you sure that you have updated it everywhere it is
>>> needed?
 Even here the script could be helpful.
>>> I did update it where we always(TM) updated it:
>>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>>> 
>>> But there are several parts (ODK, Linux packaging) which should
>>> get
>>> some
>>> attention.
>>> In 4.1.x they were not updated in all these years...
>>> 
>>> So +1 for a script from me!
>>> 
>>> Matthias
>>> 
 Marcus
 
 
 
> But my test build are always with --with-vendor in configure, so
>>> I
> didn't realize that it was missing from branch 4.1.6.
> 
> Matthias
> 
>> We now have a script to update version numbers; somewhere in
>>> the
>> devtools I think.
>> 
>> What about to create a new script to list all the code lines
>>> with a
>> the year number. Then someone can have a look and compare it
>>> with
>>> the
>> current calendar year and if needed create a patch to update
>>> all
>> affected year numbers at ones.
>> 
>> Maybe a good first step because no year number is forgotten.
>>> The
>>> next
>> one would be to automate this update. But I've not yet an idea
>>> how
>>> to
>> do this.
>> 
>> What do you think?
>> 
>> Marcus
>> 
>> 
>> 
 On Oct 20, 2018, at 11:20 AM, Matthias Seidel
  wrote:
 
 Am 20.10.18 um 17:16 schrieb Jim Jagielski:
> Found it.
 Great!
> Fixed in r1844422 and r1844423
 That means, when using --vendor it is updated automatically,
 otherwise not?
 
>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski
>>> 
>> wrote:
>> 
>> Are we sure that that part of the splash screen isn't
>>> hardcoded
>>> in
>> (ie: the Copyright part)?
>> 
>> I know that I use '--with-vendor="Apache OpenOffice
>>> Community
>> Build" \' for macOS and I am guessing the buildbots also
>>> use
>>> that
>> configure option, so maybe that's a clue.
>> 
>>> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>>> 
>>> wrote:
>>> 
>>> That is probably because your OS is named Darwin (more
>>> evolved?) :)
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
 On October 20, 2018 at 2:35 PM Jim Jagielski
>>> 
 wrote:
 
 Hmmm... The macOS builds are showing 2018:

Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Matthias Seidel 
Hi Peter,

Am 22.10.18 um 02:10 schrieb Peter kovacs:
> Stupid question where is the script?

https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/

 - hash-sign.sh generates ASC, MD5 and SHA256

 - hash-sign-512.sh generates ASC, MD5 and SHA512

We must not provide MD5 anymore and Marcus would prefer to offer ASC,
SHA256 and SHA512 on our download page.

So we would need a modified script now.

Regards,

   Matthias

>
> Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
> :
>> Am 21.10.18 um 23:55 schrieb Marcus:
>>> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
 Am 21.10.18 um 22:43 schrieb Peter kovacs:
> When the year issue has been fixed, I think we can call it an RC1.
>> I
> check tomorrow evening. Sorry had no energy for stuff on the
>> weekend.
 How do we want to sign the builds?

 "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>> SHOULD
 NOT supply MD5 or SHA-1" [1]

 My suggestion would be to only supply SHA512.
>>> I don't see a problem to support also SHA256. And it's less work to
>>> re-write the download scripting.
>> OK, then someone has to work on the signing script... ;-)
>>
>> Matthias
>>
>>> Marcus
>>>
>>>
>>>
 Signatures and checksums could be generated with:

>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh

 [1] https://www.apache.org/dev/release-distribution#sigs-and-sums

> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
> :
>> Am 21.10.18 um 20:08 schrieb Marcus:
>>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
 Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
> copyright years are always forgotten to update. Every year the
>> same.
> ;-)
 In fact I *did* update it for trunk in January... ;-)
>>> hm, OK. Are you sure that you have updated it everywhere it is
>> needed?
>>> Even here the script could be helpful.
>> I did update it where we always(TM) updated it:
>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>>
>> But there are several parts (ODK, Linux packaging) which should
>> get
>> some
>> attention.
>> In 4.1.x they were not updated in all these years...
>>
>> So +1 for a script from me!
>>
>> Matthias
>>
>>> Marcus
>>>
>>>
>>>
 But my test build are always with --with-vendor in configure, so
>> I
 didn't realize that it was missing from branch 4.1.6.

 Matthias

> We now have a script to update version numbers; somewhere in
>> the
> devtools I think.
>
> What about to create a new script to list all the code lines
>> with a
> the year number. Then someone can have a look and compare it
>> with
>> the
> current calendar year and if needed create a patch to update
>> all
> affected year numbers at ones.
>
> Maybe a good first step because no year number is forgotten.
>> The
>> next
> one would be to automate this update. But I've not yet an idea
>> how
>> to
> do this.
>
> What do you think?
>
> Marcus
>
>
>
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!
 Fixed in r1844422 and r1844423
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>>
> On Oct 20, 2018, at 10:54 AM, Jim Jagielski
>> 
> wrote:
>
> Are we sure that that part of the splash screen isn't
>> hardcoded
>> in
> (ie: the Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice
>> Community
> Build" \' for macOS and I am guessing the buildbots also
>> use
>> that
> configure option, so maybe that's a clue.
>
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>> 
>> wrote:
>>
>> That is probably because your OS is named Darwin (more
>> evolved?) :)
>>
>>
>>
>> 
>>
>>
>>
>>> On October 20, 2018 at 2:35 PM Jim Jagielski
>> 
>>> wrote:
>>>
>>> Hmmm... The macOS builds are showing 2018:
>>>
>>> 
>>>
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org >
>> wrote:
>     But even if I wanted, I can not change the
>> copyright
>> year...
>     That's what I am

Re: Test builds of AOO 4.1.6 HEAD

2018-10-22 Thread Jim Jagielski 
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts

> On Oct 21, 2018, at 8:10 PM, Peter kovacs  wrote:
> 
> Stupid question where is the script?
> 
> Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
> :
>> Am 21.10.18 um 23:55 schrieb Marcus:
>>> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
 Am 21.10.18 um 22:43 schrieb Peter kovacs:
> 
> When the year issue has been fixed, I think we can call it an RC1.
>> I
> check tomorrow evening. Sorry had no energy for stuff on the
>> weekend.
 
 How do we want to sign the builds?
 
 "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>> SHOULD
 NOT supply MD5 or SHA-1" [1]
 
 My suggestion would be to only supply SHA512.
>>> 
>>> I don't see a problem to support also SHA256. And it's less work to
>>> re-write the download scripting.
>> 
>> OK, then someone has to work on the signing script... ;-)
>> 
>> Matthias
>> 
>>> 
>>> Marcus
>>> 
>>> 
>>> 
 Signatures and checksums could be generated with:
 
>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
 
 
 [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
 
> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
> :
>> Am 21.10.18 um 20:08 schrieb Marcus:
>>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
 Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
> copyright years are always forgotten to update. Every year the
>> same.
> ;-)
 In fact I *did* update it for trunk in January... ;-)
>>> hm, OK. Are you sure that you have updated it everywhere it is
>> needed?
>>> Even here the script could be helpful.
>> I did update it where we always(TM) updated it:
>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>> 
>> But there are several parts (ODK, Linux packaging) which should
>> get
>> some
>> attention.
>> In 4.1.x they were not updated in all these years...
>> 
>> So +1 for a script from me!
>> 
>> Matthias
>> 
>>> Marcus
>>> 
>>> 
>>> 
 But my test build are always with --with-vendor in configure, so
>> I
 didn't realize that it was missing from branch 4.1.6.
 
 Matthias
 
> We now have a script to update version numbers; somewhere in
>> the
> devtools I think.
> 
> What about to create a new script to list all the code lines
>> with a
> the year number. Then someone can have a look and compare it
>> with
>> the
> current calendar year and if needed create a patch to update
>> all
> affected year numbers at ones.
> 
> Maybe a good first step because no year number is forgotten.
>> The
>> next
> one would be to automate this update. But I've not yet an idea
>> how
>> to
> do this.
> 
> What do you think?
> 
> Marcus
> 
> 
> 
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>> 
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!
 Fixed in r1844422 and r1844423
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>> 
> On Oct 20, 2018, at 10:54 AM, Jim Jagielski
>> 
> wrote:
> 
> Are we sure that that part of the splash screen isn't
>> hardcoded
>> in
> (ie: the Copyright part)?
> 
> I know that I use '--with-vendor="Apache OpenOffice
>> Community
> Build" \' for macOS and I am guessing the buildbots also
>> use
>> that
> configure option, so maybe that's a clue.
> 
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>> 
>> wrote:
>> 
>> That is probably because your OS is named Darwin (more
>> evolved?) :)
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On October 20, 2018 at 2:35 PM Jim Jagielski
>> 
>>> wrote:
>>> 
>>> Hmmm... The macOS builds are showing 2018:
>>> 
>>> 
>>> 
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org >
>> wrote:
> But even if I wanted, I can not change the
>> copyright
>> year...
> That's what I am wondering about. ;-)
> 
 Ok. I (wrongly) assumed it was all editable :)
 
 
> BTW: Can you confirm 2017 as copyright year

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Peter kovacs 
Stupid question where is the script?

Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 23:55 schrieb Marcus:
>> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>>> Am 21.10.18 um 22:43 schrieb Peter kovacs:

 When the year issue has been fixed, I think we can call it an RC1.
>I
 check tomorrow evening. Sorry had no energy for stuff on the
>weekend.
>>>
>>> How do we want to sign the builds?
>>>
>>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>SHOULD
>>> NOT supply MD5 or SHA-1" [1]
>>>
>>> My suggestion would be to only supply SHA512.
>>
>> I don't see a problem to support also SHA256. And it's less work to
>> re-write the download scripting.
>
>OK, then someone has to work on the signing script... ;-)
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> Signatures and checksums could be generated with:
>>>
>https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>>>
>>>
>>> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>>>
 Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
 :
> Am 21.10.18 um 20:08 schrieb Marcus:
>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>> Am 21.10.18 um 19:59 schrieb Marcus:
 Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
> That's what it looks like, yeah.
 copyright years are always forgotten to update. Every year the
> same.
 ;-)
>>> In fact I *did* update it for trunk in January... ;-)
>> hm, OK. Are you sure that you have updated it everywhere it is
> needed?
>> Even here the script could be helpful.
> I did update it where we always(TM) updated it:
> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>
> But there are several parts (ODK, Linux packaging) which should
>get
> some
> attention.
> In 4.1.x they were not updated in all these years...
>
> So +1 for a script from me!
>
> Matthias
>
>> Marcus
>>
>>
>>
>>> But my test build are always with --with-vendor in configure, so
>I
>>> didn't realize that it was missing from branch 4.1.6.
>>>
>>> Matthias
>>>
 We now have a script to update version numbers; somewhere in
>the
 devtools I think.

 What about to create a new script to list all the code lines
>with a
 the year number. Then someone can have a look and compare it
>with
> the
 current calendar year and if needed create a patch to update
>all
 affected year numbers at ones.

 Maybe a good first step because no year number is forgotten.
>The
> next
 one would be to automate this update. But I've not yet an idea
>how
> to
 do this.

 What do you think?

 Marcus



>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>  wrote:
>>
>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>>> Found it.
>> Great!
>>> Fixed in r1844422 and r1844423
>> That means, when using --vendor it is updated automatically,
>> otherwise not?
>>
 On Oct 20, 2018, at 10:54 AM, Jim Jagielski
>
 wrote:

 Are we sure that that part of the splash screen isn't
>hardcoded
> in
 (ie: the Copyright part)?

 I know that I use '--with-vendor="Apache OpenOffice
>Community
 Build" \' for macOS and I am guessing the buildbots also
>use
> that
 configure option, so maybe that's a clue.

> On Oct 20, 2018, at 9:45 AM, Pedro Lino
> 
> wrote:
>
> That is probably because your OS is named Darwin (more
> evolved?) :)
>
>
>
> 
>
>
>
>> On October 20, 2018 at 2:35 PM Jim Jagielski
> 
>> wrote:
>>
>> Hmmm... The macOS builds are showing 2018:
>>
>> 
>>
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>>> pedro.l...@mailbox.org >
> wrote:
     But even if I wanted, I can not change the
>copyright
> year...
     That's what I am wondering about. ;-)

>>> Ok. I (wrongly) assumed it was all editable :)
>>>
>>>
     BTW: Can you confirm 2017 as copyright year in
>Jim's
> Linux
 builds?


>>> Yes, Jim's build is showing 2017.
>>>
>>>
>>> Regards,
>>>
>>> Pedro
>>
>>
>> -
>> To unsubscribe, e-mail:

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 23:55 schrieb Marcus:
> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>> Am 21.10.18 um 22:43 schrieb Peter kovacs:
>>>
>>> When the year issue has been fixed, I think we can call it an RC1. I
>>> check tomorrow evening. Sorry had no energy for stuff on the weekend.
>>
>> How do we want to sign the builds?
>>
>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
>> NOT supply MD5 or SHA-1" [1]
>>
>> My suggestion would be to only supply SHA512.
>
> I don't see a problem to support also SHA256. And it's less work to
> re-write the download scripting.

OK, then someone has to work on the signing script... ;-)

Matthias

>
> Marcus
>
>
>
>> Signatures and checksums could be generated with:
>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>>
>>
>> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>>
>>> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
>>> :
 Am 21.10.18 um 20:08 schrieb Marcus:
> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>> Am 21.10.18 um 19:59 schrieb Marcus:
>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
 That's what it looks like, yeah.
>>> copyright years are always forgotten to update. Every year the
 same.
>>> ;-)
>> In fact I *did* update it for trunk in January... ;-)
> hm, OK. Are you sure that you have updated it everywhere it is
 needed?
> Even here the script could be helpful.
 I did update it where we always(TM) updated it:
 https://svn.apache.org/viewvc?view=revisionrevision=1780015

 But there are several parts (ODK, Linux packaging) which should get
 some
 attention.
 In 4.1.x they were not updated in all these years...

 So +1 for a script from me!

 Matthias

> Marcus
>
>
>
>> But my test build are always with --with-vendor in configure, so I
>> didn't realize that it was missing from branch 4.1.6.
>>
>> Matthias
>>
>>> We now have a script to update version numbers; somewhere in the
>>> devtools I think.
>>>
>>> What about to create a new script to list all the code lines with a
>>> the year number. Then someone can have a look and compare it with
 the
>>> current calendar year and if needed create a patch to update all
>>> affected year numbers at ones.
>>>
>>> Maybe a good first step because no year number is forgotten. The
 next
>>> one would be to automate this update. But I've not yet an idea how
 to
>>> do this.
>>>
>>> What do you think?
>>>
>>> Marcus
>>>
>>>
>>>
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>  wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>> Fixed in r1844422 and r1844423
> That means, when using --vendor it is updated automatically,
> otherwise not?
>
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
>>> wrote:
>>>
>>> Are we sure that that part of the splash screen isn't hardcoded
 in
>>> (ie: the Copyright part)?
>>>
>>> I know that I use '--with-vendor="Apache OpenOffice Community
>>> Build" \' for macOS and I am guessing the buildbots also use
 that
>>> configure option, so maybe that's a clue.
>>>
 On Oct 20, 2018, at 9:45 AM, Pedro Lino
 
 wrote:

 That is probably because your OS is named Darwin (more
 evolved?) :)



 



> On October 20, 2018 at 2:35 PM Jim Jagielski
 
> wrote:
>
> Hmmm... The macOS builds are showing 2018:
>
> 
>
>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>> pedro.l...@mailbox.org >
 wrote:
>>>     But even if I wanted, I can not change the copyright
 year...
>>>     That's what I am wondering about. ;-)
>>>
>> Ok. I (wrongly) assumed it was all editable :)
>>
>>
>>>     BTW: Can you confirm 2017 as copyright year in Jim's
 Linux
>>> builds?
>>>
>>>
>> Yes, Jim's build is showing 2017.
>>
>>
>> Regards,
>>
>> Pedro
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 22:43 schrieb Peter kovacs:


When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.


just to prevent misunderstandings:

My suggestion was a general improvement and not limited to this release. 
Of course the 4.1.6 should not wait for this.


Marcus




Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:

Am 21.10.18 um 20:08 schrieb Marcus:

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the

same.

;-)


In fact I *did* update it for trunk in January... ;-)


hm, OK. Are you sure that you have updated it everywhere it is

needed?

Even here the script could be helpful.


I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get
some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias



Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias



We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with

the

current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The

next

one would be to automate this update. But I've not yet an idea how

to

do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically,
otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
wrote:

Are we sure that that part of the splash screen isn't hardcoded

in

(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use

that

configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino



wrote:

That is probably because your OS is named Darwin (more
evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski



wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org >

wrote:



    But even if I wanted, I can not change the copyright

year...

    That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



    BTW: Can you confirm 2017 as copyright year in Jim's

Linux

builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 23:27 schrieb Matthias Seidel:

Am 21.10.18 um 22:43 schrieb Peter kovacs:


When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.


How do we want to sign the builds?

"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
NOT supply MD5 or SHA-1" [1]

My suggestion would be to only supply SHA512.


I don't see a problem to support also SHA256. And it's less work to 
re-write the download scripting.


Marcus




Signatures and checksums could be generated with:
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh

[1] https://www.apache.org/dev/release-distribution#sigs-and-sums


Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:

Am 21.10.18 um 20:08 schrieb Marcus:

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.

copyright years are always forgotten to update. Every year the

same.

;-)

In fact I *did* update it for trunk in January... ;-)

hm, OK. Are you sure that you have updated it everywhere it is

needed?

Even here the script could be helpful.

I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get
some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias


Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias


We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with

the

current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The

next

one would be to automate this update. But I've not yet an idea how

to

do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!

Fixed in r1844422 and r1844423

That means, when using --vendor it is updated automatically,
otherwise not?


On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
wrote:

Are we sure that that part of the splash screen isn't hardcoded

in

(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use

that

configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino



wrote:

That is probably because your OS is named Darwin (more
evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski



wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org >

wrote:

    But even if I wanted, I can not change the copyright

year...

    That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



    BTW: Can you confirm 2017 as copyright year in Jim's

Linux

builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Hi Peter,

Am 21.10.18 um 22:43 schrieb Peter kovacs:
> Hi all.
>
> When the year issue has been fixed, I think we can call it an RC1. I check 
> tomorrow evening. Sorry had no energy for stuff on the weekend.

How do we want to sign the builds?

"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
NOT supply MD5 or SHA-1" [1]

My suggestion would be to only supply SHA512.

Signatures and checksums could be generated with:
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh

Regards,

   Matthias

[1] https://www.apache.org/dev/release-distribution#sigs-and-sums

>
> All the best
>  Peter
>
> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
> :
>> Am 21.10.18 um 20:08 schrieb Marcus:
>>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
 Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
> copyright years are always forgotten to update. Every year the
>> same.
> ;-)
 In fact I *did* update it for trunk in January... ;-)
>>> hm, OK. Are you sure that you have updated it everywhere it is
>> needed?
>>> Even here the script could be helpful.
>> I did update it where we always(TM) updated it:
>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>>
>> But there are several parts (ODK, Linux packaging) which should get
>> some
>> attention.
>> In 4.1.x they were not updated in all these years...
>>
>> So +1 for a script from me!
>>
>> Matthias
>>
>>> Marcus
>>>
>>>
>>>
 But my test build are always with --with-vendor in configure, so I
 didn't realize that it was missing from branch 4.1.6.

 Matthias

> We now have a script to update version numbers; somewhere in the
> devtools I think.
>
> What about to create a new script to list all the code lines with a
> the year number. Then someone can have a look and compare it with
>> the
> current calendar year and if needed create a patch to update all
> affected year numbers at ones.
>
> Maybe a good first step because no year number is forgotten. The
>> next
> one would be to automate this update. But I've not yet an idea how
>> to
> do this.
>
> What do you think?
>
> Marcus
>
>
>
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!
 Fixed in r1844422 and r1844423
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>>
> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
> wrote:
>
> Are we sure that that part of the splash screen isn't hardcoded
>> in
> (ie: the Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice Community
> Build" \' for macOS and I am guessing the buildbots also use
>> that
> configure option, so maybe that's a clue.
>
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>> 
>> wrote:
>>
>> That is probably because your OS is named Darwin (more
>> evolved?) :)
>>
>>
>>
>> 
>>
>>
>>
>>> On October 20, 2018 at 2:35 PM Jim Jagielski
>> 
>>> wrote:
>>>
>>> Hmmm... The macOS builds are showing 2018:
>>>
>>> 
>>>
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org >
>> wrote:
>    But even if I wanted, I can not change the copyright
>> year...
>    That's what I am wondering about. ;-)
>
 Ok. I (wrongly) assumed it was all editable :)


>    BTW: Can you confirm 2017 as copyright year in Jim's
>> Linux
> builds?
>
>
 Yes, Jim's build is showing 2017.


 Regards,

 Pedro
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Peter kovacs 
Hi all.

When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.

All the best
 Peter

Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 20:08 schrieb Marcus:
>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>> Am 21.10.18 um 19:59 schrieb Marcus:
 Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
> That's what it looks like, yeah.

 copyright years are always forgotten to update. Every year the
>same.
 ;-)
>>>
>>> In fact I *did* update it for trunk in January... ;-)
>>
>> hm, OK. Are you sure that you have updated it everywhere it is
>needed?
>> Even here the script could be helpful.
>
>I did update it where we always(TM) updated it:
>https://svn.apache.org/viewvc?view=revisionrevision=1780015
>
>But there are several parts (ODK, Linux packaging) which should get
>some
>attention.
>In 4.1.x they were not updated in all these years...
>
>So +1 for a script from me!
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> But my test build are always with --with-vendor in configure, so I
>>> didn't realize that it was missing from branch 4.1.6.
>>>
>>> Matthias
>>>

 We now have a script to update version numbers; somewhere in the
 devtools I think.

 What about to create a new script to list all the code lines with a
 the year number. Then someone can have a look and compare it with
>the
 current calendar year and if needed create a patch to update all
 affected year numbers at ones.

 Maybe a good first step because no year number is forgotten. The
>next
 one would be to automate this update. But I've not yet an idea how
>to
 do this.

 What do you think?

 Marcus



>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>  wrote:
>>
>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>>> Found it.
>> Great!
>>>
>>> Fixed in r1844422 and r1844423
>>
>> That means, when using --vendor it is updated automatically,
>> otherwise not?
>>
>>>
 On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
 wrote:

 Are we sure that that part of the splash screen isn't hardcoded
>in
 (ie: the Copyright part)?

 I know that I use '--with-vendor="Apache OpenOffice Community
 Build" \' for macOS and I am guessing the buildbots also use
>that
 configure option, so maybe that's a clue.

> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>
> wrote:
>
> That is probably because your OS is named Darwin (more
> evolved?) :)
>
>
>
> 
>
>
>
>> On October 20, 2018 at 2:35 PM Jim Jagielski
>
>> wrote:
>>
>> Hmmm... The macOS builds are showing 2018:
>>
>> 
>>
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>>> pedro.l...@mailbox.org >
>wrote:
>>>
    But even if I wanted, I can not change the copyright
>year...
    That's what I am wondering about. ;-)

>>> Ok. I (wrongly) assumed it was all editable :)
>>>
>>>
    BTW: Can you confirm 2017 as copyright year in Jim's
>Linux
 builds?


>>> Yes, Jim's build is showing 2017.
>>>
>>>
>>> Regards,
>>>
>>> Pedro
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 20:08 schrieb Marcus:
> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>> Am 21.10.18 um 19:59 schrieb Marcus:
>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
 That's what it looks like, yeah.
>>>
>>> copyright years are always forgotten to update. Every year the same.
>>> ;-)
>>
>> In fact I *did* update it for trunk in January... ;-)
>
> hm, OK. Are you sure that you have updated it everywhere it is needed?
> Even here the script could be helpful.

I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias

>
> Marcus
>
>
>
>> But my test build are always with --with-vendor in configure, so I
>> didn't realize that it was missing from branch 4.1.6.
>>
>> Matthias
>>
>>>
>>> We now have a script to update version numbers; somewhere in the
>>> devtools I think.
>>>
>>> What about to create a new script to list all the code lines with a
>>> the year number. Then someone can have a look and compare it with the
>>> current calendar year and if needed create a patch to update all
>>> affected year numbers at ones.
>>>
>>> Maybe a good first step because no year number is forgotten. The next
>>> one would be to automate this update. But I've not yet an idea how to
>>> do this.
>>>
>>> What do you think?
>>>
>>> Marcus
>>>
>>>
>>>
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>  wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>>
>> Fixed in r1844422 and r1844423
>
> That means, when using --vendor it is updated automatically,
> otherwise not?
>
>>
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
>>> wrote:
>>>
>>> Are we sure that that part of the splash screen isn't hardcoded in
>>> (ie: the Copyright part)?
>>>
>>> I know that I use '--with-vendor="Apache OpenOffice Community
>>> Build" \' for macOS and I am guessing the buildbots also use that
>>> configure option, so maybe that's a clue.
>>>
 On Oct 20, 2018, at 9:45 AM, Pedro Lino 
 wrote:

 That is probably because your OS is named Darwin (more
 evolved?) :)



 



> On October 20, 2018 at 2:35 PM Jim Jagielski 
> wrote:
>
> Hmmm... The macOS builds are showing 2018:
>
> 
>
>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>> pedro.l...@mailbox.org > wrote:
>>
>>>    But even if I wanted, I can not change the copyright year...
>>>    That's what I am wondering about. ;-)
>>>
>> Ok. I (wrongly) assumed it was all editable :)
>>
>>
>>>    BTW: Can you confirm 2017 as copyright year in Jim's Linux
>>> builds?
>>>
>>>
>> Yes, Jim's build is showing 2017.
>>
>>
>> Regards,
>>
>> Pedro
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the same. ;-)


In fact I *did* update it for trunk in January... ;-)


hm, OK. Are you sure that you have updated it everywhere it is needed? 
Even here the script could be helpful.


Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias



We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with the
current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The next
one would be to automate this update. But I've not yet an idea how to
do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically,
otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:

Are we sure that that part of the splash screen isn't hardcoded in
(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use that
configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino 
wrote:

That is probably because your OS is named Darwin (more evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski 
wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org > wrote:


   But even if I wanted, I can not change the copyright year...
   That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



   BTW: Can you confirm 2017 as copyright year in Jim's Linux
builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
>
> copyright years are always forgotten to update. Every year the same. ;-)

In fact I *did* update it for trunk in January... ;-)

But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias

>
> We now have a script to update version numbers; somewhere in the
> devtools I think.
>
> What about to create a new script to list all the code lines with a
> the year number. Then someone can have a look and compare it with the
> current calendar year and if needed create a patch to update all
> affected year numbers at ones.
>
> Maybe a good first step because no year number is forgotten. The next
> one would be to automate this update. But I've not yet an idea how to
> do this.
>
> What do you think?
>
> Marcus
>
>
>
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!

 Fixed in r1844422 and r1844423
>>>
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>>

> On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:
>
> Are we sure that that part of the splash screen isn't hardcoded in
> (ie: the Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice Community
> Build" \' for macOS and I am guessing the buildbots also use that
> configure option, so maybe that's a clue.
>
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino 
>> wrote:
>>
>> That is probably because your OS is named Darwin (more evolved?) :)
>>
>>
>>
>> 
>>
>>
>>
>>> On October 20, 2018 at 2:35 PM Jim Jagielski 
>>> wrote:
>>>
>>> Hmmm... The macOS builds are showing 2018:
>>>
>>> 
>>>
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org > wrote:

>   But even if I wanted, I can not change the copyright year...
>   That's what I am wondering about. ;-)
>
 Ok. I (wrongly) assumed it was all editable :)


>   BTW: Can you confirm 2017 as copyright year in Jim's Linux
> builds?
>
>
 Yes, Jim's build is showing 2017.


 Regards,

 Pedro
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the same. ;-)

We now have a script to update version numbers; somewhere in the 
devtools I think.


What about to create a new script to list all the code lines with a the 
year number. Then someone can have a look and compare it with the 
current calendar year and if needed create a patch to update all 
affected year numbers at ones.


Maybe a good first step because no year number is forgotten. The next 
one would be to automate this update. But I've not yet an idea how to do 
this.


What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel  
wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically, otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:

Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
macOS and I am guessing the buildbots also use that configure option, so maybe that's a 
clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:

That is probably because your OS is named Darwin (more evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski  wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
> wrote:


  But even if I wanted, I can not change the copyright year...
  That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



  BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Jim Jagielski 
All uploaded!

> On Oct 20, 2018, at 4:18 PM, Andrea Pescetti  wrote:
> 
> Jim Jagielski wrote:
>> Which langs would people like? I'll upload to my Apache people space.
> 
> Italian please. And thanks to both you and Matthias for providing the builds.
> 
> The Release Candidate will have to be called by Peter, but it looks like we 
> are not far...
> 
> Regards,
>  Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Andrea Pescetti 

Matthias Seidel wrote:

Am 20.10.18 um 22:18 schrieb Andrea Pescetti:

The Release Candidate will have to be called by Peter, but it looks
like we are not far...

Next week Marco Pinto will probably update the English dictionary.
Maybe we are ready until then?


We never depended on a dictionary. Actually things go the other way 
round, so historically we asked Marco to keep dictionary updates on hold 
for a few weeks while we had a new fresh release that was not containing 
the new dictionary version. I honestly wouldn't wait for a new release 
of the dictionary unless Marco (who reads this list) confirm that it is 
coming.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Am 20.10.18 um 22:18 schrieb Andrea Pescetti:
> Jim Jagielski wrote:
>> Which langs would people like? I'll upload to my Apache people space.
>
> Italian please. And thanks to both you and Matthias for providing the
> builds.
>
> The Release Candidate will have to be called by Peter, but it looks
> like we are not far...

Next week Marco Pinto will probably update the English dictionary.

Maybe we are ready until then?

Regards,

   Matthias

>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Andrea Pescetti 

Jim Jagielski wrote:

Which langs would people like? I'll upload to my Apache people space.


Italian please. And thanks to both you and Matthias for providing the 
builds.


The Release Candidate will have to be called by Peter, but it looks like 
we are not far...


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Jim Jagielski 
That's what it looks like, yeah.

> On Oct 20, 2018, at 11:20 AM, Matthias Seidel  
> wrote:
> 
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>> 
>> Fixed in r1844422 and r1844423
> 
> That means, when using --vendor it is updated automatically, otherwise not?
> 
>> 
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:
>>> 
>>> Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
>>> Copyright part)?
>>> 
>>> I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
>>> macOS and I am guessing the buildbots also use that configure option, so 
>>> maybe that's a clue.
>>> 
 On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:
 
 That is probably because your OS is named Darwin (more evolved?) :)
 
 
 
 
 
 
 
> On October 20, 2018 at 2:35 PM Jim Jagielski  wrote: 
> 
> Hmmm... The macOS builds are showing 2018:
> 
>  
> 
>> On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
>> > wrote:
>> 
>>>  But even if I wanted, I can not change the copyright year... 
>>>  That's what I am wondering about. ;-) 
>>> 
>> Ok. I (wrongly) assumed it was all editable :) 
>> 
>> 
>>>  BTW: Can you confirm 2017 as copyright year in Jim's Linux builds? 
>>> 
>>> 
>> Yes, Jim's build is showing 2017. 
>> 
>> 
>> Regards, 
>> 
>> Pedro 
 
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>>

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Am 20.10.18 um 17:16 schrieb Jim Jagielski:
> Found it.
Great!
>
> Fixed in r1844422 and r1844423

That means, when using --vendor it is updated automatically, otherwise not?

>
>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:
>>
>> Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
>> Copyright part)?
>>
>> I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
>> macOS and I am guessing the buildbots also use that configure option, so 
>> maybe that's a clue.
>>
>>> On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:
>>>
>>> That is probably because your OS is named Darwin (more evolved?) :)
>>>
>>>
>>>
>>> 
>>>
>>>
>>>
 On October 20, 2018 at 2:35 PM Jim Jagielski  wrote: 

 Hmmm... The macOS builds are showing 2018:

  

> On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
> > wrote:
>
>>   But even if I wanted, I can not change the copyright year... 
>>   That's what I am wondering about. ;-) 
>>
> Ok. I (wrongly) assumed it was all editable :) 
>
>
>>   BTW: Can you confirm 2017 as copyright year in Jim's Linux builds? 
>>
>>
> Yes, Jim's build is showing 2017. 
>
>
> Regards, 
>
> Pedro 
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Jim Jagielski 
Found it.

Fixed in r1844422 and r1844423

> On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:
> 
> Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
> Copyright part)?
> 
> I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
> macOS and I am guessing the buildbots also use that configure option, so 
> maybe that's a clue.
> 
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:
>> 
>> That is probably because your OS is named Darwin (more evolved?) :)
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On October 20, 2018 at 2:35 PM Jim Jagielski  wrote: 
>>> 
>>> Hmmm... The macOS builds are showing 2018:
>>> 
>>>  
>>> 
 On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
 > wrote:
 
>   But even if I wanted, I can not change the copyright year... 
>   That's what I am wondering about. ;-) 
> 
 
 Ok. I (wrongly) assumed it was all editable :) 
 
 
>   BTW: Can you confirm 2017 as copyright year in Jim's Linux builds? 
> 
> 
 
 Yes, Jim's build is showing 2017. 
 
 
 Regards, 
 
 Pedro 
>>> 
>> 
>> 
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Jim Jagielski 
Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
macOS and I am guessing the buildbots also use that configure option, so maybe 
that's a clue.

> On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:
> 
> That is probably because your OS is named Darwin (more evolved?) :)
> 
> 
> 
> 
> 
> 
> 
>> On October 20, 2018 at 2:35 PM Jim Jagielski  wrote: 
>> 
>> Hmmm... The macOS builds are showing 2018:
>> 
>>  
>> 
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
>>> > wrote:
>>> 
But even if I wanted, I can not change the copyright year... 
That's what I am wondering about. ;-) 
 
>>> 
>>> Ok. I (wrongly) assumed it was all editable :) 
>>> 
>>> 
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds? 
 
 
>>> 
>>> Yes, Jim's build is showing 2017. 
>>> 
>>> 
>>> Regards, 
>>> 
>>> Pedro 
>> 
> 
>  
>

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Jim Jagielski 
The only customizing on my builds is:

--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 


On Oct 20, 2018, at 7:04 AM, Pedro Lino  wrote:
> 
> Hi Matthias
> 
>> On October 20, 2018 at 11:26 AM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>> 
>> 
>> 
 I can confirm that it is running as expected under Ubuntu 16.04 x64 
 (Thanks Jim!)
>>> 
 
 The About box does have a quite different text compared from what is 
 produced by the buildbots.
>>> 
 
 https://i.imgur.com/3r5Btju.png
>>> 
Yes, of course!
>> 
>>We modified the text because many people used these builds for
>>"productive" work. ;-)
>> 
>>But the question remains why the copyright year is different?
>> 
> 
> 
> I am aware of the Buildbot differences...
> 
> What I was referring to is that it is not only the copyright year. It is also 
> missing the sentence "Portion copyright The Apache Software Foundation"
> 
> It seems that the text in the About dialog is customized on each builder's 
> system and therefore it is not standardized?
> 
> 
> Regards,
> 
> Pedro


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Pedro Lino 
> But even if I wanted, I can not change the copyright year...
> That's what I am wondering about. ;-)
> 

Ok. I (wrongly) assumed it was all editable :)


> BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
> 
> 

Yes, Jim's build is showing 2017.


Regards,

Pedro

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Am 20.10.18 um 13:04 schrieb Pedro Lino:
> Hi Matthias
>
>> On October 20, 2018 at 11:26 AM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>>
>>
>>
>> > > I can confirm that it is running as expected under Ubuntu 16.04 
>> x64 (Thanks Jim!)
>>> > 
>> > > The About box does have a quite different text compared from 
>> what is produced by the buildbots.
>>> > 
>> > > https://i.imgur.com/3r5Btju.png
>>> > Yes, of course!
>> We modified the text because many people used these builds for
>> "productive" work. ;-)
>>
>> But the question remains why the copyright year is different?
>>
>
> I am aware of the Buildbot differences...
>
> What I was referring to is that it is not only the copyright year. It is also 
> missing the sentence "Portion copyright The Apache Software Foundation"
>
> It seems that the text in the About dialog is customized on each builder's 
> system and therefore it is not standardized?

Yes, the text can be customized with configure switches. You can see it
also in my Windows builds.
This way we can have different text for different builds.

But even if I wanted, I can not change the copyright year...
That's what I am wondering about. ;-)

BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?

Regards,

   Matthias

>
>
> Regards,
>
> Pedro
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Pedro Lino 
Hi Matthias

> On October 20, 2018 at 11:26 AM Matthias Seidel  mailto:matthias.sei...@hamburg.de > wrote:
> 
> 
> 
> > > I can confirm that it is running as expected under Ubuntu 16.04 
> x64 (Thanks Jim!)
> > 
> > > 
> > > The About box does have a quite different text compared from what 
> is produced by the buildbots.
> > 
> > > 
> > > https://i.imgur.com/3r5Btju.png
> > 
> > > Yes, of course!
> 
> We modified the text because many people used these builds for
> "productive" work. ;-)
> 
> But the question remains why the copyright year is different?
> 


I am aware of the Buildbot differences...

What I was referring to is that it is not only the copyright year. It is also 
missing the sentence "Portion copyright The Apache Software Foundation"

It seems that the text in the About dialog is customized on each builder's 
system and therefore it is not standardized?


Regards,

Pedro

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Hi Jim,

Am 20.10.18 um 00:24 schrieb Jim Jagielski:
> All done!

As usual Windows builds are to be found at:

https://home.apache.org/~mseidel/AOO-builds/AOO-416-Test/

Regards,

   Matthias

>
>> On Oct 19, 2018, at 4:59 PM, Pedro Lino  wrote:
>>
>> Hi Jim
>>
>> Can you please upload pt (European Portuguese)?
>>
>> Thanks
>> Pedro
>>
>>> On October 19, 2018 at 9:14 PM Jim Jagielski  wrote:
>>>
>>>
>>> Builds for macOS and Linux 64bit (CentOS5) can be found at:
>>>
>>>http://home.apache.org/~jim/AOO-builds/
>>>
>>> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
>>> your lang of choice, let me know!
>>>
 On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
 wrote:

 Hi Jim,

 Am 19.10.18 um 18:17 schrieb Jim Jagielski:
> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>
> Which langs would people like? I'll upload to my Apache people space.
 It would be great if you could provide German for Linux.

 I'd like to test it on a daily base...

 Matthias

> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Hi Pedro,

Am 20.10.18 um 12:21 schrieb Pedro Lino:
> Hi Matthias, all
>
>
>> On October 20, 2018 at 10:46 AM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>>
>> But has anyone else "Copyright © 2017" in the About Box?
>> Builds from our buildbots and my own Windows builds have "Copyright ©
>> 2018" and I am wondering about the difference.
>>
>
> I can confirm that it is running as expected under Ubuntu 16.04 x64 (Thanks 
> Jim!)
>
> The About box does have a quite different text compared from what is produced 
> by the buildbots.
>
> https://i.imgur.com/3r5Btju.png

Yes, of course!

We modified the text because many people used these builds for
"productive" work. ;-)

But the question remains why the copyright year is different?

Regards,

   Matthias

>
> Regards,
>
> Pedro
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Pedro Lino 
Hi Matthias, all


> On October 20, 2018 at 10:46 AM Matthias Seidel  mailto:matthias.sei...@hamburg.de > wrote:
> 
> But has anyone else "Copyright © 2017" in the About Box?
> Builds from our buildbots and my own Windows builds have "Copyright ©
> 2018" and I am wondering about the difference.
> 


I can confirm that it is running as expected under Ubuntu 16.04 x64 (Thanks 
Jim!)

The About box does have a quite different text compared from what is produced 
by the buildbots.

https://i.imgur.com/3r5Btju.png


Regards,

Pedro

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Matthias Seidel 
Hi Jim,

Am 19.10.18 um 22:14 schrieb Jim Jagielski:
> Builds for macOS and Linux 64bit (CentOS5) can be found at:
>
> http://home.apache.org/~jim/AOO-builds/

Thanks, works good so far on Ubuntu 16.04.

But has anyone else "Copyright © 2017" in the About Box?
Builds from our buildbots and my own Windows builds have "Copyright ©
2018" and I am wondering about the difference.

Regards,

   Matthias

>
> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
> your lang of choice, let me know!
>
>> On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> Am 19.10.18 um 18:17 schrieb Jim Jagielski:
>>> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>>>
>>> Which langs would people like? I'll upload to my Apache people space.
>> It would be great if you could provide German for Linux.
>>
>> I'd like to test it on a daily base...
>>
>> Matthias
>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Test builds of AOO 4.1.6 HEAD

2018-10-20 Thread Алексей Евгеньевич Харламенков 
Hello Jim!

Please download Russian (ru-RU).

-- 
Yours faithfully,
Aleksey Evgenievich Harlamenkov.



19.10.2018, 19:17, "Jim Jagielski" :
> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>
> Which langs would people like? I'll upload to my Apache people space.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-19 Thread Peter Kovacs 
thanks Jim!

On 10/20/18 12:24 AM, Jim Jagielski wrote:
> All done!
>
>> On Oct 19, 2018, at 4:59 PM, Pedro Lino  wrote:
>>
>> Hi Jim
>>
>> Can you please upload pt (European Portuguese)?
>>
>> Thanks
>> Pedro
>>
>>> On October 19, 2018 at 9:14 PM Jim Jagielski  wrote:
>>>
>>>
>>> Builds for macOS and Linux 64bit (CentOS5) can be found at:
>>>
>>>http://home.apache.org/~jim/AOO-builds/
>>>
>>> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
>>> your lang of choice, let me know!
>>>
 On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
 wrote:

 Hi Jim,

 Am 19.10.18 um 18:17 schrieb Jim Jagielski:
> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>
> Which langs would people like? I'll upload to my Apache people space.
 It would be great if you could provide German for Linux.

 I'd like to test it on a daily base...

 Matthias

> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-19 Thread Jim Jagielski 
All done!

> On Oct 19, 2018, at 4:59 PM, Pedro Lino  wrote:
> 
> Hi Jim
> 
> Can you please upload pt (European Portuguese)?
> 
> Thanks
> Pedro
> 
>> On October 19, 2018 at 9:14 PM Jim Jagielski  wrote:
>> 
>> 
>> Builds for macOS and Linux 64bit (CentOS5) can be found at:
>> 
>>http://home.apache.org/~jim/AOO-builds/
>> 
>> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
>> your lang of choice, let me know!
>> 
>>> On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> Am 19.10.18 um 18:17 schrieb Jim Jagielski:
 My macOS builds are almost done; next up CentOS5 (Linux) ones.
 
 Which langs would people like? I'll upload to my Apache people space.
>>> 
>>> It would be great if you could provide German for Linux.
>>> 
>>> I'd like to test it on a daily base...
>>> 
>>> Matthias
>>> 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-19 Thread Pedro Lino 
Hi Jim

Can you please upload pt (European Portuguese)?

Thanks
Pedro

> On October 19, 2018 at 9:14 PM Jim Jagielski  wrote:
> 
> 
> Builds for macOS and Linux 64bit (CentOS5) can be found at:
> 
> http://home.apache.org/~jim/AOO-builds/
> 
> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
> your lang of choice, let me know!
> 
> > On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
> > wrote:
> > 
> > Hi Jim,
> > 
> > Am 19.10.18 um 18:17 schrieb Jim Jagielski:
> >> My macOS builds are almost done; next up CentOS5 (Linux) ones.
> >> 
> >> Which langs would people like? I'll upload to my Apache people space.
> > 
> > It would be great if you could provide German for Linux.
> > 
> > I'd like to test it on a daily base...
> > 
> > Matthias
> > 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> 
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-19 Thread Jim Jagielski 
Builds for macOS and Linux 64bit (CentOS5) can be found at:

http://home.apache.org/~jim/AOO-builds/

32bit CentOS will either be over the weekend or Monday. If I didn't upload your 
lang of choice, let me know!

> On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 19.10.18 um 18:17 schrieb Jim Jagielski:
>> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>> 
>> Which langs would people like? I'll upload to my Apache people space.
> 
> It would be great if you could provide German for Linux.
> 
> I'd like to test it on a daily base...
> 
> Matthias
> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test builds of AOO 4.1.6 HEAD

2018-10-19 Thread Matthias Seidel 
Hi Jim,

Am 19.10.18 um 18:17 schrieb Jim Jagielski:
> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>
> Which langs would people like? I'll upload to my Apache people space.

It would be great if you could provide German for Linux.

I'd like to test it on a daily base...

Matthias

>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature