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 > <matthias.sei...@hamburg.de>: >> 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 >>>>> <matthias.sei...@hamburg.de>: >>>>>> 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 >>>>>>>>>>> <matthias.sei...@hamburg.de> 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 >> <j...@jagunet.com> >>>>>>>>>>>>> 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 >>>>>> <pedro.l...@mailbox.org> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>> <j...@jagunet.com> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hmmm... The macOS builds are showing 2018: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <Screen Shot 2018-10-20 at 9.34.44 AM.png> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino < >>>>>>>>>>>>>>>> pedro.l...@mailbox.org <mailto:pedro.l...@mailbox.org>> >>>>>> wrote: >>>>>>>>>>>>>>>>> But even if I wanted, I can not change the >> copyright >>>>>> year... >>>>>>>>>>>>>>>>> That's what I am wondering about. ;-) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Ok. I (wrongly) assumed it was all editable :) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> BTW: Can you confirm 2017 as copyright year in >> Jim's >>>>>> Linux >>>>>>>>>>>>>>>>> builds? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Yes, Jim's build is showing 2017. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Pedro >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
