Discussion:
macOS test builds for AOO 4.1.6 underway
Jim Jagielski
2018-10-19 11:33:03 UTC
Permalink
Subj sez it all...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2018-10-19 16:17:17 UTC
Permalink
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-19 16:36:32 UTC
Permalink
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
Jim Jagielski
2018-10-19 20:14:08 UTC
Permalink
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Pedro Lino
2018-10-19 20:59:14 UTC
Permalink
Hi Jim

Can you please upload pt (European Portuguese)?

Thanks
Pedro
Post by Jim Jagielski
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2018-10-19 22:24:45 UTC
Permalink
All done!
Post by Matthias Seidel
Hi Jim
Can you please upload pt (European Portuguese)?
Thanks
Pedro
Post by Jim Jagielski
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Peter Kovacs
2018-10-20 01:37:12 UTC
Permalink
thanks Jim!
Post by Jim Jagielski
All done!
Post by Matthias Seidel
Hi Jim
Can you please upload pt (European Portuguese)?
Thanks
Pedro
Post by Jim Jagielski
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-20 10:58:09 UTC
Permalink
Hi Jim,
Post by 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
Post by Jim Jagielski
Post by Matthias Seidel
Hi Jim
Can you please upload pt (European Portuguese)?
Thanks
Pedro
Post by Jim Jagielski
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Matthias Seidel
2018-10-20 09:46:43 UTC
Permalink
Hi Jim,
Post by Jim Jagielski
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
Post by Jim Jagielski
32bit CentOS will either be over the weekend or Monday. If I didn't upload your lang of choice, let me know!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
Pedro Lino
2018-10-20 10:21:50 UTC
Permalink
Hi Matthias, all
Post by Matthias Seidel
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.

Loading Image...


Regards,

Pedro
Matthias Seidel
2018-10-20 10:26:18 UTC
Permalink
Hi Pedro,
Post by Pedro Lino
Hi Matthias, all
Post by Matthias Seidel
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
Post by Pedro Lino
Regards,
Pedro
Pedro Lino
2018-10-20 11:04:18 UTC
Permalink
Hi Matthias
Post by Matthias Seidel
Post by Pedro Lino
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
Matthias Seidel
2018-10-20 11:09:27 UTC
Permalink
Post by Pedro Lino
Hi Matthias
Post by Matthias Seidel
Post by Pedro Lino
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
Post by Pedro Lino
Regards,
Pedro
Pedro Lino
2018-10-20 11:14:48 UTC
Permalink
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
Yes, Jim's build is showing 2017.


Regards,

Pedro
Jim Jagielski
2018-10-20 13:35:56 UTC
Permalink
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
Pedro Lino
2018-10-20 13:45:12 UTC
Permalink
That is probably because your OS is named Darwin (more evolved?) :)
Post by Matthias Seidel
?space?-- 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 :)
?space?-- BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro
Jim Jagielski
2018-10-20 14:54:19 UTC
Permalink
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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
Jim Jagielski
2018-10-20 15:16:50 UTC
Permalink
Found it.

Fixed in r1844422 and r1844423
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-20 15:20:49 UTC
Permalink
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
Jim Jagielski
2018-10-20 18:02:58 UTC
Permalink
That's what it looks like, yeah.
Post by Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
Marcus
2018-10-21 17:59:50 UTC
Permalink
Post by 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
Post by Jim Jagielski
Post by Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
Post by Pedro Lino
Post by Matthias Seidel
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 :)
Post by Matthias Seidel
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-21 18:06:16 UTC
Permalink
Post by Marcus
Post by 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
Post by Marcus
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
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, 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
---------------------------------------------------------------------
Marcus
2018-10-21 18:08:59 UTC
Permalink
Post by Matthias Seidel
Post by Marcus
Post by 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
Post by Matthias Seidel
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
Post by Marcus
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
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-21 18:19:53 UTC
Permalink
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by 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&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by 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.
Post by Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, 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
---------------------------------------------------------------------
Peter kovacs
2018-10-21 20:43:29 UTC
Permalink
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
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea how
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by Jim Jagielski
Are we sure that that part of the splash screen isn't hardcoded
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
(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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
   But even if I wanted, I can not change the copyright
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
   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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-21 21:27:53 UTC
Permalink
Hi Peter,
Post by 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
Post by Peter kovacs
All the best
Peter
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea how
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by Jim Jagielski
Are we sure that that part of the splash screen isn't hardcoded
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
(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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
   But even if I wanted, I can not change the copyright
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
   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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
Marcus
2018-10-21 21:55:03 UTC
Permalink
Post by Matthias Seidel
Post by 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
Post by Matthias Seidel
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
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea how
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by Jim Jagielski
Are we sure that that part of the splash screen isn't hardcoded
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
(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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
   But even if I wanted, I can not change the copyright
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
   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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-21 21:58:25 UTC
Permalink
Post by Marcus
Post by Matthias Seidel
Post by 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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea how
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by Jim Jagielski
Are we sure that that part of the splash screen isn't hardcoded
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
(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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
    But even if I wanted, I can not change the copyright
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
    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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
Peter kovacs
2018-10-22 00:10:21 UTC
Permalink
Stupid question where is the script?
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
    But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
    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
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2018-10-22 11:58:12 UTC
Permalink
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts
Post by Peter kovacs
Stupid question where is the script?
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
Post by Matthias Seidel
But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
That's what I am wondering about. ;-)
Ok. I (wrongly) assumed it was all editable :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in
Jim's
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-22 16:28:42 UTC
Permalink
Hi Peter,
Post by 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
Post by Peter kovacs
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
    But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
    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
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
Jim Jagielski
2018-10-22 16:34:07 UTC
Permalink
All done. hash-sign-512 removed as a consequence.
Post by Matthias Seidel
Hi Peter,
Post by 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
Post by Peter kovacs
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
Post by Matthias Seidel
But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
That's what I am wondering about. ;-)
Ok. I (wrongly) assumed it was all editable :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in
Jim's
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-22 16:35:35 UTC
Permalink
Post by Jim Jagielski
All done. hash-sign-512 removed as a consequence.
Thanks!
Post by Jim Jagielski
Post by Matthias Seidel
Hi Peter,
Post by 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
Post by Peter kovacs
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
Post by Matthias Seidel
But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
That's what I am wondering about. ;-)
Ok. I (wrongly) assumed it was all editable :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in
Jim's
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Marcus
2018-10-22 22:03:33 UTC
Permalink
Post by Jim Jagielski
All done. hash-sign-512 removed as a consequence.
wow, that was fast. :-)

Thanks

Marcus
Post by Jim Jagielski
Post by Matthias Seidel
Hi Peter,
Post by 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
Post by Peter kovacs
Post by Peter kovacs
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
When the year issue has been fixed, I think we can call it an RC1.
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
check tomorrow evening. Sorry had no energy for stuff on the
weekend.
Post by Marcus
Post by Matthias Seidel
How do we want to sign the builds?
"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
SHOULD
Post by Marcus
Post by Matthias Seidel
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
Post by Marcus
Marcus
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
Post by Marcus
Post by Matthias Seidel
[1] https://www.apache.org/dev/release-distribution#sigs-and-sums
Post by Peter kovacs
Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;revision=1780015
But there are several parts (ODK, Linux packaging) which should
get
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
some
attention.
In 4.1.x they were not updated in all these years...
So +1 for a script from me!
Matthias
Post by Marcus
Marcus
Post by Matthias Seidel
But my test build are always with --with-vendor in configure, so
I
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
didn't realize that it was missing from branch 4.1.6.
Matthias
Post by Marcus
We now have a script to update version numbers; somewhere in
the
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
devtools I think.
What about to create a new script to list all the code lines
with a
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
the year number. Then someone can have a look and compare it
with
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
the
Post by Marcus
Post by Matthias Seidel
Post by Marcus
current calendar year and if needed create a patch to update
all
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
affected year numbers at ones.
Maybe a good first step because no year number is forgotten.
The
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
next
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea
how
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically,
otherwise not?
Post by Jim Jagielski
On Oct 20, 2018, at 10:54 AM, Jim Jagielski
Are we sure that that part of the splash screen isn't
hardcoded
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
(ie: the Copyright part)?
I know that I use '--with-vendor="Apache OpenOffice
Community
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Build" \' for macOS and I am guessing the buildbots also
use
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
that
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more
evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
Post by Matthias Seidel
But even if I wanted, I can not change the
copyright
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
That's what I am wondering about. ;-)
Ok. I (wrongly) assumed it was all editable :)
Post by Matthias Seidel
BTW: Can you confirm 2017 as copyright year in
Jim's
Post by Marcus
Post by Matthias Seidel
Post by Peter kovacs
Post by Marcus
Linux
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Matthias Seidel
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org

Marcus
2018-10-21 21:55:11 UTC
Permalink
Post by 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
Post by Peter kovacs
Post by Marcus
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
That's what it looks like, yeah.
copyright years are always forgotten to update. Every year the
same.
Post by Marcus
Post by Matthias Seidel
Post by Marcus
;-)
In fact I *did* update it for trunk in January... ;-)
hm, OK. Are you sure that you have updated it everywhere it is
needed?
Post by Marcus
Even here the script could be helpful.
https://svn.apache.org/viewvc?view=revision&amp;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
Post by Marcus
Marcus
Post by Matthias Seidel
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
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
one would be to automate this update. But I've not yet an idea how
to
Post by Marcus
Post by Matthias Seidel
Post by Marcus
do this.
What do you think?
Marcus
Post by Jim Jagielski
On Oct 20, 2018, at 11:20 AM, Matthias Seidel
Post by Jim Jagielski
Found it.
Great!
Post by Jim Jagielski
Fixed in r1844422 and r1844423
That means, when using --vendor it is updated automatically, otherwise not?
Post by Jim Jagielski
Post by Jim Jagielski
Are we sure that that part of the splash screen isn't hardcoded
in
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
(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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
configure option, so maybe that's a clue.
On Oct 20, 2018, at 9:45 AM, Pedro Lino
That is probably because your OS is named Darwin (more evolved?) :)
<Build1844227_Linux_x86_64.png>
On October 20, 2018 at 2:35 PM Jim Jagielski
<Screen Shot 2018-10-20 at 9.34.44 AM.png>
On Oct 20, 2018, at 7:14 AM, Pedro Lino <
   But even if I wanted, I can not change the copyright
year...
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
   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
Post by Marcus
Post by Matthias Seidel
Post by Marcus
Post by Jim Jagielski
Post by Jim Jagielski
Post by Jim Jagielski
builds?
Yes, Jim's build is showing 2017.
Regards,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2018-10-20 13:39:59 UTC
Permalink
The only customizing on my builds is:

--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`"
Post by Pedro Lino
Hi Matthias
Post by Matthias Seidel
Post by Pedro Lino
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Kay Schenk
2018-10-22 21:55:11 UTC
Permalink
Installed the Linux 64-bit, en-US rpm version (yes, I've FINALLY
switched over). So far, so good. Thanks.
Post by Jim Jagielski
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!
Post by Matthias Seidel
Hi Jim,
Post by 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
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Алексей Евгеньевич Харламенков
2018-10-20 06:48:40 UTC
Permalink
Hello Jim!

Please download Russian (ru-RU).

-- 
Yours faithfully,
Aleksey Evgenievich Harlamenkov.
Post by 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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Andrea Pescetti
2018-10-20 20:18:52 UTC
Permalink
Post by Jim Jagielski
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2018-10-20 20:37:45 UTC
Permalink
Post by Andrea Pescetti
Post by Jim Jagielski
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
Post by Andrea Pescetti
Regards,
  Andrea.
---------------------------------------------------------------------
Andrea Pescetti
2018-10-20 22:08:32 UTC
Permalink
Post by Matthias Seidel
Post by 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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2018-10-21 12:07:53 UTC
Permalink
All uploaded!
Post by Jim Jagielski
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Loading...