+1 (binding)
On 12/18/2017 5:24 AM, Jim Jagielski wrote:
I am calling a VOTE on releasing Apache OpenOffice 4.1.5-RC1
as GA!!
You can find these gems at:
https://dist.apache.org/repos/dist/dev/openoffice/4.1.5-RC1/
The vote will last at least the normal 72 hours.
Cheers!
--
Jim
My solution is to do all file-changing svn operations, including
check-out, using the Cygwin command line svn, not TortoiseSVN.
On 12/8/2017 2:04 PM, Keith N. McKenna wrote:
For a number of reasons I am considering embarking into the wonderful
world of building AOO on Windows. In the section
If it turns out to only make things even more complicated, adding yet
another build tool, how hard would it be to remove it from trunk?
On 12/6/2017 6:10 PM, Damjan Jovanovic wrote:
...
Should we make a separate branch for SCons or develop in trunk? It doesn't
alter any existing files so it
and build a last production version and that will be voted on.
By this we have simple names, every one can follow, plus we do not break our
work process.
All the best
Peter
Am 3. Dezember 2017 18:40:23 MEZ schrieb Jim Jagielski <j...@jagunet.com>:
On Dec 3, 2017, at 10:06 AM, Patricia Shana
On 12/3/2017 6:50 AM, Marcus wrote:
Am 03.12.2017 um 11:11 schrieb Peter Kovacs:
I would put Beta into the Splash screen, but Release I would use RC
for for Release Candidate plus a number. So the first version would be
4.2.0RC1
If this does not break something of course.
I think this
(to create a 4.1.5) and
start keeping track there?
On Dec 1, 2017, at 8:18 AM, Patricia Shanahan <p...@acm.org> wrote:
Remember we also have the 4.1.5 branch, which is a lower risk solution to some
4.1.4 regressions.
I think it is time to decide whether to release it, and if so, what the
Remember we also have the 4.1.5 branch, which is a lower risk solution
to some 4.1.4 regressions.
I think it is time to decide whether to release it, and if so, what the
timing should be relative to the start of the 4.2 beta test. There is
something to be said for a single announcement so
The changes must not be committed as is, because that would undo some
comment translation. I have built a modified trunk and plan to test it
today. If all goes well I'll commit later today.
On 11/30/2017 7:38 AM, Jim Jagielski wrote:
Thx!
Looking over, I does appear to me that these need to
I would put it a bit more strongly. I think 4.1.x should be strictly
reserved for changes that are essential to fix urgent user-visible bugs.
On 11/30/2017 5:59 AM, Jim Jagielski wrote:
I think for 4.2.x and later, we have deprecated CentOS5 as a supported
build system... I ran into a LOT of
Thanks. I'll do a detailed analysis.
On 11/27/2017 7:44 PM, Don Lewis wrote:
When I diff the files that were changed for security reasons in 4.1.4
(this is actually 4.1.5 since I have a fresh checkout handy) vs. the
same files in trunk, and throw out all the diff chunks that solely
contain
On 11/27/2017 7:07 PM, Don Lewis wrote:
On 26 Nov, Patricia Shanahan wrote:
On 11/26/2017 4:47 PM, Don Lewis wrote:
On 27 Nov, Damjan Jovanovic wrote:
I can't reproduce it here, on trunk with:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown
On 11/26/2017 4:47 PM, Don Lewis wrote:
On 27 Nov, Damjan Jovanovic wrote:
I can't reproduce it here, on trunk with:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.3
with either our built-in HSQLDB driver or SQlite over ODBC.
What
it,
etc. Referencing 4.1.5 is about the same as referencing a "dev" build, but
additional info on how/why it got fixed would be helpful. Was it. Fixed on
trunk and then ported to 4.1.5 or ???
MzK
On Nov 25, 2017 05:51, "Patricia Shanahan" <p...@acm.org> wro
:
Yeah, I'll update the build instructions as needed.
On Nov 22, 2017, at 11:17 PM, Patricia Shanahan <p...@acm.org> wrote:
Do we need an update to the instructions to clarify that?
On 11/22/2017 12:34 PM, Jim Jagielski wrote:
I think I finally tracked down the problem w/ my Win7/cygwin
Should bugs be being marked "FIXED" based on the 4.1.5-dev build? We
have not yet committed to releasing it.
Forwarded Message
Subject: [Issue 127600] AOO 4.1.4 : Creating labels on more than One
page freezes application
Date: Sat, 25 Nov 2017 13:48:42 +
From:
On 11/24/2017 8:23 AM, Jim Jagielski wrote:
On Nov 23, 2017, at 6:06 PM, Larry Gusaas wrote:
There are serious regressions in 4.1.4 for Macs. The fix needs to be released
now, not wait until 4.2.0
And at least 1 fix that address all platforms as well, so I do
Do we need an update to the instructions to clarify that?
On 11/22/2017 12:34 PM, Jim Jagielski wrote:
I think I finally tracked down the problem w/ my Win7/cygwin
build problems. It was subtle.
I kept all my sources in
/home/jim/src/asf/AOO415
that is, it lived under the cygwin
I don't think we should wait for more development before releasing fixes
for the 4.1.4 regressions. If 4.2.0 needs another month or so of
development, I'm in favor of releasing 4.1.5 as soon as we can get the
various bug reports checked against it.
On a side note, for those living outside the
I see 4.1.5-dev as a device for testing whether a bug is due to a
specific problem. That change is already checked in to the trunk.
We still have to decide whether to go straight to 4.2.0. The upside is,
as Damjam points out, that we need to get the general benefits of 4.2
out in the field.
I agree. As soon as there is a Windows version of 4.1.5-dev I'll ask for
a test.
On 11/21/2017 7:35 AM, Dave Fisher wrote:
Hi Patricia,
This smells like a manifestation of the null link resource link you are fixing.
Regards,
Dave
Sent from my iPhone
Begin forwarded message:
From:
Thanks.
On 11/20/2017 3:42 PM, Matthias Seidel wrote:
I will start a build tomorrow in the evening...
Am 21.11.2017 um 00:37 schrieb Patricia Shanahan:
This should be tested on 4.1.5-dev. Is there going to be a Windows build?
Forwarded Message
Subject: [Issue 127601] New
This should be tested on 4.1.5-dev. Is there going to be a Windows build?
Forwarded Message
Subject: [Issue 127601] New: DDE Fields
Date: Mon, 20 Nov 2017 21:21:43 +
From: bugzi...@apache.org
Reply-To: iss...@openoffice.apache.org
To: iss...@openoffice.apache.org
Whether we will actually release a 4.1.5 is not yet decided. We do need
to do some testing with a version that only has a limited set of changes
relative to 4.1.4, so we are using the 4.1.5 branch for that purpose.
On 11/19/2017 7:38 PM, Dave Fisher wrote:
Isn’t the next version 4.1.5? Of
Now that I have a bit more time, I wanted to thank Jim for raising the
question. I really want people to review my code and question anything
that seems dubious.
On 11/19/2017 7:21 AM, Patricia Shanahan wrote:
The null check inside the mAutoAskUpdateAllLinks test is something of an
over
and hiding all exceptions. That means
data structures could be left in an inconsistent state without AOO
crashing or the access violation being reported, and almost any symptom
could result.
On 11/19/2017 7:21 AM, Patricia Shanahan wrote:
The null check inside the mAutoAskUpdateAllLinks test
(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
On Nov 18, 2017, at 3:49 PM, Patricia Shanahan <p...@acm.org> wrote:
I'm attaching the patch in case anyone else
I see you have checked in some Mac building changes. Would it be better
to keep the two fixes separate, or encourage testing both of them together?
On 11/18/2017 1:20 PM, Jim Jagielski wrote:
We do have the AOO415 branch! :)
On Nov 18, 2017, at 2:11 PM, Patricia Shanahan <p...@acm.org>
I'm attaching the patch in case anyone else wants to build their own
test version.
On 11/18/2017 11:11 AM, Patricia Shanahan wrote:
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being null, and it turns out it can be null :-(
The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer
Is it possible that this is another manifestation of
https://bz.apache.org/ooo/show_bug.cgi?id=127581
If so, it will not happen in the trunk.
On 11/17/2017 10:47 AM, Damjan Jovanovic wrote:
tl;dr:
Put a breakpoint on dbaui::DatabaseObjectView::doDispatch or
I've been waiting for the dust to settle. What is the best set of
instructions for doing a Windows 10 build with Cygwin 64?
On 11/15/2017 7:47 AM, Matthias Seidel wrote:
Hi Damjan,
I added 2 trailing "/" and now it works... ;-)
Maybe Patricia can confirm it?
I will now start a build from
anymore if my uild is
sane anymore.
Can I force the build process into a sequence build? Maybe that helps.
would that be -p1?
Thanks for any ideas.
all the best
Peter
On 12.11.2017 15:03, Patricia Shanahan wrote:
I sometimes get similar messages that go away if I just rerun the build.
I
I sometimes get similar messages that go away if I just rerun the build.
I think there may be some problem in whatever is supposed to ensure
dependencies are built before the things that depend on them.
On 11/12/2017 4:24 AM, Peter Kovacs wrote:
|
|
|My Compile setup:|
|| ./configure
I have a Windows 10 computer I do not currently use for builds. I'll
configure it with 64-bit Cygwin and JDK 8 and try this out.
On 11/10/2017 6:58 AM, Matthias Seidel wrote:
Hi Damjan,
Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic:
Hi
I've committed a few small small fixes to oowintool,
The more automated testing we can do, the better. I have a possible
patch for one of the regressions. What do I need to do to run the
"subsequent tests"?
On 11/9/2017 9:46 PM, Damjan Jovanovic wrote:
Hi
It seems to me that regressions that we've had with releases recently could
have been
to join.
Am 17. Oktober 2017 22:27:34 MESZ schrieb Andrea Pescetti <pesce...@apache.org>:
Patricia Shanahan wrote:
I am currently considering FOSDEM 2018, but is there a better choice?
No better choice. It is confirmed there will be a Devroom for Open
Document Editors (like OpenOffice) and th
There is something I've seen in the OpenOffice code that may be involved
in the silent failures to do something. For example,
main\xmloff\source\core\xmlexp.cxx, line 759:
catch( com::sun::star::uno::Exception& )
{
}
This will hide any and all
I do not know if this is the right choice, but we should include doing
both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as
soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up
the upgrade service.
On 10/31/2017 9:30 AM, Dave Fisher wrote:
There have been
I bow to empirical facts, but I am still confused. There are several xml
files in the .ods, most of which are written correctly. Why just the
ones under 'Object 1'?
On 10/31/2017 8:53 AM, Jim Jagielski wrote:
OK, I *think* I found it... it looks like it is a XML/xslt issue
where the 10.12
On 10/28/2017 12:11 PM, Andrea Pescetti wrote:
Dave Fisher wrote:
We ought to factor out the build tooling by comparing a build based on
4.1.3 with the bug to rule out a tooling regression.
Very good suggestion. Building 4.1.3 on exactly the same system and with
exactly the same config used
If aoo413 is built on the same tooling as aoo414 is it broken
too?
Regards,
Dave
On Oct 28, 2017, at 5:47 AM, Patricia Shanahan <p...@acm.org> wrote:
I at first thought this might be a load problem. It is now clear it is a case
of file corruption on save, only on Mac.
Unfortunately, tha
loading, not saving.
On 10/26/2017 5:45 AM, Jim Jagielski wrote:
Yeah, I kinda figured out what your hypothesis was... I'll need
to think about this some more.
On Oct 26, 2017, at 8:34 AM, Patricia Shanahan <p...@acm.org> wrote:
OK, forget that hypothesis. You have even done the next test I
Unless the changes are also in 4.1.4 or are super-urgent, I do not think
they belong in 4.1.5. 4.1.5, which we hope will never be released, is
for fixes to 4.1.4 that are too urgent to wait for 4.2.
On 10/27/2017 7:17 PM, Dave Fisher wrote:
Hi Damjan,
A friend is sending me a JDK7.
But I
OK, forget that hypothesis. You have even done the next test I would
have asked for if the line 288 breakpoint was not reached.
I'll need to think up a new hypothesis. I'm planning to go groom a
couple of horses this morning, but I'll work on this in the afternoon.
On 10/26/2017 5:01 AM, Jim
macOS *builds* is that 4.1.4 uses
'--with-alloc=system'
but the 4.1.3 build does not.
I will create a macOS build of AOO414 but adjust the configure script
to not include that and see what effect that may have.
On Oct 24, 2017, at 8:52 AM, Patricia Shanahan <p...@acm.org> wrote:
On 10/
On 10/24/2017 2:34 PM, Kay Schenk wrote:
On 10/24/2017 01:25 PM, Andrea Pescetti wrote:
I'm starting a short series of occasional posts to capture the current
collective state of mind on the next release. I'll float them here for
refinement or lazy consensus, and then we may want to reuse
On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan <p...@acm.org> wrote:
Since the issue appeared in 4.1.4, and involves document links, it might
be related to my changes.
I do not have a Mac, and do not have any Mac debug experience.
Since the issue appeared in 4.1.4, and involves document links, it might
be related to my changes.
I do not have a Mac, and do not have any Mac debug experience.
How do people think we should proceed with this? Is there a Mac
developer who can work with me on it?
On 10/24/2017 4:40 AM,
I like all this.
In addition, I would like to get set up to do code review. I don't like
the idea of changes going out to millions of users having only been
seriously examined by one programmer - even if I'm that programmer.
For both code review and testing, we need more active developers in
On 10/18/2017 5:35 PM, Dave Fisher wrote:
On Oct 18, 2017, at 4:45 PM, Pedro Lino wrote:
Maybe we need to ask for review of
http://www.apache.org/legal/release-policy.html#release-approval at the same
time as looking at the voting process documentation. If taken
In general, we are documenting our release process in
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release.
We have a problem that the ASF itself documents the rules for voting on
releases in two places:
http://www.apache.org/legal/release-policy.html#release-approval
On 10/18/2017 3:39 PM, Carl Marcum wrote:
On 10/18/2017 03:11 PM, Jim Jagielski wrote:
We expect PMC members to have a deep sense of responsibility
to their projects. When they cast a binding vote, we trust that
they have satisfied themselves enough to warrant them casting
the vote. That,
On 10/18/2017 12:28 PM, Pedro Lino wrote:
On 18/10/2017 19:02, Andrea Pescetti wrote:
This is OK as long as the Apache Policy doesn't get in the way too
much... I mean, I highly appreciate when people provide a list of what
they did to justify their +1. But this shouldn't be used "against"
On 10/17/2017 1:38 PM, Rory O'Farrell wrote:
On Tue, 17 Oct 2017 22:27:34 +0200
Andrea Pescetti <pesce...@apache.org> wrote:
Patricia Shanahan wrote:
I am currently considering FOSDEM 2018, but is there a better choice?
No better choice. It is confirmed there will be a Devroom fo
In my experience face-to-face meetings help smooth e-mail communication.
I live in California but many of the AOO developers seem to be based in
Europe, so my best chance of meeting some of you is to attend a European
open source conference.
I would like to decide at least a couple of months
Does this call for a change to
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Mac_OS_X
to prevent it in the future?
On 10/17/2017 12:09 PM, Andrea Pescetti wrote:
Matthias Seidel wrote:
(Later) I would be interested if your changes in the build process would
no changes to the files I used in my testing, so no need to retest.
On 10/16/2017 12:45 PM, Patricia Shanahan wrote:
-1, binding
The macOS problem seems to me to be sufficiently serious that we cannot
release RC5 with it. It has now been reported by two different users. I
may change my vote based
Yeah! What is the test and vote procedure from this point? I've checked
the commit messages, and none of the files I used in my testing have
changed, so I do not see any need to repeat it. On the other hand, we
need to allow time for Mac users to retest.
On 10/17/2017 8:52 AM, Jim Jagielski
Good catch!
Would it make sense to test with expat-2.2.4?
On 10/17/2017 3:48 AM, Jim Jagielski wrote:
Good news... I think.
For some reason, it does look like the expat patch is
the root cause, but for the life of me I can't grok
why. With the RC4 version of expat-2.2.3.patch, RC5
works on
-1, binding
The macOS problem seems to me to be sufficiently serious that we cannot
release RC5 with it. It has now been reported by two different users. I
may change my vote based on future information.
(If I were considering only my Windows 8.1 and Windows 10 testing, my
vote would be +1)
As a test, would it be possible for a Mac developer to rebuild with the
source code for RC5 but the process and libraries from RC4, and/or the
other way round? That will tell us whether the problem is a source code
change or a build process change.
On 10/16/2017 11:33 AM, Dave Fisher wrote:
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
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
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
On 10/10/2017 11:49 AM, Marcus wrote:
Am 10.10.2017 um 01:15 schrieb Andrea Pescetti:
Jim Jagielski wrote:
I was wondering... what do people think about going from 4.1.x all the
way straight to 4.5.0...
Since this next "major" release is pretty major, maybe a
bigger step in number might be
I hope you will stay on. I am not sure I would have made the same
decision as you about the release number, but in my opinion part of the
RM role is bike-shedding prevention by making decisions.
I hope that the need to test the patch ASAP does not get lost in the
discussion of what to call
onsidering this issue, this means that 4.1.4 is also DOA. I will wait for
a few more hours, for West Coast to get online but my plan is to
start the process for AOO-415
On Oct 10, 2017, at 8:16 AM, Patricia Shanahan <p...@acm.org> wrote:
The attached patch fixes this, as well as the business c
for AOO-415
On Oct 10, 2017, at 8:16 AM, Patricia Shanahan <p...@acm.org> wrote:
The attached patch fixes this, as well as the business card case.
On 10/10/2017 2:59 AM, Mathias Röllig wrote:
Hello!
Even on Linux.
Problem: linked sections will not be updated if the original section is c
rds, Mathias
Am 10.10.2017 um 11:10 schrieb Patricia Shanahan:
Thanks for the report.
I have reproduced the problem in my Windows 8.1 debug environment,
based on trunk but with some 4.1.4 changes added. I need to get some
more sleep before serious debug (it is 2:08 a.m. here). Could someone
ch
The equivalent of this patch for my debug environment does fix the
labels problem.
On 10/10/2017 3:28 AM, Patricia Shanahan wrote:
I have a theory for the Labels issue, and am in the process of building
to test it.
On an extremely experimental, untested, basis I am attaching a candidate
fix
section
5. Tools… → Update → Links
or Tools… → Update → Update All
=> Nothing happens. :-(
Regards, Mathias
Am 10.10.2017 um 11:10 schrieb Patricia Shanahan:
Thanks for the report.
I have reproduced the problem in my Windows 8.1 debug environment,
based on trunk but with some 4.1.4 changes added
Thanks for the report.
I have reproduced the problem in my Windows 8.1 debug environment, based
on trunk but with some 4.1.4 changes added. I need to get some more
sleep before serious debug (it is 2:08 a.m. here). Could someone check
whether it happens in the unmodified trunk? That would
On 10/4/2017 3:03 AM, Roberto Galoppini wrote:
...
I've just tried this on another Mac, with the very same operating system,
and it works.
I need to wait until later today to retry on the other machine, let's say
in 6 hours from now.
...
Given this, and the other reports of it working on Macs,
AM, Roberto Galoppini <roberto.galopp...@gmail.com
wrote:
I've re-downloaded again, it does not work. Does anyone else have tried
that? I'm really the only one facing problem with this build?
2017-10-03 15:04 GMT+02:00 Patricia Shanahan <p...@acm.org>:
Did you happen to check keys o
wrote:
I've re-downloaded again, it does not work. Does anyone else have tried
that? I'm really the only one facing problem with this build?
2017-10-03 15:04 GMT+02:00 Patricia Shanahan <p...@acm.org>:
Did you happen to check keys or do a sumcheck on the download? This is
sounding like it
t;j...@jagunet.com>:
How do you open it? Dbl-click the Icon? Select it and choose Open?
Alt-click Open?
On Oct 3, 2017, at 5:51 AM, Roberto Galoppini <
roberto.galopp...@gmail.com> wrote:
It never launched, actually. It crashes before anything else.
2017-10-03 11:24 GMT+02:00 Patricia
Do you do anything in particular, such as open some type of document,
before it crashes?
On 10/3/2017 12:28 AM, Roberto Galoppini wrote:
I was trying to test
Apache_OpenOffice_4.1.4_MacOS_x86-64_install_en-US.dmg but I couldn't, it
keeps crashing.
Best,
Roberto
+1 (binding)
On 9/30/2017 12:54 PM, Jim Jagielski wrote:
I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC4
as GA!!
You can find these gems at:
https://dist.apache.org/repos/dist/dev/openoffice/4.1.4-RC4/
The vote will last at least the normal 72 hours.
Cheers!
--
Jim Jagielski
I have completed the minimum testing I need to cast a binding +1 vote
for RC4, including successfully compiling and testing from the source
tarball as well as installing and testing a couple of binaries. I will,
of course, continue testing until the decision is made.
On 9/22/2017 10:51 AM,
23/09/2017 22:38, Patricia Shanahan wrote:
I installed the en-GB binary on a Windows 10 machine. Its spell
checker wants me to drop the "u" from "colour". Is there something
else I have to do to make it really en-GB?
On 9/22/2017 10:51 AM, Jim Jagielski wrote:
Avail
Tools - Language - For all Text - Reset to Default Language makes it
accept "colour". Shouldn't it start out in the default language on
installation?
On 9/23/2017 2:38 PM, Patricia Shanahan wrote:
I installed the en-GB binary on a Windows 10 machine. Its spell checker
wants me to d
I installed the en-GB binary on a Windows 10 machine. Its spell checker
wants me to drop the "u" from "colour". Is there something else I have
to do to make it really en-GB?
On 9/22/2017 10:51 AM, Jim Jagielski wrote:
Available for immediate testing are the source tarballs/zips and
community
That specific bug has already been tested. It is a symptom of the
unfortunate fact that what I don't know about the AOO source code can
hurt us, in the form of unexpected regressions.
The more different testing, the better. Linked files are the general
area that should be hit most, but any
On 9/17/2017 9:04 AM, Andrea Pescetti wrote:
On 14/09/2017 Dave Fisher wrote:
does SVN vs. GIT prevent new developers from volunteering?
I think this is the key question, even though there are many good points
also in what others replied.
We currently have a couple semi-official GIT
I would like to add one more condition: We should not move until the
process we will use has been applied successfully to smaller projects.
I am relatively neutral on the choice of repository, and a lot of people
seem to like Git.
On 9/14/2017 11:16 AM, Marcus wrote:
Even when I'm not a
I know Git is the repository-of-the-decade, and therefore a switch to it
is probably inevitable, just like the switch from RCS to SCCS and from
SCCS to Subversion.
Just as a matter of curiosity, which IDE's do not support Subversion? I
know I was using a it with Eclipse before I heard of Git.
On 9/5/2017 3:42 PM, Peter Kovacs wrote:
...
Can we make an OpenOffice meetup like last year?
I mean it was great to meet new people. If we announce this a little
then maybe more people come. Of course I would be happy to see those I
already have met again.
...
If there is an OpenOffice meetup
Would Opengrok be out of service during the "remove all branches" phase?
If so, for how long?
On 9/5/2017 3:04 PM, Peter Kovacs wrote:
Hi,
maybe it would be nice to have a small script that runs once a day that
just removes all branches and set them up which it finds.
It would remove the
this?
What did you do in the end?
Thanks the Information! :-D
Am Montag, den 28.08.2017, 12:18 -0700 schrieb Patricia Shanahan:
Looks interesting. An include I needed from sfx2 worked just fine,
so
I'll make sc look the same way in that file.
On 8/28/2017 12:12 PM, Peter Kovacs wrote:
sry
On 9/5/2017 7:11 AM, Peter Kovacs wrote:
Hello all,
To be honest I am not very happy with gmake and ant. It is difficult to
add the functionality to Eclipse. Also we stay dependant for Windows on
Cygwin or Windows Subsystem for Linux, which feels to me awkward. Also
if we want to have people
wrote:
Maybe Gregg could create a test document and send us a link?
I would be interested to test it on Windows and Ubuntu.
Also, as it happens in Writer it could be related to the other bug.
Regards, Matthias
Am 27.08.2017 um 12:35 schrieb Patricia Shanahan:
Thanks for this report. I am
/pch \
-I$(WORKDIR)/SdiTarget/sfx2/sdi \
-I$(WORKDIR)/inc/ \
$$(INCLUDE) \
-I$(OUTDIR)/inc/offuh \
-I$(OUTDIR)/inc \
$(LIBXML_CFLAGS) \
But maybe my understanding on including is wrong :-)
All the best
Peter
On 28.08.2017 19:41, Patricia Shanahan wrote:
I need to include
I need to include main/sc/inc/document.hxx in
main/sfx2/source/view/frmload.cxx. It is proving surprisingly difficult
- there seems to be some copying of header files???
Any suggestions? What should the include line look like? Do I need to
run configure and/or bootstrap again?
Thanks for this report. I am working on another bug so I can't get to it
immediately.
It would be helpful to get as much characterization as possible. Does it
happen on other operating systems? How many styles are necessary to
reproduce the bug?
On 8/26/2017 10:39 PM, Greg Madden wrote:
I have suggested a refactoring pass to make more use of STL structures
instead of fixed size, unchecked arrays. Some security problem would be
caught by array bounds checking.
We have some new volunteers over on the recruitment mailing list. I
think refactoring would be a good project for
at Adfinis SyGroup?
Thanks in advance for your help.
Marcus
Am 15.08.2017 um 19:46 schrieb Patricia Shanahan:
Opengrok, http://opengrok.adfinis-sygroup.org/source/, times out.
This makes it very unlikely I will be able to solve the RC2 OLE problem
before I go out of town for a few days starting
Opengrok, http://opengrok.adfinis-sygroup.org/source/, times out.
This makes it very unlikely I will be able to solve the RC2 OLE problem
before I go out of town for a few days starting on Thursday. I can use
find and grep instead, but it takes a lot longer.
I am rebuilding my 4.1.4 debug environment to make sure it is up to
date. I am going to work on this ASAP, but I do have travel planned and
will not be available Thursday through Tuesday.
On 8/14/2017 1:35 PM, Matthias Seidel wrote:
Well, not exactly the same...
If I zoom into the document I
Have you tried repeating "build --all" a few times?
I quite often have failures that go away with a few repeated builds. My
interpretation is that whatever is supposed to make sure all
dependencies are satisfied before building a module does not quite work
right. Sooner or later, everything
One of the changes for 4.1.4 is supposed to tighten validation of doc
files. Unfortunately, I made a mistake in the version that went into
RC1, and it gets false positives.
The problem should be fixed in RC2.
On 8/10/2017 4:27 AM, Rory O'Farrell wrote:
Forum volunteer John_Ha has sent me a
101 - 200 of 630 matches
Mail list logo