On 9/19/2016 9:20 AM, Pedro Giffuni wrote:
...
Given this is already late you should probably reconsider bringing in
some fixes to known bugs. If the idea is just that 4.1.3 = 4.1.2 +
CVE-2016-15-13, then it seems to be a huge waste of bandwidth for both
mirrors and end users.
All just IMHO,
..
I installed the german DEB on Ubuntu 16.04.1 (64bit)
So far everything is working as expected...
regards
Matthias
Am 21.09.2016 um 01:04 schrieb Andrea Pescetti:
> On 17/09/2016 Mechtilde wrote:
>> Am 17.09.2016 um 07:25 schrieb Mechtilde:
>>> is there a first "nightly build for version 4.1.3
I am quite sure it was Rob Weir who managed it.
As for the AOO-community
(https://plus.google.com/u/0/communities/103683488250592271079) there
are some members listed as "Moderator" who still should have
access/rights to the profile. Some of them might be still active.
regards
Matthias
Am 20.0
I believe I have done all the preliminary steps. configure appeared to
work, but I have a persistent bootstrap failure:
...
all external libraries present
downloading dmake-4.12.tar.bz2
downloading to C:/OpenOfficeDev/AOO413/ext_sources/dmake-4.12.tar.bz2.part
download from
http://dmake.apache-
I missed a couple of configure parameter changes I need.
On 9/21/2016 10:03 AM, Patricia Shanahan wrote:
I believe I have done all the preliminary steps. configure appeared to
work, but I have a persistent bootstrap failure:
...
all external libraries present
downloading dmake-4.12.tar.bz2
down
I use this URL for successfully downloading dmake:
http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2
HTH
Marcus
Am 09/21/2016 07:26 PM, schrieb Patricia Shanahan:
I missed a couple of configure parameter changes I need.
On 9/21/2016 10:03 AM, Patricia Shanahan wrote
Pedro has asked for 4.1.3_release_blocker:
Issue 127127: English dictionary included in 4.1.3 installer is outdated
https://bz.apache.org/ooo/show_bug.cgi?id=127127
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
How would granting 4.1.3_release_blocker on this impact progress on the
builds?
Forwarded Message
Subject: 4.1.3_release_blocker requested: [Issue 127127] English
dictionary included in 4.1.3 installer is outdated
Date: Wed, 21 Sep 2016 18:37:17 +
From: bugzi...@apache.o
Where is this documented? I can see the ./configure line in
the puppet files but we should also have this on a wiki someplace,
right?
> On Sep 19, 2016, at 2:08 PM, Marcus wrote:
>
> I remember that old times at Sun where we have done builds with more than
> just en-US.
>
> In order to cover p
I'll set one up in the next day.
> On Sep 20, 2016, at 6:25 PM, Andrea Pescetti wrote:
>
> On 19/09/2016 Jim Jagielski wrote:
>> If useful, I can replace my 64bit CentOS5 vm with a 32bit one.
>
> It would be useful (to have more coverage) to test
> https://wiki.openoffice.org/wiki/Documentation
Am 09/21/2016 09:41 PM, schrieb Jim Jagielski:
Where is this documented? I can see the ./configure line in
the puppet files but we should also have this on a wiki someplace,
right?
Gav has created a wikipage for the new buildbot setup:
https://cwiki.apache.org/confluence/display/OOOUSERS/Build
Patricia Shanahan wrote:
How would granting 4.1.3_release_blocker on this impact progress on the
builds?
It wouldn't have had a major impact, but in this case (as later
clarified in the issue) the blocker request is simply a misunderstanding.
As a general rule, we first apply fixes on trunk
Am 09/21/2016 10:17 PM, schrieb Andrea Pescetti:
Patricia Shanahan wrote:
How would granting 4.1.3_release_blocker on this impact progress on the
builds?
It wouldn't have had a major impact, but in this case (as later
clarified in the issue) the blocker request is simply a misunderstanding.
Ariel Constenla-Haile wrote:
On Wed, Sep 21, 2016 at 12:10:29AM +0200, Andrea Pescetti wrote:
(the way it is now; I haven't checked
https://bz.apache.org/ooo/show_bug.cgi?id=127120 yet) it uses only packages
from CentOS and EPEL repositories, plus custom Ant and Perl as the versions
shipping wit
1. My current policy for release blocker is to grant it immediately if
it seems obvious to me that a fix is needed to build 4.1.3. I will also
do so based on prior security@ discussion. Otherwise, I'll ask for input
on dev@ before deciding.
2. I would like to get a list of environments in whic
Patricia Shanahan wrote:
1. My current policy for release blocker is to grant it immediately if
it seems obvious to me that a fix is needed to build 4.1.3. I will also
do so based on prior security@ discussion. Otherwise, I'll ask for input
on dev@ before deciding.
OK. 4.1.4 is a good fallback
16 matches
Mail list logo
