Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Keith N. McKenna]

Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Thursday, August 18, 2016 14:46
>> To: qa@openoffice.apache.org; d...@openoffice.apache.org
>> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
> [ ... ]
>> [knmc]
>> As we move forward to a general distribution here  is an odt revision of
>> the readme that can be used to generate an html, pdf, or text versions.
>> All versions are attached but may not come through to the list. They can
>> all be accessed from the following link.
>> <https://1drv.ms/f/s!AMMYmStvrJNJgQQ>
>> All feedback is both welcomed and encouraged.
> [orcmid] 
>
> The .odt and the .txt file come through as attachments.
>
> Do you have specific recommendations about what should be done with these?  
[knmc]
My initial idea was to create a template that could be used to
standardize this type of documentation rather than having individuals
using different tools and methodologies on the different operating
systems that we support. It just took me longer than I had expected.
At this point it is far to late to attempt to do anything for this
particular patch release. So all I am looking for is feed back on
structure and if it is even a worthwhile endeavor to pursue.
[knmc]
> I notice that there are problems with the .txt file layout not having hard 
> line breaks.
[knmc]
That is one reason I have never been a big fan of using plain text for
documentation. I would rather see PDF or HTML
>   The name changes and dates in 0.2.0 are not reflected.
That is just a field and can be changed easily
>   The .odt also needs layout work.  There's too much white space and I have 
> not looked closely enough to figure out why.
[knmc]
I suspect that it is due to the styles choices I made. I based them off
the standard headings and text styles. I do not see to much white space
, but that may be a difference on how we view document structure.
>
> I know we differ on formatting and some document organization matters.  I am 
> not going to address them at this point.
There are always going to be those kinds of differences and compromises
have to be made on all sides. That is why I am seeking feedback.
> I am going to 1.0.0 now, essentially with the 0.2.0 except for the change of 
> version number and removal of the limitation to testing use.  I did the other 
> repair you suggested.  I think Marcus is ready on the other binaries, so 
> something will happen tomorrow (Friday).  
Given the time critical nature it is imperative that the general release
be done quickly. As I said earlier it took me longer than I had
anticipated to get the structure to where I wanted it.

Regards
Keith
>
> I'm not certain what the final inch is just yet, but it looks like everything 
> is ready enough.
>
>  - Dennis
>> regards
>> Keith
>>>
>>> -
>>> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: qa-h...@openoffice.apache.org
>>>
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org
>




signature.asc
Description: OpenPGP digital signature

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Thursday, August 18, 2016 14:40
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Am 08/16/2016 05:26 AM, schrieb Dennis E. Hamilton:
> > BETA 0.2.0 IS NOW AVAILABLE
> >
> > This is a cleanup version.  It is hoped that this will be the last
> change before bumping the version to 1.0.0 and making general
> availability.
> >
> > One important change:
> >
> >  The names of the files have been changed.
> >
> >  The README is now named README-4.1.2-patch1-Windows.txt.
> >
> >  The zip and the related .asc, .md5, .sha1, and .sha256 files all
> have the base name
> >  apache-openoffice-4.1.2-patch1-Win_x86.zip
> >
> > The two scripts also have simpler names:
> >
> >  APPLY-4.1.2-patch1.bat
> >  REVERT-4.1.2-patch1.bat
> >
> > The files are still available at
> >
> >  <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/Windows>
> >
> > Now it is worth testing enough to know there is no regression and that
> APPLY and REVERT operate properly as before.
> 
> I've downloaded the new ZIP and tested again:
> 
> - Download new ZIP file   OK
> - Unzipping   OK
> - ASC signature   OK
> - MD5 OK
> - SHA1OK
> - SHA256  OK
> - "tl.dll.new" ASC signature  OK
> - "tl.dll.old" ASC signature  OK
> 
> The both .bat files differ from the past ones. I've not run the new ones
> again but looked closely to the diff output. There are no functional
> changes but only for file name and version.
> 
> If I should run them again, just tell me.
> 
> Otherwise I think also this ZIP is ready to do its work.
> 
> Marcus
[orcmid] 

That's great, Marcus.  Thanks.

I will go ahead and cut 1.0.0 now.  

 - Dennis


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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Thursday, August 18, 2016 14:46
> To: qa@openoffice.apache.org; d...@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
[ ... ]
> [knmc]
> As we move forward to a general distribution here  is an odt revision of
> the readme that can be used to generate an html, pdf, or text versions.
> All versions are attached but may not come through to the list. They can
> all be accessed from the following link.
> <https://1drv.ms/f/s!AMMYmStvrJNJgQQ>
> All feedback is both welcomed and encouraged.
[orcmid] 

The .odt and the .txt file come through as attachments.

Do you have specific recommendations about what should be done with these?  

I notice that there are problems with the .txt file layout not having hard line 
breaks.  The name changes and dates in 0.2.0 are not reflected.  The .odt also 
needs layout work.  There's too much white space and I have not looked closely 
enough to figure out why.

I know we differ on formatting and some document organization matters.  I am 
not going to address them at this point.

I am going to 1.0.0 now, essentially with the 0.2.0 except for the change of 
version number and removal of the limitation to testing use.  I did the other 
repair you suggested.  I think Marcus is ready on the other binaries, so 
something will happen tomorrow (Friday).  

I'm not certain what the final inch is just yet, but it looks like everything 
is ready enough.

 - Dennis
> 
> regards
> Keith
> >
> >
> > -
> > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: qa-h...@openoffice.apache.org
> >



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

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Keith N. McKenna]

Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Monday, August 15, 2016 21:05
>> To: qa@openoffice.apache.org; d...@openoffice.apache.org
>> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
>>
>>
>> Dennis E. Hamilton wrote:
>>> BETA 0.2.0 IS NOW AVAILABLE
>>>
>>> This is a cleanup version.  It is hoped that this will be the last
>> change before bumping the version to 1.0.0 and making general
>> availability.
>>> One important change:
>>>
>>> The names of the files have been changed.
>>>
>>> The README is now named README-4.1.2-patch1-Windows.txt.
>>>
>>> The zip and the related .asc, .md5, .sha1, and .sha256 files all
>> have the base name
>>> apache-openoffice-4.1.2-patch1-Win_x86.zip
>>>
>>> The two scripts also have simpler names:
>>>
>>> APPLY-4.1.2-patch1.bat
>>> REVERT-4.1.2-patch1.bat
>>>
>>> The files are still available at
>>>
>>> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/Windows>
>> [knmc]
>> the link should read
>> <
> [orcmid] 
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/binaries/Windows/>
> [orcmid] 
>
> Right you are.  Thanks for the quick check.
>> Regards
>> Keith
>>> Now it is worth testing enough to know there is no regression and that
>> APPLY and REVERT operate properly as before.
>>>  - Dennis
>>>
> [ ... ]
[knmc]
As we move forward to a general distribution here  is an odt revision of
the readme that can be used to generate an html, pdf, or text versions.
All versions are attached but may not come through to the list. They can
all be accessed from the following link.
<https://1drv.ms/f/s!AMMYmStvrJNJgQQ>
All feedback is both welcomed and encouraged.

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



New_Readmeforpatch.odt
Description: application/vnd.oasis.opendocument.text
Title: Readme




APPLYING
HOTFIX FOR APACHE OPENOFFICE ON WINDOWS

README-4.1.2-patch1-apply-Windows.txt	1.0.0	2016-08-07

	
		
		Table of
		Contents
	
	Notice	1
	Purpose	1
	Intended
	Audience	1
	Prerequisites	2
	Preliminary
	Instructions	2
	Apply Patch
	Automatically	3
	Removing the Patch	3
	Appendicies	4
	Manually
	Apply Patch	4
	Troubleshooting	4




Notice
Licensed to the Apache Software
Foundation (ASF) under one or more contributor license agreements.
The ASF licenses this file to you under the Apache License, Version
2.0 (the "License"). You may obtain a copy of the License
at http://www.apache.org/licenses/LICENSE-2.0
Purpose
The purpose of this document is to
describe how to apply the hotfix to eliminate a security
vulnerability identified as CVE-2016-1513. The latest details about
that vulnerability and its mitigation can be found on the web at
<http://www.openoffice.org/security/cves/CVE-2016-1513.html>.
The hotfix is provided as a zip
file at the following
location:<https://dist.apache.org/repos/dist/release/openoffice/4.1.2-patch1/>

Intended Audience
This document is primarily
intended for use by non-technical individuals but presumes
familiarity with the following;

	Your account has
	administrator privileges or you have access to an adminstrator
	password
	NOTE: If your Operating System
	is Windows XP you must be logged into an account with administrator
	privileges.
	Use of a web browser to
	download files from the internet
	Use of the file manager to
	locate files and folders
	Use of the file manager to
	select files

Prerequisites

	Apache OpenOffice Version
	4.1.2 
	
	Quickstarter must be off

Preliminary
Instructions

	Verify installed version is
	4.1.2
	
		Open Apache OpenOffice 
		
	
	Download the zip file from
	<https://dist.apache.org/repos/dist/release/openoffice/4.1.2-patch1/>
	
		Use of the download folder
		for this procedure is fine
	
	Navigate to the above folder
	with the file manager
	Select the downloaded zip
	file
	Right click the zip file
	Select Extract All... from
	the context menu
	
		This will create a folder in
		the same folder you downloaded the archive with the contents of the
		archive un-packed in it
	
	Open the new folder from step
	5 it should contain the following files
	
		README-4.1.2-patch1-apply-Windows.txt
		
			This procedure
		
		LICENSE.txt
		
			The Apache License Version
			2.0 under which the .zip and i

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Marcus]

Am 08/16/2016 05:26 AM, schrieb Dennis E. Hamilton:

BETA 0.2.0 IS NOW AVAILABLE

This is a cleanup version.  It is hoped that this will be the last change 
before bumping the version to 1.0.0 and making general availability.

One important change:

 The names of the files have been changed.

 The README is now named README-4.1.2-patch1-Windows.txt.

 The zip and the related .asc, .md5, .sha1, and .sha256 files all have the 
base name
 apache-openoffice-4.1.2-patch1-Win_x86.zip

The two scripts also have simpler names:

 APPLY-4.1.2-patch1.bat
 REVERT-4.1.2-patch1.bat

The files are still available at

 <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/Windows>

Now it is worth testing enough to know there is no regression and that APPLY 
and REVERT operate properly as before.


I've downloaded the new ZIP and tested again:

- Download new ZIP file OK
- Unzipping OK
- ASC signature OK
- MD5   OK
- SHA1  OK
- SHA256OK
- "tl.dll.new" ASC signature  OK
- "tl.dll.old" ASC signature  OK

The both .bat files differ from the past ones. I've not run the new ones 
again but looked closely to the diff output. There are no functional 
changes but only for file name and version.


If I should run them again, just tell me.

Otherwise I think also this ZIP is ready to do its work.

Marcus




-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Thursday, August 11, 2016 21:08
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE

The scripts make life much easier, since users don't have to go hunting
for anything and digging around in operating-system locations.

You should be able to go through the procedure that uses the automated
steps pretty easily.

It is very important to know the difficulties that arise or whether
there were none.

The material is available at
<http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
patch1/binaries/Windows>.

  - Dennis




-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Wednesday, August 10, 2016 18:01
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Beta version 0.1.0 is now nearing completion.

It will include two scripts, one for applying the patch, the other for
reverting the patch.

The .zip will also have a copy of the original 4.1.2 tl.dll as well as
the new one.  These are used in the procedures to verify the files

that

are present in the OpenOffice configuration in order to apply the

patch

and also to remove it.

Next steps:
  * Additional path testing of the two scripts and verification that
operation on Windows XP and on Windows 10 work as expected.

[orcmid]

Done

It is also much easier to work through the patch checks using the
scripts.


  * Updating of the README to reflect the availability of the batch-

file

scripts as well as the manual procedure if ever needed.

[orcmid]

Done



  * Although the Zips already carry executable code (i.e., DLLs) there
may be some Antivirus push-back where the policy is to not allow .zip
files with scripts in them.  The README will also have to address that
possibility.

[orcmid]

I forgot that at the last minute.  I will put that into the next
version.  Meanwhile, those who check these procedures should report any
AV objections they ran into.




  - Dennis


-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Monday, August 8, 2016 09:58
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has

been

introduced into the files (and the .zip) at
<https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
patch1/binaries/Windows>.

This version reflects suggestions by Marcus Lange, Pedro Lino, and

Keith

McKenna.  Suggestions that are not (yet) implemented will be

discussed

in replies to their messages and on the bugzilla issue at
<https://bz.apache.org/ooo/show_bug.cgi?id=127065>.


By its nature, this material is intended for users operating on

Windows.

In some cases, incompatible forms are used on the Subversion server
where the above files are situated.  Version 0.0.1 attempts to
accommodate for this incompatibility.  In continuing to verify the
procedure, please indicate whether there are (now) difficulties

using

the text files, especially on Windows.

Users of Linux systems may have difficulties with some utilities for
which the Windows versions of the same tool (e.g., md5sum) do not
produce Linux-acceptable line endings.  It is useful to know if that

is

st

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Keith N. McKenna]

Dennis E. Hamilton wrote:
> BETA 0.2.0 IS NOW AVAILABLE
>
> This is a cleanup version.  It is hoped that this will be the last change 
> before bumping the version to 1.0.0 and making general availability.
>
> One important change:
>
> The names of the files have been changed.  
>
> The README is now named README-4.1.2-patch1-Windows.txt.
>
> The zip and the related .asc, .md5, .sha1, and .sha256 files all have the 
> base name
> apache-openoffice-4.1.2-patch1-Win_x86.zip
>
> The two scripts also have simpler names:
>
> APPLY-4.1.2-patch1.bat
> REVERT-4.1.2-patch1.bat
>
> The files are still available at
>
> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/Windows>
[knmc]
the link should read
<https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/binaries/Windows/>

Regards
Keith
>
> Now it is worth testing enough to know there is no regression and that APPLY 
> and REVERT operate properly as before.
>
>  - Dennis
>
>> -Original Message-
>> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>> Sent: Thursday, August 11, 2016 21:08
>> To: d...@openoffice.apache.org
>> Cc: qa@openoffice.apache.org
>> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
>> BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
>>
>> The scripts make life much easier, since users don't have to go hunting
>> for anything and digging around in operating-system locations.
>>
>> You should be able to go through the procedure that uses the automated
>> steps pretty easily.
>>
>> It is very important to know the difficulties that arise or whether
>> there were none.
>>
>> The material is available at
>> <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/Windows>.
>>
>>  - Dennis
>>
>>
>>
>>> -Original Message-
>>> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>>> Sent: Wednesday, August 10, 2016 18:01
>>> To: d...@openoffice.apache.org
>>> Cc: qa@openoffice.apache.org
>>> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>>
>>> Beta version 0.1.0 is now nearing completion.
>>>
>>> It will include two scripts, one for applying the patch, the other for
>>> reverting the patch.
>>>
>>> The .zip will also have a copy of the original 4.1.2 tl.dll as well as
>>> the new one.  These are used in the procedures to verify the files
>> that
>>> are present in the OpenOffice configuration in order to apply the
>> patch
>>> and also to remove it.
>>>
>>> Next steps:
>>>  * Additional path testing of the two scripts and verification that
>>> operation on Windows XP and on Windows 10 work as expected.
>> [orcmid]
>>
>> Done
>>
>> It is also much easier to work through the patch checks using the
>> scripts.
>>>  * Updating of the README to reflect the availability of the batch-
>> file
>>> scripts as well as the manual procedure if ever needed.
>> [orcmid]
>>
>> Done
>>
>>>  * Although the Zips already carry executable code (i.e., DLLs) there
>>> may be some Antivirus push-back where the policy is to not allow .zip
>>> files with scripts in them.  The README will also have to address that
>>> possibility.
>> [orcmid]
>>
>> I forgot that at the last minute.  I will put that into the next
>> version.  Meanwhile, those who check these procedures should report any
>> AV objections they ran into.
>>
>>
>>>  - Dennis
>>>
>>>> -Original Message-
>>>> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>>>> Sent: Monday, August 8, 2016 09:58
>>>> To: d...@openoffice.apache.org
>>>> Cc: qa@openoffice.apache.org
>>>> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>>>
>>>> Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has
>> been
>>>> introduced into the files (and the .zip) at
>>>> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>>>> patch1/binaries/Windows>.
>>>>
>>>> This version reflects suggestions by Marcus Lange, Pedro Lino, and
>>> Keith
>>>> McKenna.  Suggestions that are not (yet) implemented will be
>> discussed
>>>> in replies to their messages and on the bugzilla issue at
>>>> <https://bz.apache.o

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

BETA 0.2.0 IS NOW AVAILABLE

This is a cleanup version.  It is hoped that this will be the last change 
before bumping the version to 1.0.0 and making general availability.

One important change:

The names of the files have been changed.  

The README is now named README-4.1.2-patch1-Windows.txt.

The zip and the related .asc, .md5, .sha1, and .sha256 files all have the 
base name
apache-openoffice-4.1.2-patch1-Win_x86.zip

The two scripts also have simpler names:

APPLY-4.1.2-patch1.bat
REVERT-4.1.2-patch1.bat

The files are still available at

<https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/Windows>

Now it is worth testing enough to know there is no regression and that APPLY 
and REVERT operate properly as before.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Thursday, August 11, 2016 21:08
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
> 
> The scripts make life much easier, since users don't have to go hunting
> for anything and digging around in operating-system locations.
> 
> You should be able to go through the procedure that uses the automated
> steps pretty easily.
> 
> It is very important to know the difficulties that arise or whether
> there were none.
> 
> The material is available at
> <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>.
> 
>  - Dennis
> 
> 
> 
> > -Original Message-
> > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > Sent: Wednesday, August 10, 2016 18:01
> > To: d...@openoffice.apache.org
> > Cc: qa@openoffice.apache.org
> > Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> >
> > Beta version 0.1.0 is now nearing completion.
> >
> > It will include two scripts, one for applying the patch, the other for
> > reverting the patch.
> >
> > The .zip will also have a copy of the original 4.1.2 tl.dll as well as
> > the new one.  These are used in the procedures to verify the files
> that
> > are present in the OpenOffice configuration in order to apply the
> patch
> > and also to remove it.
> >
> > Next steps:
> >  * Additional path testing of the two scripts and verification that
> > operation on Windows XP and on Windows 10 work as expected.
> [orcmid]
> 
> Done
> 
> It is also much easier to work through the patch checks using the
> scripts.
> >
> >  * Updating of the README to reflect the availability of the batch-
> file
> > scripts as well as the manual procedure if ever needed.
> [orcmid]
> 
> Done
> 
> >
> >  * Although the Zips already carry executable code (i.e., DLLs) there
> > may be some Antivirus push-back where the policy is to not allow .zip
> > files with scripts in them.  The README will also have to address that
> > possibility.
> [orcmid]
> 
> I forgot that at the last minute.  I will put that into the next
> version.  Meanwhile, those who check these procedures should report any
> AV objections they ran into.
> 
> 
> >
> >  - Dennis
> >
> > > -Original Message-
> > > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > > Sent: Monday, August 8, 2016 09:58
> > > To: d...@openoffice.apache.org
> > > Cc: qa@openoffice.apache.org
> > > Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> > >
> > > Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has
> been
> > > introduced into the files (and the .zip) at
> > > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> > > patch1/binaries/Windows>.
> > >
> > > This version reflects suggestions by Marcus Lange, Pedro Lino, and
> > Keith
> > > McKenna.  Suggestions that are not (yet) implemented will be
> discussed
> > > in replies to their messages and on the bugzilla issue at
> > > <https://bz.apache.org/ooo/show_bug.cgi?id=127065>.
> > >
> > >
> > > By its nature, this material is intended for users operating on
> > Windows.
> > > In some cases, incompatible forms are used on the Subversion server
> > > where the above files are situated.  Version 0.0.1 attempts to
> > > accommodate for this incompatibility.  In continuing to verify the
> > > procedure, please indicate whether there are (now) difficulties
> using
> > > the text files, especially on Windows.
> >

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Saturday, August 13, 2016 13:20
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
[ ... ]
> PS:
> However, I've a point that could be improved.
> 
> The name of the script files are very long. Same for the Readme. Inside
> the zip'ed file there is no need to repeat the complete patch name
> structure. IMHO they're better recognizable when it's just an
> "Apply.bat", "Revert.bat" and "Readme_Win.txt".
> 
> 
[orcmid] 

I looked into the naming.  These changes will help:

 1. There is no longer any need for -apply in the names now that there is a 
single distribution that provides a script and provides manual instructions as 
an alternative.

 2. There is no reason to mention -Windows in the name of a .bat file, since 
that is where those run these days.

 3. I still want to be specific to 4.1.2-patch1 so that it is always clear what 
these are about, wherever the materials happen to be found on an user's PC.  
That should be evident without examining the .bat file or even knowing how to 
do that without causing it to be executed [;<).  (It's a bit like the reasoning 
to have the README available to download directly so it can be read without 
downloading the full .zip.)

I'll do all of this in a 0.2.0 beta that I'll build today, Sunday.  There are 
some other suggestions that I will look into, after those are in the dev SVN, 
that may improve the text more.  At this point, I am concerned about 
introducing regressions.

 - Dennis
> 
> Thanks a lot for providing the script files. This will be a great help
> for the normal users.
> 
> If you need more details or tests just tell me.
> 
> Marcus
> 
> 
> 
[ ... ]


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

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Marcus]

Am 08/14/2016 10:17 AM, schrieb Marcus:

Am 08/14/2016 01:07 AM, schrieb Dennis E. Hamilton:

Thanks for the checking, Marcus.


-Original Message-
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Saturday, August 13, 2016 13:20
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Am 08/12/2016 06:07 AM, schrieb Dennis E. Hamilton:

BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE

The scripts make life much easier, since users don't have to go

hunting for anything and digging around in operating-system locations.


You should be able to go through the procedure that uses the automated

steps pretty easily.


It is very important to know the difficulties that arise or whether

there were none.


The material is available at
<http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-

patch1/binaries/Windows>.

great to have now a script-based installation. Here is my test procedure
on Windows 10 Home:

APPLY script:

- When starting the script I get a "... Windows SmartScreen has
prevented the start of a not recognized app. To run this App,
Administrator permission is needed ..." message. Doing so, it started
but showed a message [1] that Administrator permission is needed. I've
verified that nothing was done or changed.

- When starting with right-clicked "Run as Administrator" the script
showed some useful information [1], renamed the old file and copied the
new file.

REVERT script:

- When starting the script I get a "... Windows SmartScreen has
prevented the start of a not recognized app. To run this App,
Administrator permission is needed ..." message. Doing so, it started
but showed a message [1] that Administrator permission is needed. I've
verified that nothing was done or changed.

- When starting with right-clicked "Run as Administrator" the script
showed some useful information [1], deleted the new file and renamed the
old file back to the old name.

At the end both scripts are working successfully.

[1] The command line window where the output information is shown uses a
*very little* font size (looked like 4pt or similar) and is therefore
nearyl unreadable. I had to increase the font size in the properties of
the window (click on the icon in the top left corner).

[orcmid]

The font size is not under control of the script. I have no idea what
has it be so small in your case. Changing it should be persistent now.


yes, it must come from Windows. Actual it was a 10pt fonsize but with a
resolution of ? x ? even this looks like much too small.


I've pressed too fast the [Send] button. It's a 1920 x 1080 resolution.

Marcus


PS:
However, I've a point that could be improved.

The name of the script files are very long. Same for the Readme. Inside
the zip'ed file there is no need to repeat the complete patch name
structure. IMHO they're better recognizable when it's just an
"Apply.bat", "Revert.bat" and "Readme_Win.txt".

[orcmid]

Well, yes, especially the Readme. At this late point, I'd like to get
to 1.0.0 without risking any regression in the text. I don't like
these things becoming mysteries if separated from the packages.

I will give it serious consideration.


You can put a descriptive text into the script as comment lines. So,
then it's clear what it is and where it comes from. OK, if you don't
want to change it for this patch then next time. ;-)

Marcus




Thanks a lot for providing the script files. This will be a great help
for the normal users.

If you need more details or tests just tell me.

Marcus




-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Wednesday, August 10, 2016 18:01
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Beta version 0.1.0 is now nearing completion.

It will include two scripts, one for applying the patch, the other

for

reverting the patch.

The .zip will also have a copy of the original 4.1.2 tl.dll as well

as

the new one. These are used in the procedures to verify the files

that

are present in the OpenOffice configuration in order to apply the

patch

and also to remove it.

Next steps:
* Additional path testing of the two scripts and verification that
operation on Windows XP and on Windows 10 work as expected.

[orcmid]

Done

It is also much easier to work through the patch checks using the

scripts.


* Updating of the README to reflect the availability of the batch-

file

scripts as well as the manual procedure if ever needed.

[orcmid]

Done



* Although the Zips already carry executable code (i.e., DLLs)

there

may be some Antivirus push-back where the policy is to not allow .zip
files with scripts in them. The README will also have to address

that

possibility.

[orcmid]

I forgot that at the last minute. I will put that into the next

version. Meanwhil

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Marcus]

Am 08/14/2016 01:07 AM, schrieb Dennis E. Hamilton:

Thanks for the checking, Marcus.


-Original Message-
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Saturday, August 13, 2016 13:20
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Am 08/12/2016 06:07 AM, schrieb Dennis E. Hamilton:

BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE

The scripts make life much easier, since users don't have to go

hunting for anything and digging around in operating-system locations.


You should be able to go through the procedure that uses the automated

steps pretty easily.


It is very important to know the difficulties that arise or whether

there were none.


The material is available at
<http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-

patch1/binaries/Windows>.

great to have now a script-based installation. Here is my test procedure
on Windows 10 Home:

APPLY script:

- When starting the script I get a "... Windows SmartScreen has
prevented the start of a not recognized app. To run this App,
Administrator permission is needed ..." message. Doing so, it started
but showed a message [1] that Administrator permission is needed. I've
verified that nothing was done or changed.

- When starting with right-clicked "Run as Administrator" the script
showed some useful information [1], renamed the old file and copied the
new file.

REVERT script:

- When starting the script I get a "... Windows SmartScreen has
prevented the start of a not recognized app. To run this App,
Administrator permission is needed ..." message. Doing so, it started
but showed a message [1] that Administrator permission is needed. I've
verified that nothing was done or changed.

- When starting with right-clicked "Run as Administrator" the script
showed some useful information [1], deleted the new file and renamed the
old file back to the old name.

At the end both scripts are working successfully.

[1] The command line window where the output information is shown uses a
*very little* font size (looked like 4pt or similar) and is therefore
nearyl unreadable. I had to increase the font size in the properties of
the window (click on the icon in the top left corner).

[orcmid]

The font size is not under control of the script.  I have no idea what has it 
be so small in your case.  Changing it should be persistent now.


yes, it must come from Windows. Actual it was a 10pt fonsize but with a 
resolution of ? x ? even this looks like much too small.



PS:
However, I've a point that could be improved.

The name of the script files are very long. Same for the Readme. Inside
the zip'ed file there is no need to repeat the complete patch name
structure. IMHO they're better recognizable when it's just an
"Apply.bat", "Revert.bat" and "Readme_Win.txt".

[orcmid]

Well, yes, especially the Readme.  At this late point, I'd like to get to 1.0.0 
without risking any regression in the text.  I don't like these things becoming 
mysteries if separated from the packages.

I will give it serious consideration.


You can put a descriptive text into the script as comment lines. So, 
then it's clear what it is and where it comes from. OK, if you don't 
want to change it for this patch then next time. ;-)


Marcus




Thanks a lot for providing the script files. This will be a great help
for the normal users.

If you need more details or tests just tell me.

Marcus




-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Wednesday, August 10, 2016 18:01
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Beta version 0.1.0 is now nearing completion.

It will include two scripts, one for applying the patch, the other

for

reverting the patch.

The .zip will also have a copy of the original 4.1.2 tl.dll as well

as

the new one.  These are used in the procedures to verify the files

that

are present in the OpenOffice configuration in order to apply the

patch

and also to remove it.

Next steps:
   * Additional path testing of the two scripts and verification that
operation on Windows XP and on Windows 10 work as expected.

[orcmid]

Done

It is also much easier to work through the patch checks using the

scripts.


   * Updating of the README to reflect the availability of the batch-

file

scripts as well as the manual procedure if ever needed.

[orcmid]

Done



   * Although the Zips already carry executable code (i.e., DLLs)

there

may be some Antivirus push-back where the policy is to not allow .zip
files with scripts in them.  The README will also have to address

that

possibility.

[orcmid]

I forgot that at the last minute.  I will put that into the next

version.  Meanwhile, those who check these procedures should report any
AV objections they ran into.





   - Denni

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Keith N. McKenna]

Dennis;
Attached is an odt file with mark-ups and comments for a couple of
changes for the readme. For the general public release I have been
working on a draft of a more formal format that can be used as a
template for future situations such as this.

Keith

Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Friday, August 12, 2016 13:49
>> To: qa@openoffice.apache.org; d...@openoffice.apache.org
>> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
>> Attached is a text file with the tests that I ran and the results of
>> each. The only problem encountered was in verifying tl.dll.new with the
>> .asc signature file. This was due to the web of trust issue discussed
>> earlier in this thread.Patricia's signature had not been certified by
>> anyone. One I elevated the Owner Trust level and certified it the
>> verification passed.
>>
>> I will finish reviewing the latest documentation and send any comments
>> or suggested changes under separate cover.
>>
>> Regards
>> Keith
> [orcmid] 
>
> Thanks Keith.  The copy-paste error in the APPLY :FAIL3 message will be 
> fixed.  Thanks for being so attentive and meticulous.  Your test log is 
> wonderful.
>
>  I'm gratified that the Administrator Permissions pain has been alleviated on 
> both admin and standard Windows 7 accounts.
>
> I look forward to anything else you come up with.  I anticipate that we can 
> go to 1.0.0 for the next round and make general availability next week.
>
>  - Dennis
>>
>> Dennis E. Hamilton wrote:
>>
>>
>>  BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
>>
>>  The scripts make life much easier, since users don't have to go
>> hunting for anything and digging around in operating-system locations.
>>
>>  You should be able to go through the procedure that uses the
>> automated steps pretty easily.
>>
>>  It is very important to know the difficulties that arise or whether
>> there were none.
>>
>>  The material is available at
>>  <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/Windows>
>> <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/Windows> .
>>
>>   - Dennis
> [ ... ]
>
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org
>



README-4.1.2-patch1-apply-Windows.odt
Description: application/vnd.oasis.opendocument.text


signature.asc
Description: OpenPGP digital signature

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Marcus]

Am 08/12/2016 06:07 AM, schrieb Dennis E. Hamilton:

BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE

The scripts make life much easier, since users don't have to go hunting for 
anything and digging around in operating-system locations.

You should be able to go through the procedure that uses the automated steps 
pretty easily.

It is very important to know the difficulties that arise or whether there were 
none.

The material is available at
<http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/binaries/Windows>.


great to have now a script-based installation. Here is my test procedure 
on Windows 10 Home:


APPLY script:

- When starting the script I get a "... Windows SmartScreen has 
prevented the start of a not recognized app. To run this App, 
Administrator permission is needed ..." message. Doing so, it started 
but showed a message [1] that Administrator permission is needed. I've 
verified that nothing was done or changed.


- When starting with right-clicked "Run as Administrator" the script 
showed some useful information [1], renamed the old file and copied the 
new file.


REVERT script:

- When starting the script I get a "... Windows SmartScreen has 
prevented the start of a not recognized app. To run this App, 
Administrator permission is needed ..." message. Doing so, it started 
but showed a message [1] that Administrator permission is needed. I've 
verified that nothing was done or changed.


- When starting with right-clicked "Run as Administrator" the script 
showed some useful information [1], deleted the new file and renamed the 
old file back to the old name.


At the end both scripts are working successfully.

[1] The command line window where the output information is shown uses a 
*very little* font size (looked like 4pt or similar) and is therefore 
nearyl unreadable. I had to increase the font size in the properties of 
the window (click on the icon in the top left corner).


PS:
However, I've a point that could be improved.

The name of the script files are very long. Same for the Readme. Inside 
the zip'ed file there is no need to repeat the complete patch name 
structure. IMHO they're better recognizable when it's just an 
"Apply.bat", "Revert.bat" and "Readme_Win.txt".




Thanks a lot for providing the script files. This will be a great help 
for the normal users.


If you need more details or tests just tell me.

Marcus




-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Wednesday, August 10, 2016 18:01
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Beta version 0.1.0 is now nearing completion.

It will include two scripts, one for applying the patch, the other for
reverting the patch.

The .zip will also have a copy of the original 4.1.2 tl.dll as well as
the new one.  These are used in the procedures to verify the files that
are present in the OpenOffice configuration in order to apply the patch
and also to remove it.

Next steps:
  * Additional path testing of the two scripts and verification that
operation on Windows XP and on Windows 10 work as expected.

[orcmid]

Done

It is also much easier to work through the patch checks using the scripts.


  * Updating of the README to reflect the availability of the batch-file
scripts as well as the manual procedure if ever needed.

[orcmid]

Done



  * Although the Zips already carry executable code (i.e., DLLs) there
may be some Antivirus push-back where the policy is to not allow .zip
files with scripts in them.  The README will also have to address that
possibility.

[orcmid]

I forgot that at the last minute.  I will put that into the next version.  
Meanwhile, those who check these procedures should report any AV objections 
they ran into.




  - Dennis


-Original Message-
From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
Sent: Monday, August 8, 2016 09:58
To: d...@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has been
introduced into the files (and the .zip) at
<https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
patch1/binaries/Windows>.

This version reflects suggestions by Marcus Lange, Pedro Lino, and

Keith

McKenna.  Suggestions that are not (yet) implemented will be discussed
in replies to their messages and on the bugzilla issue at
<https://bz.apache.org/ooo/show_bug.cgi?id=127065>.


By its nature, this material is intended for users operating on

Windows.

In some cases, incompatible forms are used on the Subversion server
where the above files are situated.  Version 0.0.1 attempts to
accommodate for this incompatibility.  In continuing to verify the
procedure, please indicate whether there are (now) difficulties using
the te

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Friday, August 12, 2016 13:49
> To: qa@openoffice.apache.org; d...@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Attached is a text file with the tests that I ran and the results of
> each. The only problem encountered was in verifying tl.dll.new with the
> .asc signature file. This was due to the web of trust issue discussed
> earlier in this thread.Patricia's signature had not been certified by
> anyone. One I elevated the Owner Trust level and certified it the
> verification passed.
> 
> I will finish reviewing the latest documentation and send any comments
> or suggested changes under separate cover.
> 
> Regards
> Keith
[orcmid] 

Thanks Keith.  The copy-paste error in the APPLY :FAIL3 message will be fixed.  
Thanks for being so attentive and meticulous.  Your test log is wonderful.

 I'm gratified that the Administrator Permissions pain has been alleviated on 
both admin and standard Windows 7 accounts.

I look forward to anything else you come up with.  I anticipate that we can go 
to 1.0.0 for the next round and make general availability next week.

 - Dennis
> 
> 
> Dennis E. Hamilton wrote:
> 
> 
>   BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
> 
>   The scripts make life much easier, since users don't have to go
> hunting for anything and digging around in operating-system locations.
> 
>   You should be able to go through the procedure that uses the
> automated steps pretty easily.
> 
>   It is very important to know the difficulties that arise or whether
> there were none.
> 
>   The material is available at
>   <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>
> <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows> .
> 
>- Dennis
[ ... ]



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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE

The scripts make life much easier, since users don't have to go hunting for 
anything and digging around in operating-system locations.

You should be able to go through the procedure that uses the automated steps 
pretty easily.

It is very important to know the difficulties that arise or whether there were 
none.

The material is available at 
<http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/binaries/Windows>.

 - Dennis



> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Wednesday, August 10, 2016 18:01
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Beta version 0.1.0 is now nearing completion.
> 
> It will include two scripts, one for applying the patch, the other for
> reverting the patch.
> 
> The .zip will also have a copy of the original 4.1.2 tl.dll as well as
> the new one.  These are used in the procedures to verify the files that
> are present in the OpenOffice configuration in order to apply the patch
> and also to remove it.
> 
> Next steps:
>  * Additional path testing of the two scripts and verification that
> operation on Windows XP and on Windows 10 work as expected.
[orcmid] 

Done
 
It is also much easier to work through the patch checks using the scripts.
> 
>  * Updating of the README to reflect the availability of the batch-file
> scripts as well as the manual procedure if ever needed.
[orcmid] 

Done

> 
>  * Although the Zips already carry executable code (i.e., DLLs) there
> may be some Antivirus push-back where the policy is to not allow .zip
> files with scripts in them.  The README will also have to address that
> possibility.
[orcmid] 

I forgot that at the last minute.  I will put that into the next version.  
Meanwhile, those who check these procedures should report any AV objections 
they ran into.


> 
>  - Dennis
> 
> > -Original Message-
> > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > Sent: Monday, August 8, 2016 09:58
> > To: d...@openoffice.apache.org
> > Cc: qa@openoffice.apache.org
> > Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> >
> > Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has been
> > introduced into the files (and the .zip) at
> > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> > patch1/binaries/Windows>.
> >
> > This version reflects suggestions by Marcus Lange, Pedro Lino, and
> Keith
> > McKenna.  Suggestions that are not (yet) implemented will be discussed
> > in replies to their messages and on the bugzilla issue at
> > <https://bz.apache.org/ooo/show_bug.cgi?id=127065>.
> >
> >
> > By its nature, this material is intended for users operating on
> Windows.
> > In some cases, incompatible forms are used on the Subversion server
> > where the above files are situated.  Version 0.0.1 attempts to
> > accommodate for this incompatibility.  In continuing to verify the
> > procedure, please indicate whether there are (now) difficulties using
> > the text files, especially on Windows.
> >
> > Users of Linux systems may have difficulties with some utilities for
> > which the Windows versions of the same tool (e.g., md5sum) do not
> > produce Linux-acceptable line endings.  It is useful to know if that
> is
> > still the case.  The files have been confirmed to be usable using the
> > utilities built for use on Windows.
> >
> > For future versions, the use of HTML instead of text will be
> considered.
> > HTML does not have white-space incompatibility problems across
> different
> > platforms. The HTML will also be digitally-signed as a means of
> > verifying its authenticity.
> >
> > In addition to possibly using HTML as a better form for cross-platform
> > use of text, attention will now move toward introducing scripts that
> > automatically apply the change, replacing all of steps 9-18.
> >
> > Meanwhile, it is valuable to continue testing that the replacement
> file
> > produces no regression or introduction of any defects not seen using
> an
> > unmodified Apache OpenOffice 4.1.2.
> >
> >  - Dennis
> >
> >
> > > -Original Message-
> > > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > > Sent: Tuesday, August 2, 2016 20:31
> > > To: d...@openoffice.apache.org
> > > Cc: qa@openoffice.apache.org
> > > Subject: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> > >
> > > Testin

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

Beta version 0.1.0 is now nearing completion.

It will include two scripts, one for applying the patch, the other for 
reverting the patch.

The .zip will also have a copy of the original 4.1.2 tl.dll as well as the new 
one.  These are used in the procedures to verify the files that are present in 
the OpenOffice configuration in order to apply the patch and also to remove it.

Next steps:
 * Additional path testing of the two scripts and verification that operation 
on Windows XP and on Windows 10 work as expected.

 * Updating of the README to reflect the availability of the batch-file scripts 
as well as the manual procedure if ever needed.

 * Although the Zips already carry executable code (i.e., DLLs) there may be 
some Antivirus push-back where the policy is to not allow .zip files with 
scripts in them.  The README will also have to address that possibility.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Monday, August 8, 2016 09:58
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has been
> introduced into the files (and the .zip) at
> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>.
> 
> This version reflects suggestions by Marcus Lange, Pedro Lino, and Keith
> McKenna.  Suggestions that are not (yet) implemented will be discussed
> in replies to their messages and on the bugzilla issue at
> <https://bz.apache.org/ooo/show_bug.cgi?id=127065>.
> 
> 
> By its nature, this material is intended for users operating on Windows.
> In some cases, incompatible forms are used on the Subversion server
> where the above files are situated.  Version 0.0.1 attempts to
> accommodate for this incompatibility.  In continuing to verify the
> procedure, please indicate whether there are (now) difficulties using
> the text files, especially on Windows.
> 
> Users of Linux systems may have difficulties with some utilities for
> which the Windows versions of the same tool (e.g., md5sum) do not
> produce Linux-acceptable line endings.  It is useful to know if that is
> still the case.  The files have been confirmed to be usable using the
> utilities built for use on Windows.
> 
> For future versions, the use of HTML instead of text will be considered.
> HTML does not have white-space incompatibility problems across different
> platforms. The HTML will also be digitally-signed as a means of
> verifying its authenticity.
> 
> In addition to possibly using HTML as a better form for cross-platform
> use of text, attention will now move toward introducing scripts that
> automatically apply the change, replacing all of steps 9-18.
> 
> Meanwhile, it is valuable to continue testing that the replacement file
> produces no regression or introduction of any defects not seen using an
> unmodified Apache OpenOffice 4.1.2.
> 
>  - Dennis
> 
> 
> > -Original Message-
> > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > Sent: Tuesday, August 2, 2016 20:31
> > To: d...@openoffice.apache.org
> > Cc: qa@openoffice.apache.org
> > Subject: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> >
> > Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
> >
> > The files to be used in testing are at
> > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>.
> >
> > The files to be tested and reviewed are
> >
> >  * README-4.1.2-patch1-apply-Windows.txt
> >The description of the procedure for applying a corrected
> >library file to installed copies of Apache OpenOffice 4.1.2
> >on Windows.  Read this first before deciding to download
> >the Zip file and attempting the procedure.
> >
> >  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
> >The Zip archive containing the files to be used in the
> >procedure.  There is a copy of the README within the
> >archive as well.
> >
> >  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
> >  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
> >  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
> >Files that provide a digital signature, an MD5 hash,
> >and an SHA256 hash that can be used to verify the
> >integrity of the download and, in the case of the
> >digital signature, the authenticity and accuracy of
> >the download.
> >
> > REQUESTED TESTING
> >
> >  * [OPTIONAL] If you are able to check any of the .asc,
> >.md5, and .sha25

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has been 
introduced into the files (and the .zip) at 
.

This version reflects suggestions by Marcus Lange, Pedro Lino, and Keith 
McKenna.  Suggestions that are not (yet) implemented will be discussed in 
replies to their messages and on the bugzilla issue at 
.


By its nature, this material is intended for users operating on Windows.  In 
some cases, incompatible forms are used on the Subversion server where the 
above files are situated.  Version 0.0.1 attempts to accommodate for this 
incompatibility.  In continuing to verify the procedure, please indicate 
whether there are (now) difficulties using the text files, especially on 
Windows.

Users of Linux systems may have difficulties with some utilities for which the 
Windows versions of the same tool (e.g., md5sum) do not produce 
Linux-acceptable line endings.  It is useful to know if that is still the case. 
 The files have been confirmed to be usable using the utilities built for use 
on Windows.

For future versions, the use of HTML instead of text will be considered.  HTML 
does not have white-space incompatibility problems across different platforms. 
The HTML will also be digitally-signed as a means of verifying its authenticity.

In addition to possibly using HTML as a better form for cross-platform use of 
text, attention will now move toward introducing scripts that automatically 
apply the change, replacing all of steps 9-18.

Meanwhile, it is valuable to continue testing that the replacement file 
produces no regression or introduction of any defects not seen using an 
unmodified Apache OpenOffice 4.1.2.

 - Dennis


> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Tuesday, August 2, 2016 20:31
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
> 
> The files to be used in testing are at
> .
> 
> The files to be tested and reviewed are
> 
>  * README-4.1.2-patch1-apply-Windows.txt
>The description of the procedure for applying a corrected
>library file to installed copies of Apache OpenOffice 4.1.2
>on Windows.  Read this first before deciding to download
>the Zip file and attempting the procedure.
> 
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
>The Zip archive containing the files to be used in the
>procedure.  There is a copy of the README within the
>archive as well.
> 
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
>Files that provide a digital signature, an MD5 hash,
>and an SHA256 hash that can be used to verify the
>integrity of the download and, in the case of the
>digital signature, the authenticity and accuracy of
>the download.
> 
> REQUESTED TESTING
> 
>  * [OPTIONAL] If you are able to check any of the .asc,
>.md5, and .sha256 files against the .zip, report any
>difficulties that may have been encountered.
> 
>  * If you performed the procedure, report
> * the version of Microsoft Windows and the type of
>   account used (administrator or standard user).
> * report whether the procedure succeeded
> * if the procedure failed or met with difficulties,
>   please summarize the problems and how you over-
>   came any of them
> 
>  * [IMPORTANT] Identify any missing, incomplete or
>confusing information in the README.  Describe what you
>see as important improvements before making general
>release of the procedure for use by non-expert users of
>Apache OpenOffice on Windows.
> 
> The goal is to provide as much as we can to assist Windows users in
> applying this fix with confidence and success.  The experience of more-
> knowledgable users who appreciate the difficulties of non-experts is
> important in achieving that.
> 
> Thank you for any effort you invest and the feedback you provide.
> 
>  - Dennis
> 
> 
> 
> 
> 
> 
>  -- Dennis E. Hamilton
> orc...@apache.org
> dennis.hamil...@acm.org+1-206-779-9430
> https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> X.509 certs used and requested for signed e-mail
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Sunday, August 7, 2016 09:21
> To: d...@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Feedback for the .zip file:
> 
> Do you have a reason in mind for the "apply" in the file name? I would
> delete this as I don't see a benefit and it would shorten the file name.
[orcmid] 

I used the apply suffix to allow for there being a (semi-)automatic version 
that worked automatically later.  I would then propose hotfix or something for 
that.  This allowed for both to exist at some point.

I'd rather not change that now since folks know to look for it by that name, it 
is used in the readme, etc.

> 
> When extracting a ZIP file I cannot stand it when no subdirectory is
> included and the files are extracted where the current directory is at
> the moment. So, I've to search for the new files.
[orcmid] 

The Extract ... tool for Windows automatically creates a folder to put 
everything into, although it will be in the same folder as the .zip.  So having 
a folder in there simply adds an extra level.  That is using the Windows 
extract. 

Other tools, such as WinZip also allow the user to choose a folder destination, 
although it might take more work, and knowledgeable users of Zip tools know how 
to tell what to do that works according to the README.

> 
> Therefore please include a "files" dir (or similar name) into the ZIP
> file.
[orcmid] 

The normal choice would be something like 4.1.2-patch1-apply :).
> 
> 
> 
> Feedback for the README file.
[orcmid] 

Thank you.  I will go over all of the suggestions on the README that have come 
in so far, and provide an update today.


> 
> Line 25:
> It should be improve into "please consult a knowledgable person (e.g.,
> family member work colleauge, acquaintance) that is able to assist you".
> At least for me it sounds better.
> 
> Line 41.
> Put all OPTIONAL things at the section end.
> 
> Line 44/45:
> old: "... that are part of the system.installed."
> new: "... that are part of the installed system."
> 
> Line 64/65:
> One "which" is double.
> 
> Line 86-89:
> I don't know if this is necessary for this process. I think it would
> just foster help requests to the dev@ mailing list.
> 
> Line 111:
> I would write ", the .zip file is available to use.".
> 
> Line 114:
> One "or" is double.
> 
> Line 131:
> No, there is no folder extracted. Please include one (see at the top of
> this mail).
[orcmid] 

Did you not use the Windows "Extract ..." action on the context menu?

> 
> Line 147:
> IMHO this was stated already. Please don't rename the new file in the
> ZIP file. Otherwise the user has to do an additional file rename which
> should not be done.
[orcmid] 

That must be a misunderstanding.  I don't propose anything like that.

> 
> Line 153:
> The same for the ASC file.
> 
> Line 183 and 186:
> Both parts can be described together to save 1 step.
> 
> Line 208:
> This step should be avoided (see at the top of this mail).
> 
> Line 222-231:
> As stated previously (line 86-89).
> 
> Line 240:
> To give (again) the hint that OpenOffice should be closed before
> renaming the files would be nice to the user.
> 
> 
> I hope this feedback is helpful for you.
[orcmid] 

Yes, thank you.  I will look more closely when making the edits.

> 
> Marcus
> 
> 
> 
> Am 08/03/2016 05:31 AM, schrieb Dennis E. Hamilton:
> > Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
> >
> > The files to be used in testing are at
> > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>.
> >
> > The files to be tested and reviewed are
> >
> >   * README-4.1.2-patch1-apply-Windows.txt
> > The description of the procedure for applying a corrected
> > library file to installed copies of Apache OpenOffice 4.1.2
> > on Windows.  Read this first before deciding to download
> > the Zip file and attempting the procedure.
> >
> >   * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
> > The Zip archive containing the files to be used in the
> > procedure.  There is a copy of the README within the
> > archive as well.
> >
> >   * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
> >   * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
> >   * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
> > Files that provide a digital signature, an MD5 hash,
> > and an SHA256 hash tha

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Carl Marcum]

On 08/05/2016 12:28 PM, Dennis E. Hamilton wrote:

For tracking the [TESTING] of the 4.1.2-patch1 binary for windows, I have 
created task Issue 127065,
<https://bz.apache.org/ooo/show_bug.cgi?id=127065>.  Comment 7 there already 
speaks to the untrusted identification situation.

I am adding an abridged version of this message from Carl with the part 
relevant to certificate trust.  Note that most of us who have worked on 
4.1.2-patch1 and provided digital signatures will find that identity will be 
reported as untrusted based on the Web-of-Trust technique PGP software uses.  
We can, of course, verify the fingerprints and Apache account identity and 
certify each other.  That will change the status for those of us in this 
particular circle but not necessarily for anyone who does not already trust the 
identification of enough of us.

I don't think there is any way to get into this in our README files.  However, this 
is useful for any future contributions we might make to the page at 
<http://www.apache.org/dev/release-signing.html> or anything supplemental that 
is oriented to the users of Apache OpenOffice and their particular range of skills.


-Original Message-
From: Carl Marcum [mailto:cmar...@apache.org]
Sent: Friday, August 5, 2016 03:30
To: d...@openoffice.apache.org
Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

On 08/04/2016 06:52 PM, Marcus wrote:

Am 08/05/2016 12:26 AM, schrieb Kay Schenk:

On 08/04/2016 02:21 PM, Marcus wrote:

[ ... ]

* apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc

I don't know if this is OK or still bad:

gpg --verify apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
gpg: Signature made Tue 02 Aug 2016 06:24:08 AM CEST using RSA key

ID

D456628A
gpg: Good signature from "keybase.io/orcmid (confirmed identifier)
<orc...@keybase.io>"
gpg: aka "orcmid (Dennis E.

Hamilton)<orc...@msn.com>"

gpg: aka "orcmid Apache (code
signing)<orc...@apache.org>"
gpg: aka "Dennis E. Hamilton (orcmid)
<dennis.hamil...@acm.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to

the

owner.

I get this on sig checks also. There's probably a step we're missing

to

specify "trust" locally.

See:
http://www.apache.org/dev/release-signing.html

signing Dennis' key locally worked for me.
On Linux I use:
gpg --default-key 9553BF9A --sign-key D456628A

If the key you want to sign it with is already the default key you can
omit the "--default-key 9553BF9A" part.
Sometimes you may have to prefix the ID's with "0x" to denote hex.

If you trust this is Dennis' key you can send his key back with your sig
now attached and it will have more trust.
gpg --send-key 0xD456628A

If a few people do it the warning should go away. Web-of-trust  :)

Carl

[orcmid]

The warning will go away for us who have created a mutual Web-of-Trust but it 
won't help those who are not in that circle or have not somehow determined to 
trust in it themselves.  This is still useful advice about how to do it.

PS: I don't think the dist-level KEYS file is updated automatically, so the 
release KEYS set needs to be refreshed to work.  (We can check that by waiting 
for a while to see if Carl's trust of Dennis's key shows up.)


Dennis,

Yes I think I over simplified that.

Thanks for clarifying.

Best regards,
Carl


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

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Marcus]

Am 08/03/2016 05:31 AM, schrieb Dennis E. Hamilton:

Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.

The files to be used in testing are at
.

The files to be tested and reviewed are

  * README-4.1.2-patch1-apply-Windows.txt
The description of the procedure for applying a corrected
library file to installed copies of Apache OpenOffice 4.1.2
on Windows.  Read this first before deciding to download
the Zip file and attempting the procedure.


wow, really? I think I need much more time for this than an average 
evening. ;-) I'll do the README steps on Sunday.



  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
The Zip archive containing the files to be used in the
procedure.  There is a copy of the README within the
archive as well.


- I've exchanged the DLL
- Created a new text and presentation document with simple content.
- Both were reopened successfully.

Anything more to test?


  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc


I don't know if this is OK or still bad:

gpg --verify apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc 
apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
gpg: Signature made Tue 02 Aug 2016 06:24:08 AM CEST using RSA key ID 
D456628A
gpg: Good signature from "keybase.io/orcmid (confirmed identifier) 
"

gpg: aka "orcmid (Dennis E. Hamilton) "
gpg: aka "orcmid Apache (code signing) "
gpg: aka "Dennis E. Hamilton (orcmid) 
"

gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the 
owner.



  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5


Windows 10 Home (Version 1511):
I've visually compared the MD5 hashes from the ZIP and MD5 file
--> OK

Linux:
$ md5sum -c apache-openoffice-4.1.2-patch1.zip.md5
--> OK


  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256


Windows 10 Home (Version 1511):
I've visually compared the SHA256 hashes from the ZIP and SHA256 file
--> OK

Linux:
$ sha256sum -c apache-openoffice-4.1.2-patch1.zip.sha256
--> OK


REQUESTED TESTING

  * [OPTIONAL] If you are able to check any of the .asc,
.md5, and .sha256 files against the .zip, report any
difficulties that may have been encountered.


Please remove the new line at the end of the MD5 file. Otherwise it 
doesn't work on Linux:


md5sum -c apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
: No such file or directory.1.2-patch1-apply-Win_x86.zip
: FAILED open or read.2-patch1-apply-Win_x86.zip
md5sum: WARNING: 1 of 1 listed file could not be read


  * If you performed the procedure, report
 * the version of Microsoft Windows and the type of
   account used (administrator or standard user).


Windows 10 Home (Version 1511)
Administrator


 * report whether the procedure succeeded


Yes


 * if the procedure failed or met with difficulties,
   please summarize the problems and how you over-
   came any of them


To do a quick check, I've used a shortcut:

I've used the Total Commander (started as administrator, a normal user 
cannot modify anything in the OpenOffice directory) and exchanged the DLL.



  * [IMPORTANT] Identify any missing, incomplete or
confusing information in the README.  Describe what you
see as important improvements before making general
release of the procedure for use by non-expert users of
Apache OpenOffice on Windows.


Marcus

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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Wednesday, August 3, 2016 12:47
> To: d...@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Replies in line
> 
> Dennis E. Hamilton wrote:
> > Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
> >
> > The files to be used in testing are at
> > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/Windows>.
> >
> >  The files to be tested and reviewed are
> >
> > * README-4.1.2-patch1-apply-Windows.txt The description of the
> > procedure for applying a corrected library file to installed copies
> > of Apache OpenOffice 4.1.2 on Windows.  Read this first before
> > deciding to download the Zip file and attempting the procedure.
> >
> > * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip The Zip archive
> > containing the files to be used in the procedure.  There is a copy of
> > the README within the archive as well.
> >
> > * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc *
> > apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5 *
> > apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256 Files that
> > provide a digital signature, an MD5 hash, and an SHA256 hash that can
> > be used to verify the integrity of the download and, in the case of
> > the digital signature, the authenticity and accuracy of the download.
> >
> >
> > REQUESTED TESTING
> >
> > * [OPTIONAL] If you are able to check any of the .asc, .md5, and
> > .sha256 files against the .zip, report any difficulties that may have
> > been encountered.
> >
> [knmc]
> checked the zip against all of the signatures with the following
> results:
> .md5 matched
> .sha256 matched
> .asc failed with error not enough information to verify signature.
> 
[orcmid] 

Had you installed my PGP key (in the current KEYS file)?  
How did you download the .asc file?

[ ... ]
> >
> [knmc]
> In section 10 of the procedure section the line "Open the folder
> selected in step (7)" should read "Open the folder selected in step (8)"
> 
> On the whole I found the README difficult to follow with information out
> of sequence and extraneous information such as not accepting help from
> unsolicited phone calls. Not bad information, just out of place in a
> process document. Now that I have some available time I will get out my
> "blue pencil" and mark-up the document.
[orcmid] 

Note that someone has already spell-checked the document and I will do so in 
the future.

And all suggestions are welcome.

> 
> One improvement for the average user would be to automate the process
> with a .bat file that could find the proper folders and do the copy and
> rename procedures.
[orcmid] 

Oh duhh!

Yes, there is no reason a .bat file can't be included in the package.  With 
"Run as Administrator" that should also relieve the pain for folks on 
non-Administrator accounts who are able to provide/select administrator 
credentials.

I would leave the longer instructions, perhaps in an Appendix, for those who 
prefer the manual procedure or who otherwise have reservations/problems about 
running a script.

Something to work on over the next day or two while also gaining more results 
from the current testing.


> 
> > The goal is to provide as much as we can to assist Windows users in
> > applying this fix with confidence and success.  The experience of
> > more-knowledgable users who appreciate the difficulties of
> > non-experts is important in achieving that.
> >
> > Thank you for any effort you invest and the feedback you provide.
> >
> > - Dennis
> >
> >
> >
> >
> >
> >
> > -- Dennis E. Hamilton orc...@apache.org dennis.hamil...@acm.org
> > +1-206-779-9430 https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> > X.509 certs used and requested for signed e-mail
> >
> 
> 
> 



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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

Thank you, Pedro.

Thanks for the spell-checking too!  

Yes, the comment about quickstarter was misplaced and should go where there is 
mention of turning it off.

I did not notice the date change situation when I applied the procedure.  I 
think the date is preserved in the File Explorer listing. I will double-check 
the date business.

I also note that 

 * there are two list items (3) in the procedure.  That will be corrected.

 * the final location of the material is incorrect, and that will be repaired 
also.

 - Dennis

PS: The .odt attachment appears on the qa@ list mailings and that archive.  I 
think it may be good to create a bugzilla issue on this testing so anyone can 
post and also access attachments.  I will do that today.

> -Original Message-
> From: Pedro Lino [mailto:pedl...@gmail.com]
> Sent: Wednesday, August 3, 2016 09:08
> To: qa@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Hi all
> 
> 
> 
> 
>   REQUESTED TESTING
> 
>* [OPTIONAL] If you are able to check any of the .asc,
>  .md5, and .sha256 files against the .zip, report any
>  difficulties that may have been encountered.
> 
> 
> 
> ​Checked md5 and sha256. No problem.​ Assuming advanced users will be
> doing this, they probably have the tools to check. Such tool is not
> included in any program included in the Windows OS.
> 
> 
> 
> 
>* If you performed the procedure, report
>   * the version of Microsoft Windows and the type of
> account used (administrator or standard user).
>   * report whether the procedure succeeded
>   * if the procedure failed or met with difficulties,
> please summarize the problems and how you over-
> came any of them
> 
> 
> 
> ​Tested under Windows 7 x64 SP1 using an admin account. Procedure was
> successful. I would recommend to rename the file from dll.new to dll in
> the unzip folder (step​ 16) and _after_ that copy it to \OpenOffice
> 4\program\ (step 15)
> 
> This allows the file to retain the date. If the file is renamed after
> moving to \OpenOffice 4\program\ it will change date/time to the current
> date/time.(Obviously the Created date is not modified but from a user
> perspective that is not evident)
> 
> ​Following the​ same logic, it would be wiser to copy tl.dll.old to the
> patch folder (or any non-system folder) and if needed rename the file to
> tl.dll _before_ copying to \OpenOffice 4\program\ when reverting the
> patch.
> 
> 
> 
> 
>* [IMPORTANT] Identify any missing, incomplete or
>  confusing information in the README.  Describe what you
>  see as important improvements before making general
>  release of the procedure for use by non-expert users of
>  Apache OpenOffice on Windows.
> 
> 
> 
> ​There are some typos (and a confusing sentence) in the readme file.
> Please check the attached ODT (created with the patched AOO)​
> 
> Hope this helps,
> 
> Pedro



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

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Pedro Lino]

Hi all


> REQUESTED TESTING
>
>  * [OPTIONAL] If you are able to check any of the .asc,
>.md5, and .sha256 files against the .zip, report any
>difficulties that may have been encountered.
>

​Checked md5 and sha256. No problem.​ Assuming advanced users will be doing
this, they probably have the tools to check. Such tool is not included in
any program included in the Windows OS.


>
>  * If you performed the procedure, report
> * the version of Microsoft Windows and the type of
>   account used (administrator or standard user).
> * report whether the procedure succeeded
> * if the procedure failed or met with difficulties,
>   please summarize the problems and how you over-
>   came any of them
>

​Tested under Windows 7 x64 SP1 using an admin account. Procedure was
successful. I would recommend to rename the file from dll.new to dll in the
unzip folder (step​ 16) and _after_ that copy it to \OpenOffice 4\program\
(step 15)
This allows the file to retain the date. If the file is renamed after
moving to \OpenOffice 4\program\ it will change date/time to the current
date/time.(Obviously the Created date is not modified but from a user
perspective that is not evident)
​Following the​ same logic, it would be wiser to copy tl.dll.old to the
patch folder (or any non-system folder) and if needed rename the file to
tl.dll _before_ copying to \OpenOffice 4\program\ when reverting the patch.


>
>  * [IMPORTANT] Identify any missing, incomplete or
>confusing information in the README.  Describe what you
>see as important improvements before making general
>release of the procedure for use by non-expert users of
>Apache OpenOffice on Windows.
>

​There are some typos (and a confusing sentence) in the readme file. Please
check the attached ODT (created with the patched AOO)​

Hope this helps,
Pedro


README-4.1.2-patch1-apply-Windows.txt_RecordedChanges.odt
Description: application/vnd.oasis.opendocument.text

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