Re: AOO 4.1.6-RC1 m1 r1844555

2018-10-22 Thread Peter Kovacs 
I am a bit confused where we all are now. I think all Issues are
resolved and currently we are not aware on regressions right?

If r1844555 has not been build yet, then please start. :) I would like
to do some signing.

Thank you all for your efforts!

On 22.10.18 15:12, Jim Jagielski wrote:
> I am ready to start building macOS and Linux 64&32bit builds of HEAD of 
> AOO416, which is m1 at r1844555
>
> Just say the word :)
> -
> 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 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=revision&revision=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: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Matthias Seidel 
Hi Pedro,

Am 22.10.18 um 18:47 schrieb Pedro Lino:
> Hi all
>
>
>> On October 22, 2018 at 5:38 PM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>>
>>
>> Am 22.10.18 um 18:35 schrieb Jim Jagielski:
>>
>> > > The thing is, IMO, that these ARE community builds, and, as 
>> such, should be noted as such on the About Page... But I'm fine w/ removing 
>> that depending on what people think.
>>> > The community is not a vendor. If you leave it out everything is 
>>> OK:
>> "This product was created by the OpenOffice community."
>>
>
> Shouldn't it be "This product was created by the OpenOffice community, based 
> on Apache OpenOffice." for all OSes?

That phrase is hard coded in:

https://svn.apache.org/repos/asf/openoffice/branches/AOO416/main/cui/source/dialogs/about.src

I wouldn't want to change it for 4.1.x (localization would be needed).
Maybe for 4.2.x?

Regards,

   Matthias

>
> I agree with Matthias that "This product was created by Apache OpenOffice 
> Community Build" does not make sense in English
>
>
> Regards,
>
> Pedro
>
>
>> >
>> >> On Oct 22, 2018, at 12:32 PM, Matthias Seidel 
>> mailto:matthias.sei...@hamburg.de > wrote:
>> >>
>> >> Am 22.10.18 um 18:13 schrieb Jim Jagielski:
>> >>> It was used for macOS. I was just making it consistent among all my 
>> builds.
>> >> Wouldn't it be better to make the macOS build consistent with the 
>> other
>> >> builds... ;-)
>> >>
>>  On Oct 22, 2018, at 12:08 PM, Matthias Seidel 
>> mailto:matthias.sei...@hamburg.de > wrote:
>> 
>>  Hi Jim,
>> 
>>  --with-vendor="Apache OpenOffice Community Build" \
>> 
>>  results in weird wording:
>> 
>>  "This product was created by Apache OpenOffice Community Build, 
>> based on
>>  Apache OpenOffice"
>> 
>>  And we didn't use --with-vendor for a release build before.
>> 
>>  Regards,
>> 
>>  Matthias
>> 
>>  Am 22.10.18 um 14:31 schrieb j...@apache.org mailto:j...@apache.org 
>> :
>> > Author: jim
>> > Date: Mon Oct 22 12:31:52 2018
>> > New Revision: 1844550
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1844550&view=rev 
>> http://svn.apache.org/viewvc?rev=1844550&view=rev
>> > Log:
>> > Update vendor for builds
>> >
>> > Modified:
>> > 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>> > 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>> >
>> > Modified: 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>> > URL: 
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>>  
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>> > 
>> ==
>> > --- 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>  (original)
>> > +++ 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>  Mon Oct 22 12:31:52 2018
>> > @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>> > fi
>> > ./configure \
>> > --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>> > + --with-vendor="Apache OpenOffice Community Build" \
>> > --enable-verbose \
>> > --with-system-stdlibs \
>> > --enable-crashdump=yes \
>> >
>> > Modified: 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>> > URL: 
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>>  
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>> > 
>> ==
>> > --- 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>  (original)
>> > +++ 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>  Mon Oct 22 12:31:52 2018
>> > @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>> > fi
>> > ./configure \
>> > --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>> > + --with-vendor="Apache OpenOffice Community Build" \
>> > --enable-verbose \
>> > --with-system-stdlibs \
>> > --enable-crashdump=yes \
>> >
>> >
>> >>> -

Re: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Pedro Lino 
Hi all


> On October 22, 2018 at 5:38 PM Matthias Seidel  mailto:matthias.sei...@hamburg.de > wrote:
> 
> 
> Am 22.10.18 um 18:35 schrieb Jim Jagielski:
> 
> > > The thing is, IMO, that these ARE community builds, and, as such, 
> should be noted as such on the About Page... But I'm fine w/ removing that 
> depending on what people think.
> > 
> > > The community is not a vendor. If you leave it out everything is 
> > OK:
> 
> "This product was created by the OpenOffice community."
> 


Shouldn't it be "This product was created by the OpenOffice community, based on 
Apache OpenOffice." for all OSes?

I agree with Matthias that "This product was created by Apache OpenOffice 
Community Build" does not make sense in English


Regards,

Pedro


> 
> >
> >> On Oct 22, 2018, at 12:32 PM, Matthias Seidel 
> mailto:matthias.sei...@hamburg.de > wrote:
> >>
> >> Am 22.10.18 um 18:13 schrieb Jim Jagielski:
> >>> It was used for macOS. I was just making it consistent among all my 
> builds.
> >> Wouldn't it be better to make the macOS build consistent with the other
> >> builds... ;-)
> >>
>  On Oct 22, 2018, at 12:08 PM, Matthias Seidel 
> mailto:matthias.sei...@hamburg.de > wrote:
> 
>  Hi Jim,
> 
>  --with-vendor="Apache OpenOffice Community Build" \
> 
>  results in weird wording:
> 
>  "This product was created by Apache OpenOffice Community Build, 
> based on
>  Apache OpenOffice"
> 
>  And we didn't use --with-vendor for a release build before.
> 
>  Regards,
> 
>  Matthias
> 
>  Am 22.10.18 um 14:31 schrieb j...@apache.org mailto:j...@apache.org :
> > Author: jim
> > Date: Mon Oct 22 12:31:52 2018
> > New Revision: 1844550
> >
> > URL: http://svn.apache.org/viewvc?rev=1844550&view=rev 
> http://svn.apache.org/viewvc?rev=1844550&view=rev
> > Log:
> > Update vendor for builds
> >
> > Modified:
> > 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
> > 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
> >
> > Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
> > URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>  
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> > 
> ==
> > --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh 
> (original)
> > +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh 
> Mon Oct 22 12:31:52 2018
> > @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
> > fi
> > ./configure \
> > --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> > + --with-vendor="Apache OpenOffice Community Build" \
> > --enable-verbose \
> > --with-system-stdlibs \
> > --enable-crashdump=yes \
> >
> > Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
> > URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>  
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> > 
> ==
> > --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  (original)
> > +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  Mon Oct 22 12:31:52 2018
> > @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
> > fi
> > ./configure \
> > --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> > + --with-vendor="Apache OpenOffice Community Build" \
> > --enable-verbose \
> > --with-system-stdlibs \
> > --enable-crashdump=yes \
> >
> >
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> mailto:dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> mailto:dev-h...@openoffice.apache.org
> >>>
> >
> 
> ---
To unsubscribe,

Re: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Matthias Seidel 
Am 22.10.18 um 18:35 schrieb Jim Jagielski:
> The thing is, IMO, that these ARE community builds, and, as such, should be 
> noted as such on the About Page... But I'm fine w/ removing that depending on 
> what people think.

The community is not a vendor. If you leave it out everything is OK:

"This product was created by the OpenOffice community."

Regards,

Matthias

>
>> On Oct 22, 2018, at 12:32 PM, Matthias Seidel  
>> wrote:
>>
>> Am 22.10.18 um 18:13 schrieb Jim Jagielski:
>>> It was used for macOS. I was just making it consistent among all my builds.
>> Wouldn't it be better to make the macOS build consistent with the other
>> builds... ;-)
>>
 On Oct 22, 2018, at 12:08 PM, Matthias Seidel  
 wrote:

 Hi Jim,

 --with-vendor="Apache OpenOffice Community Build" \

 results in weird wording:

 "This product was created by Apache OpenOffice Community Build, based on
 Apache OpenOffice"

 And we didn't use --with-vendor for a release build before.

 Regards,

   Matthias

 Am 22.10.18 um 14:31 schrieb j...@apache.org:
> Author: jim
> Date: Mon Oct 22 12:31:52 2018
> New Revision: 1844550
>
> URL: http://svn.apache.org/viewvc?rev=1844550&view=rev
> Log:
> Update vendor for builds
>
> Modified:
>   
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>   
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>
> Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
> URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> ==
> --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>  (original)
> +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>  Mon Oct 22 12:31:52 2018
> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
> fi
> ./configure   \
>   --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> + --with-vendor="Apache OpenOffice Community Build" \
>   --enable-verbose \
>   --with-system-stdlibs \
>   --enable-crashdump=yes \
>
> Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
> URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> ==
> --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  (original)
> +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  Mon Oct 22 12:31:52 2018
> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
> fi
> ./configure   \
>   --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> + --with-vendor="Apache OpenOffice Community Build" \
>   --enable-verbose \
>   --with-system-stdlibs \
>   --enable-crashdump=yes \
>
>
>>> -
>>> 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: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Jim Jagielski 
The thing is, IMO, that these ARE community builds, and, as such, should be 
noted as such on the About Page... But I'm fine w/ removing that depending on 
what people think.

> On Oct 22, 2018, at 12:32 PM, Matthias Seidel  
> wrote:
> 
> Am 22.10.18 um 18:13 schrieb Jim Jagielski:
>> It was used for macOS. I was just making it consistent among all my builds.
> 
> Wouldn't it be better to make the macOS build consistent with the other
> builds... ;-)
> 
>>> On Oct 22, 2018, at 12:08 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> --with-vendor="Apache OpenOffice Community Build" \
>>> 
>>> results in weird wording:
>>> 
>>> "This product was created by Apache OpenOffice Community Build, based on
>>> Apache OpenOffice"
>>> 
>>> And we didn't use --with-vendor for a release build before.
>>> 
>>> Regards,
>>> 
>>>   Matthias
>>> 
>>> Am 22.10.18 um 14:31 schrieb j...@apache.org:
 Author: jim
 Date: Mon Oct 22 12:31:52 2018
 New Revision: 1844550
 
 URL: http://svn.apache.org/viewvc?rev=1844550&view=rev
 Log:
 Update vendor for builds
 
 Modified:
   
 openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
   
 openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
 
 Modified: 
 openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
 URL: 
 http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
 ==
 --- 
 openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
  (original)
 +++ 
 openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
  Mon Oct 22 12:31:52 2018
 @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
 fi
 ./configure   \
--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
 +  --with-vendor="Apache OpenOffice Community Build" \
--enable-verbose \
--with-system-stdlibs \
--enable-crashdump=yes \
 
 Modified: 
 openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
 URL: 
 http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
 ==
 --- 
 openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
  (original)
 +++ 
 openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
  Mon Oct 22 12:31:52 2018
 @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
 fi
 ./configure   \
--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
 +  --with-vendor="Apache OpenOffice Community Build" \
--enable-verbose \
--with-system-stdlibs \
--enable-crashdump=yes \
 
 
>> 
>> -
>> 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=revision&revision=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=revision&revision=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: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Matthias Seidel 
Am 22.10.18 um 18:13 schrieb Jim Jagielski:
> It was used for macOS. I was just making it consistent among all my builds.

Wouldn't it be better to make the macOS build consistent with the other
builds... ;-)

>> On Oct 22, 2018, at 12:08 PM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> --with-vendor="Apache OpenOffice Community Build" \
>>
>> results in weird wording:
>>
>> "This product was created by Apache OpenOffice Community Build, based on
>> Apache OpenOffice"
>>
>> And we didn't use --with-vendor for a release build before.
>>
>> Regards,
>>
>>Matthias
>>
>> Am 22.10.18 um 14:31 schrieb j...@apache.org:
>>> Author: jim
>>> Date: Mon Oct 22 12:31:52 2018
>>> New Revision: 1844550
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1844550&view=rev
>>> Log:
>>> Update vendor for builds
>>>
>>> Modified:
>>>
>>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>>
>>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>>
>>> Modified: 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>> URL: 
>>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>>> ==
>>> --- 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>>  (original)
>>> +++ 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>>  Mon Oct 22 12:31:52 2018
>>> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>>> fi
>>> ./configure   \
>>> --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>>> +   --with-vendor="Apache OpenOffice Community Build" \
>>> --enable-verbose \
>>> --with-system-stdlibs \
>>> --enable-crashdump=yes \
>>>
>>> Modified: 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>> URL: 
>>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>>> ==
>>> --- 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>>  (original)
>>> +++ 
>>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>>  Mon Oct 22 12:31:52 2018
>>> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>>> fi
>>> ./configure   \
>>> --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>>> +   --with-vendor="Apache OpenOffice Community Build" \
>>> --enable-verbose \
>>> --with-system-stdlibs \
>>> --enable-crashdump=yes \
>>>
>>>
>
> -
> 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-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=revision&revision=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 wonderi

Re: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Jim Jagielski 
It was used for macOS. I was just making it consistent among all my builds.

> On Oct 22, 2018, at 12:08 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> --with-vendor="Apache OpenOffice Community Build" \
> 
> results in weird wording:
> 
> "This product was created by Apache OpenOffice Community Build, based on
> Apache OpenOffice"
> 
> And we didn't use --with-vendor for a release build before.
> 
> Regards,
> 
>Matthias
> 
> Am 22.10.18 um 14:31 schrieb j...@apache.org:
>> Author: jim
>> Date: Mon Oct 22 12:31:52 2018
>> New Revision: 1844550
>> 
>> URL: http://svn.apache.org/viewvc?rev=1844550&view=rev
>> Log:
>> Update vendor for builds
>> 
>> Modified:
>>
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>> 
>> Modified: 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>> URL: 
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>> ==
>> --- 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>  (original)
>> +++ 
>> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
>>  Mon Oct 22 12:31:52 2018
>> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>> fi
>> ./configure   \
>>  --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>> +--with-vendor="Apache OpenOffice Community Build" \
>>  --enable-verbose \
>>  --with-system-stdlibs \
>>  --enable-crashdump=yes \
>> 
>> Modified: 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>> URL: 
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
>> ==
>> --- 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>  (original)
>> +++ 
>> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>>  Mon Oct 22 12:31:52 2018
>> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>> fi
>> ./configure   \
>>  --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
>> +--with-vendor="Apache OpenOffice Community Build" \
>>  --enable-verbose \
>>  --with-system-stdlibs \
>>  --enable-crashdump=yes \
>> 
>> 
> 


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

Re: svn commit: r1844550 - in /openoffice/devtools/build-scripts/4.1.6: unxlngi6/build_aoo32bit_on_centos5.sh unxlngix6/build_aoo64bit_on_centos5.sh

2018-10-22 Thread Matthias Seidel 
Hi Jim,

--with-vendor="Apache OpenOffice Community Build" \

results in weird wording:

"This product was created by Apache OpenOffice Community Build, based on
Apache OpenOffice"

And we didn't use --with-vendor for a release build before.

Regards,

   Matthias

Am 22.10.18 um 14:31 schrieb j...@apache.org:
> Author: jim
> Date: Mon Oct 22 12:31:52 2018
> New Revision: 1844550
>
> URL: http://svn.apache.org/viewvc?rev=1844550&view=rev
> Log:
> Update vendor for builds
>
> Modified:
> 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
> 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>
> Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh
> URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> ==
> --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh 
> (original)
> +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngi6/build_aoo32bit_on_centos5.sh 
> Mon Oct 22 12:31:52 2018
> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>  fi
>  ./configure   \
>   --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> + --with-vendor="Apache OpenOffice Community Build" \
>   --enable-verbose \
>   --with-system-stdlibs \
>   --enable-crashdump=yes \
>
> Modified: 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
> URL: 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh?rev=1844550&r1=1844549&r2=1844550&view=diff
> ==
> --- 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  (original)
> +++ 
> openoffice/devtools/build-scripts/4.1.6/unxlngix6/build_aoo64bit_on_centos5.sh
>  Mon Oct 22 12:31:52 2018
> @@ -15,6 +15,7 @@ if [ ! -e configure -o configure.in -nt
>  fi
>  ./configure   \
>   --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
> + --with-vendor="Apache OpenOffice Community Build" \
>   --enable-verbose \
>   --with-system-stdlibs \
>   --enable-crashdump=yes \
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

AOO 4.1.6-RC1 m1 r1844555

2018-10-22 Thread Jim Jagielski 
I am ready to start building macOS and Linux 64&32bit builds of HEAD of AOO416, 
which is m1 at r1844555

Just say the word :)
-
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 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=revision&revision=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