Hello,
> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Wednesday, November 11, 2020 12:34 AM
> To: dev@openoffice.apache.org
> Subject: [ANNOUNCE] Apache OpenOffice 4.1.8 released
>
> 10 November 2020 - Apache OpenOffice, the leading Open Source office
>
Hi Peter,
Currently cosv on pi.
I think I will start fresh - install what depends I can prior. or... if i can
fix cosv and start from there...
Will try again tonight.
- Original Message -
From: "Peter Kovacs"
To: dev@openoffice.apache.org
Sent: Sunday, November 8, 2020 3:43:06 AM
Dear OpenOffice Community,
A great big Thank You to everyone who has helped, tested, coded,
discussed or otherwise spent their precious time in making this release
possible !
We couldn't do this without you.
Please keep up the great work toward our next release!
Carl
(on behalf of the
CVE-2020-13958 Unrestricted actions leads to arbitrary code execution in
crafted documents
Fixed in Apache OpenOffice 4.1.8
Description
A vulnerability in Apache OpenOffice scripting events allows an attacker to
construct
documents containing hyperlinks pointing to an executable on the
10 November 2020 - Apache OpenOffice, the leading Open Source office
document productivity suite, announced today Apache OpenOffice 4.1.8,
now available in 41 languages on Windows, macOS and Linux.
Apache OpenOffice 4.1.8 is a maintenance release aimed at correcting
some regressions and
Damjan Jovanovic wrote:
AppImage and Snap packages would be the best, as those are multi-distro,
portable apps, do desktop integration, user friendly, standard
uninstallation, etc.
I'm singling this out as this is a different discussion, related to how
we package rather than how we build. I
Jim Jagielski wrote:
Cast your vote:
[X] CentOS7
[ ] Ubuntu 14.04
[ ] Something else:
CentOS 7 builds will run under Ubuntu 13.x too. While CentOS 7 32-bit
would be unsupported, the 64-bit version would receive maintenance until
2024; Ubuntu 14.04, instead, is already
Jim Jagielski wrote:
I am 100% still supportive of my original decision to baseline CentOS7 for the
4.2.x community builds. I see no reason to change that.
I fully agree. Building on CentOS 5 is extremely hard these times, and
one would have to replace the system SSL libraries just to
On 10 Nov, Jim Jagielski wrote:
> CentOS7: glibc 2.17
> Ubuntu 14.04: glibc 2.19
>
> Since CentOS7 emulates the "super stable" worldview of RHEL, the
> CentOS7 version will likely always be the older one.
In that case I think a Ubuntu build is unlikely to run on CentOS 7.
Hello,
we can't look only for 32 bit vs 64 bit versions for Linux.
We must also look for Java version 8 vs Java version 11.
So at this point we should start with a plttform which also support java 8
So this should discuss after releasing AOO version 4.1.8
I will give my Vote after evaluating
Am 10.11.20 um 19:23 schrieb Marcus:
Am 10.11.20 um 18:58 schrieb Jim Jagielski:
History: For previous AOO releases (up to 4.1.8), we have used
CentOS5 as our build environ for our community builds.
As of 4.2.x, this is no longer an option. Instead, we
baselined
CentOS7: glibc 2.17
Ubuntu 14.04: glibc 2.19
Since CentOS7 emulates the "super stable" worldview of RHEL, the CentOS7
version will likely always be the older one.
> On Nov 10, 2020, at 1:02 PM, Don Lewis wrote:
>
> On 10 Nov, Jim Jagielski wrote:
>> History: For previous AOO releases (up to
> On Nov 10, 2020, at 1:23 PM, Marcus wrote:
>
> Am 10.11.20 um 18:58 schrieb Jim Jagielski:
>> History: For previous AOO releases (up to 4.1.8), we have used
>> CentOS5 as our build environ for our community builds.
>> As of 4.2.x, this is no longer an option. Instead, we
Am 10.11.20 um 19:48 schrieb Melinda J.M.J.:
Hello, and good day. I am writing to inquire about which version, or which
version and plug-in, etc., I might be able to download to have Apache Open
Office on a new Amazon Kindle Fire HD8? Please, and Thank you. I am wishing
you health and
Hello, and good day. I am writing to inquire about which version, or which
version and plug-in, etc., I might be able to download to have Apache Open
Office on a new Amazon Kindle Fire HD8? Please, and Thank you. I am wishing
you health and wellness. Graciously,Melinda J.M.J. P.O. Box
On Tue, Nov 10, 2020 at 7:58 PM Jim Jagielski wrote:
> History: For previous AOO releases (up to 4.1.8), we have used
> CentOS5 as our build environ for our community builds.
> As of 4.2.x, this is no longer an option. Instead, we
> baselined CentOS7 (mainly due to
Am 10.11.20 um 18:58 schrieb Jim Jagielski:
History: For previous AOO releases (up to 4.1.8), we have used
CentOS5 as our build environ for our community builds.
As of 4.2.x, this is no longer an option. Instead, we
baselined CentOS7 (mainly due to gstreamer 1.0).
On 11/10/20 1:02 PM, Don Lewis wrote:
> On 10 Nov, Jim Jagielski wrote:
>> History: For previous AOO releases (up to 4.1.8), we have used
>> CentOS5 as our build environ for our community builds.
>> As of 4.2.x, this is no longer an option. Instead, we
>> baselined
On 10 Nov, Jim Jagielski wrote:
> History: For previous AOO releases (up to 4.1.8), we have used
> CentOS5 as our build environ for our community builds.
> As of 4.2.x, this is no longer an option. Instead, we
> baselined CentOS7 (mainly due to gstreamer 1.0).
>
>
> On Nov 10, 2020, at 12:58 PM, Jim Jagielski wrote:
>
> History: For previous AOO releases (up to 4.1.8), we have used
> CentOS5 as our build environ for our community builds.
> As of 4.2.x, this is no longer an option. Instead, we
> baselined CentOS7 (mainly due to
History: For previous AOO releases (up to 4.1.8), we have used
CentOS5 as our build environ for our community builds.
As of 4.2.x, this is no longer an option. Instead, we
baselined CentOS7 (mainly due to gstreamer 1.0).
Discussion: The issue w/ CentOS7 is that the
> On Nov 10, 2020, at 11:52 AM, Peter Kovacs wrote:
>
>
> Am 10.11.20 um 14:48 schrieb Jim Jagielski:
>> I think you may be confused... we are just talking about community builds
>> here, not anything regarding maintenance or modernizing AOO.
>
> I am not sure why you think I am confused. I
Am 10.11.20 um 14:48 schrieb Jim Jagielski:
I think you may be confused... we are just talking about community builds here,
not anything regarding maintenance or modernizing AOO.
I am not sure why you think I am confused. I just say that the AOO
report states we will not bring another
I think you may be confused... we are just talking about community builds here,
not anything regarding maintenance or modernizing AOO.
And, FTR, I can easily great 2 sets of Linux 32+64 builds: one set built on
CentOS5 w/ gstreamer 0.1 and the other on CentOS7 w/ gstreamer 1.0. Is it
"worth
I am against keeping 4.1.x alive once 4.2.0 is production ready. And
this strategy we have communicated.
Am 10.11.20 um 04:07 schrieb Jim Jagielski:
The only reason why we've decided to move to CentOS7 for our community builds is because
we build them w/ gstreamer, and only CentOS7 has
Hi Don,
Am 10.11.20 um 01:24 schrieb Don Lewis:
> For 4.2.0, we are talking about building on CentOS 7. Therefore some of
> platforms that we currently support won't support 4.2.0, in particular
> CentOS 5, which is currently EOL and CentOS 6, which is still supported
> upstream, at least for
26 matches
Mail list logo
