Hi all,
+1
From
https://dist.apache.org/repos/dist/dev/openoffice/4.1.4-RC5/binaries/ja/
I downloaded
Apache_OpenOffice_4.1.4_Win_x86_install_ja.exe and installed it on my
Windows 10 machine.
It works fine, no problem.
It was uninstalled ok.
From
Based on my own testing, I was about to cast a binding +1, but I'm going
to hold my vote until we know more about this.
On 10/14/2017 3:36 PM, Larry Gusaas wrote:
-1 (non binding)
Get general error message (macOS High Sierra) every time I open a
document. See separate post for details
-1 (non binding)
Get general error message (macOS High Sierra) every time I open a document. See separate post
for details
On 2017-10-13, 6:52 AM Jim Jagielski wrote:
Due to a last-minute regression noted in 4.1.4-RC4 (Thx! to
all testers, by the way. We are glad this was found before
we
-1 (non binding)
Get general error message (macOS High Sierra) every time I open a document. See separate post
for details
--
_
Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most
Hi Patricia
Am .10.2017, 23:42 Uhr, schrieb Patricia Shanahan :
On 10/14/2017 2:24 PM, Andrea Pescetti wrote:
Patricia Shanahan wrote:
On my Windows 10 machine, Spellcheck defaults to en-US spelling,
regardless of the language of the installation. I have tested this with
both
Every time I try to open a document with AOO 4.1.4 I get an error message (X on red circle,
General Error). When I click on the OK button the document opens. Happens every time I open a
document or a new document. Does not occur with AOO 4.1.3.
MacBook Pro 13" late 2013
macOS 10.13 High Sierra
Am 14.10.2017 um 22:39 schrieb Jim Jagielski:
All done.
great, thanks for the updates.
Marcus
On Oct 14, 2017, at 1:42 PM, Andrea Pescetti wrote:
Jim Jagielski wrote:
IMO, no need to redo the hash files. We can adjust the script
post-release to simply use basename,
On 10/14/2017 2:24 PM, Andrea Pescetti wrote:
Patricia Shanahan wrote:
On my Windows 10 machine, Spellcheck defaults to en-US spelling,
regardless of the language of the installation. I have tested this with
both fr and en-GB. (French and the two variants of English are the only
languages I
Patricia Shanahan wrote:
On my Windows 10 machine, Spellcheck defaults to en-US spelling,
regardless of the language of the installation. I have tested this with
both fr and en-GB. (French and the two variants of English are the only
languages I know well enough to test.) For each document, I
All done.
> On Oct 14, 2017, at 1:42 PM, Andrea Pescetti wrote:
>
> Jim Jagielski wrote:
>> IMO, no need to redo the hash files. We can adjust the script
>> post-release to simply use basename, or whatever we want.
>
> It's really a cosmetic issue, without any effects on
On my Windows 10 machine, Spellcheck defaults to en-US spelling,
regardless of the language of the installation. I have tested this with
both fr and en-GB. (French and the two variants of English are the only
languages I know well enough to test.) For each document, I have to
specify the
Peter Kovacs wrote:
D) does not explain the CD exclusion.
Just in case you are not aware of it, this is our policy for
redistribution, "selling on Ebay" included (allowed by our license).
https://www.openoffice.org/distribution/
In short, we require that people who "sell" OpenOffice
Jim Jagielski wrote:
IMO, no need to redo the hash files. We can adjust the script
post-release to simply use basename, or whatever we want.
It's really a cosmetic issue, without any effects on the ongoing vote,
but indeed the instructions we give to users assume that the .md5 and
.sha256
IMO, no need to redo the hash files. We can adjust the script
post-release to simply use basename, or whatever we want.
> On Oct 14, 2017, at 12:55 PM, Matthias Seidel
> wrote:
>
> If we do want to correct the files, wouldn't it be the easiest way to
> strip the
On 13/10/2017 Jim Jagielski wrote:
I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC5
as GA!!
+1 (binding)
I did the same tests as RC4, so:
- downloading and verifying the .bz2 sources (checksums, hashes)
- making sure these match with SVN: this worsened a bit in RC5 but it is
If we do want to correct the files, wouldn't it be the easiest way to
strip the relative paths and keep the hash?
I don't think we need completely new hash files...
The script itself can be updated for future use afterwards.
Matthias
Am 14.10.2017 um 18:09 schrieb Andrea Pescetti:
> Matthias
Am 13.10.2017 um 14:52 schrieb Jim Jagielski:
Due to a last-minute regression noted in 4.1.4-RC4 (Thx! to
all testers, by the way. We are glad this was found before
we actually released), 4.1.4-RC4 was revoked as GA.
But fear not!
I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC5
as
Matthias Seidel wrote:
Don't get me wrong:
This is exacty what I meant and therefore the issue is for Target
Release 4.2.0
OK! Then I simply got it wrong... we are on the same page, good.
Regards,
Andrea.
-
To unsubscribe,
+1 binding
Am 13.10.2017 um 14:52 schrieb Jim Jagielski:
> Due to a last-minute regression noted in 4.1.4-RC4 (Thx! to
> all testers, by the way. We are glad this was found before
> we actually released), 4.1.4-RC4 was revoked as GA.
>
> But fear not!
>
> I am calling a VOTE on releasing Apache
On Fri, Oct 13, 2017 at 5:52 AM, Jim Jagielski wrote:
> Due to a last-minute regression noted in 4.1.4-RC4 (Thx! to
> all testers, by the way. We are glad this was found before
> we actually released), 4.1.4-RC4 was revoked as GA.
>
> But fear not!
>
> I am calling a VOTE on
Am 14.10.2017 um 17:28 schrieb Jim Jagielski:
On Oct 14, 2017, at 11:28 AM, Jim Jagielski wrote:
I found the problem... It looked to be a cut/paste error where the
build system was looking in:
solver/420/unxmaccx.pro/xml/components
instead of:
-1 for Spalash screen
A) show time is not fixed.
B) splash is grafix no good to copy a link
C) maybe helpful for Windows, mac but is not for Linux.
D) does not explain the CD exclusion.
All the Best
Peter
Am 14. Oktober 2017 14:39:48 MESZ schrieb Marcus :
>Am 13.10.2017
Am 14.10.2017 um 15:39 schrieb Marcus:
> With hash files of previous versions is was easily possible to check
> the integrity of the download file with "sha256sum -c name>.sha256".
For Windows files I get:
sha256sum -c Apache_OpenOffice_4.1.4_Win_x86_install_de.exe.sha256
On 13/10/2017 Jörg Schmidt wrote:
Perhaps it would then be possible to explain the situation at Sourceforge at
the same time. Again and again, users are unsettled by the confusing structure
of Sourceforge's pages and the advertisements displayed there.
Is this still happening? I mean, there
> On Oct 14, 2017, at 11:28 AM, Jim Jagielski wrote:
>
> I found the problem... It looked to be a cut/paste error where the
> build system was looking in:
>
> solver/420/unxmaccx.pro/xml/components
>
> instead of:
>
> solver/420/unxmaccx.pro/xml/components
>
Oops.
I found the problem... It looked to be a cut/paste error where the
build system was looking in:
solver/420/unxmaccx.pro/xml/components
instead of:
solver/420/unxmaccx.pro/xml/components
It looks like a number of things in 4.2.0 related to
macOS haven't been tested/built yet so I'm running
On 13/10/2017 Jim Jagielski wrote:
I've gotten pretty far in building 4.2.0 but the below error is
a puzzler for me... Any ideas or hints would be appreciated.
It looks like a build dependency, somewhere
How many parallel jobs do you run?
I usually build "4x4", i.e.
$ build --all -P4 -- -P4
Am 14.10.2017 um 16:47 schrieb Matthias Seidel:
>
> I have absolutely no problem verifying the hashes with "gpg --verify
> filemane.asc". How about others?
> And why did nobody complain in RC1, RC2 and RC4?
Sorry, that was for verifying the signature... ;-)
Matthias
>
>>
Am 14.10.2017 um 16:40 schrieb Andrea Pescetti:
Matthias Seidel wrote:
While at it, we could also add support for SHA512. ;-)
https://bz.apache.org/ooo/show_bug.cgi?id=127530
Yes, but while at it we could also... just fix the SHA256 bug and be
happy with it.
Every time we add some other
Am 14.10.2017 um 16:40 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> While at it, we could also add support for SHA512. ;-)
>> https://bz.apache.org/ooo/show_bug.cgi?id=127530
>
> Yes, but while at it we could also... just fix the SHA256 bug and be
> happy with it.
>
> Every time we add
Matthias Seidel wrote:
While at it, we could also add support for SHA512. ;-)
https://bz.apache.org/ooo/show_bug.cgi?id=127530
Yes, but while at it we could also... just fix the SHA256 bug and be
happy with it.
Every time we add some other change "while at it", this has side effects
on the
Am 14.10.2017 um 16:09 schrieb Marcus:
> Am 14.10.2017 um 15:56 schrieb Matthias Seidel:
>> Am 14.10.2017 um 15:39 schrieb Marcus:
>>> With hash files of previous versions is was easily possible to check
>>> the integrity of the download file with "sha256sum -c >> name>.sha256".
>>>
>>> Now with
Am 14.10.2017 um 15:56 schrieb Matthias Seidel:
Am 14.10.2017 um 15:39 schrieb Marcus:
With hash files of previous versions is was easily possible to check
the integrity of the download file with "sha256sum -c .sha256".
Now with 4.1.4 a relative path was added before the file name in the
hash
> On Oct 14, 2017, at 9:56 AM, Matthias Seidel
> wrote:
>
> Am 14.10.2017 um 15:39 schrieb Marcus:
>> With hash files of previous versions is was easily possible to check
>> the integrity of the download file with "sha256sum -c > name>.sha256".
>>
>> Now with 4.1.4
Am 14.10.2017 um 15:39 schrieb Marcus:
> With hash files of previous versions is was easily possible to check
> the integrity of the download file with "sha256sum -c name>.sha256".
>
> Now with 4.1.4 a relative path was added before the file name in the
> hash files. Now it's a bit more
For the Windows files I used Jims hash-script [1], but the path there is
a bit different because I created them separately in every single
sub-directory.
[1]
http://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign.sh
Matthias
Am 14.10.2017 um 15:39 schrieb Marcus:
> With
Moin Jörg,
dann kann ich davon ausgehen, dass kommende Woche 4.1.4 rausgeht.
Gruß
Jan
-
To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-de-h...@openoffice.apache.org
With hash files of previous versions is was easily possible to check the
integrity of the download file with "sha256sum -c .sha256".
Now with 4.1.4 a relative path was added before the file name in the
hash files. Now it's a bit more complicated to get the same working. As
we are publishing
Am 13.10.2017 um 06:51 schrieb Jörg Schmidt:
From: Marcus [mailto:marcus.m...@wtnet.de]
I'm forwarding an idea from Andrea:
We can add a hint to the splash screen that OpenOffice is
open source,
free to download and where to download the official files.
This is a chance to remember our
Am 12.10.2017 um 22:48 schrieb Marcus:
I'm forwarding an idea from Andrea:
We can add a hint to the splash screen that OpenOffice is open source,
free to download and where to download the official files.
This is a chance to remember our users to download always from us and
not from other
>Do we have a bug # for this longstanding issue? We still advertise this
>feature but it is not working since 4.1.0 (?).
https://bz.apache.org/ooo/buglist.cgi?quicksearch=wikipublisher
But none specific to this problem
-
To
Am 13.10.2017 um 19:58 schrieb Jörg Schmidt:
> Hallo Michael,
> Das "Übliche" meinte keinen Verkauf, denn der hat auch in Vergangenheit nicht
> stattgefunden, sondern mit das "Übliche" meinte ich das noch niemals eine
> Standbesatzung irgendeine Verpflichtung auf Anwesenheit am Stand hatte
42 matches
Mail list logo