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

2016-08-12 Thread Keith N. McKenna

  
  
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 

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 
.

 - 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
.

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 

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

2016-08-12 Thread 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
>    patch1/binaries/Windows>
>  patch1/binaries/Windows> .
> 
>- Dennis
[ ... ]



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