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.
- 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 .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
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org
