Nevermind, Microsoft just published my submission.
Let's call it luck!
Matthias
Am 05.05.22 um 14:42 schrieb Matthias Seidel:
> Really?!
>
> This breaks every download from the Microsoft Store now until the new
> submission is published...
>
> This is clearly documented in the Release Schedule!
Really?!
This breaks every download from the Microsoft Store now until the new
submission is published...
This is clearly documented in the Release Schedule! Please revert.
Matthias
Am 05.05.22 um 14:29 schrieb j...@apache.org:
> Author: jim
> Date: Thu May 5 12:29:49 2022
> New Revision: 5428
Ah, I see they are "branded" as "Test Development Builds"... ;-)
Just installed it on macOS Catalina with the latest AdoptOpenJDK 11.
Am 06.08.21 um 22:16 schrieb Jim Jagielski:
> I am uploading both the regular and the ./Dev/ builds... just in case there
> is something in the Dev builds themsel
I am uploading both the regular and the ./Dev/ builds... just in case there is
something in the Dev builds themselves which causes issues
> On Aug 6, 2021, at 3:44 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Sorry, these are NOT Dev builds, compare to Dev2:
>
> https://dist.apache.org/repos
Hi Jim,
Sorry, these are NOT Dev builds, compare to Dev2:
https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev2/binaries/en-US/
Regards,
Matthias
Am 06.08.21 um 21:36 schrieb j...@apache.org:
> Author: jim
> Date: Fri Aug 6 19:36:48 2021
> New Revision: 49231
>
> Log:
> AOO 4.2.0-De
Hello all,
On Thu, Jun 17, 2021 at 02:54:26AM +0200, Damjan Jovanovic wrote:
> On Thu, Jun 17, 2021 at 1:34 AM Don Lewis wrote:
>
> > On 16 Jun, ard...@apache.org wrote:
> > > Author: ardovm
> > > Date: Wed Jun 16 19:07:44 2021
> > > New Revision: 1890844
> > >
> > > URL: http://svn.apache.org/
On Thu, Jun 17, 2021 at 1:34 AM Don Lewis wrote:
> On 16 Jun, ard...@apache.org wrote:
> > Author: ardovm
> > Date: Wed Jun 16 19:07:44 2021
> > New Revision: 1890844
> >
> > URL: http://svn.apache.org/viewvc?rev=1890844&view=rev
> > Log:
> > Build script for AOO 4.1.10 under Mingw
> >
> > Better
On 16 Jun, ard...@apache.org wrote:
> Author: ardovm
> Date: Wed Jun 16 19:07:44 2021
> New Revision: 1890844
>
> URL: http://svn.apache.org/viewvc?rev=1890844&view=rev
> Log:
> Build script for AOO 4.1.10 under Mingw
>
> Better late than never... could be used as a template for the future
I tho
Hi -
I’m about to pull the trigger on completing the CMS migration.
Are you planning on making changes on GitHub too?
Regards,
Dave
Sent from my iPhone
> On Nov 18, 2020, at 8:09 AM, msei...@apache.org wrote:
>
> Author: mseidel
> Date: Wed Nov 18 16:09:05 2020
> New Revision: 1068165
>
> L
Yes, no problem.
Any idea how long it will last until we switch? The layout is not 100%
identical for openoffice.org.
Matthias
Am 14.11.20 um 23:26 schrieb Dave Fisher:
> Would you please make the same changes in the new location.
>
> Sent from my iPhone
>
>> On Nov 14, 2020, at 9:50 AM, msei...
Would you please make the same changes in the new location.
Sent from my iPhone
> On Nov 14, 2020, at 9:50 AM, msei...@apache.org wrote:
>
> Author: mseidel
> Date: Sat Nov 14 17:50:04 2020
> New Revision: 1883427
>
> URL: http://svn.apache.org/viewvc?rev=1883427&view=rev
> Log:
> Use Italian
Hi Aivaras,
/"2020 m. spalio 15 d."/
/Is this right?/
/We released on November 10th.
/
//Regards,//
// Matthias
//
Am 11.11.20 um 15:23 schrieb astepuko...@apache.org:
> Author: astepukonis
> Date: Wed Nov 11 14:23:06 2020
> New Revision: 1883306
>
> URL: http://svn.apache.org/viewvc?rev=18
Hi Dave,
On 10/19/20 4:44 PM, Dave Fisher wrote:
Hi -
I added more analysis in README.txt
New is FRAMEWORKS.txt which has some notes about Pelican, JBake, Hugo, and
Jekyll frameworks.
So, far JBake is the most promising.
If anyone has another framework to consider let me know.
I’ll be taki
Hi -
I added more analysis in README.txt
New is FRAMEWORKS.txt which has some notes about Pelican, JBake, Hugo, and
Jekyll frameworks.
So, far JBake is the most promising.
If anyone has another framework to consider let me know.
I’ll be taking my next steps on Wednesday.
Regards,
Dave
> On
Hi -
After discussing the CMS migration of the OpenOffice.org site on the
anniversary call yesterday with Carl I created a README.txt and ssi.json files
to start the process towards a description that can be easier to fit into
whatever new framework we choose.
The next step will be to look int
Hi Andrea,
Am 15.08.19 um 08:30 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> Shouldn't SVN be read-only now?!
>> This will introduce some inconsistencies to Git now...
>
> If it is writable, please do not fix it!
>
> We definitely need some README there (in trunk) that points to the new
>
Matthias Seidel wrote:
Shouldn't SVN be read-only now?!
This will introduce some inconsistencies to Git now...
If it is writable, please do not fix it!
We definitely need some README there (in trunk) that points to the new
repository URL, and a last commit message for it saying "Point to the
Personally, I think migrating from svn to git while in the midst of also trying
to cut a release was somewhat unwise... As far as SVN being read only,
obviously I was able to commit to the AOO417 branch. So I've no idea what the
status is... I was just as surprised, but since my entire macOS (an
On Wed, Aug 14, 2019 at 8:37 AM Andrea Pescetti wrote:
> On 13/08/2019 Kay Schenk wrote:
> > The page name from the current project website repository is --
> > source_new.mdtext as you probably saw.
>
> There is no need to be shy here... we have version control and we can
> just update source.md
Shouldn't SVN be read-only now?!
This will introduce some inconsistencies to Git now...
Matthias
Am 14.08.19 um 17:51 schrieb j...@apache.org:
> Author: jim
> Date: Wed Aug 14 15:51:11 2019
> New Revision: 1865164
>
> URL: http://svn.apache.org/viewvc?rev=1865164&view=rev
> Log:
> Align w/ 42X a
On 13/08/2019 Kay Schenk wrote:
The page name from the current project website repository is --
source_new.mdtext as you probably saw.
There is no need to be shy here... we have version control and we can
just update source.mdtext. I've moved your source_new.mdtext to be the
new version of so
Hi Kay,
Am 13.08.19 um 22:56 schrieb Kay Schenk:
> Hi Matthias --
> The page name from the current project website repository is --
> source_new.mdtext
> as you probably saw.
> I really know VERY little about git but I will try to do some editing and
> hope others will do a lot more. ☺
Yes, let's
Hi Matthias --
The page name from the current project website repository is --
source_new.mdtext
as you probably saw.
I really know VERY little about git but I will try to do some editing and
hope others will do a lot more. ☺
-- Kay
On Tue, Aug 13, 2019 at 1:25 PM Matthias Seidel
wrote:
> Thank
Thanks Kay,
I already got notified via commits@ ;-)
Do you plan to publish that page later? It is indeed one, that needs to
be updated due to the Git switch.
Regards,
Matthias
Am 13.08.19 um 21:43 schrieb Kay Schenk:
> As an FYI, I was able to add and commit a new page to the project web si
As an FYI, I was able to add and commit a new page to the project web site
--
https://openoffice.apache.org/
to verify that svn is still OK there also.
On Tue, Aug 13, 2019 at 2:48 AM Matthias Seidel
wrote:
> Hi all,
>
> Totally forgot to say that I was able to commit to that directory early
Hi all,
Totally forgot to say that I was able to commit to that directory early
this morning.
I have not checked other directories yet.
Thank you Peter for the talk on Slack #asfinfra.
(We really should use this more for quick communication)
Regards,
Matthias
Am 13.08.19 um 00:37 schrieb M
Am 13.08.19 um 00:28 schrieb Peter Kovacs:
Infra Chat Log from on slack ( for documentation reasons):
petko 23:44 Uhr
Hello, is SVN path
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/
readonly? (edited)
warwalrux 23:54 Uhr
I believe it's readonly to all but members of the openo
Infra Chat Log from on slack ( for documentation reasons):
petko 23:44 Uhr
Hello, is SVN path
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/
readonly? (edited)
warwalrux 23:54 Uhr
I believe it's readonly to all but members of the openoffice group.
(edited)
Gavin McDonald 23:58 U
Hi Andrea,
Am 13.08.19 um 00:05 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
>> read-only now?
>> Can anyone confirm?
>
> Confirmed. I tried adding an empty "aoo417" directory and commit was
> rejected. Transcript below.
Matthias Seidel wrote:
https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
read-only now?
Can anyone confirm?
Confirmed. I tried adding an empty "aoo417" directory and commit was
rejected. Transcript below.
$ svn mkdir aoo417
A aoo417
$ svn ci -m "Empty dir for 4.1.
Infra confirms. I ask now what they need to fix it.
On 13.08.19 00:00, Marcus wrote:
> Am 12.08.19 um 23:39 schrieb Matthias Seidel:
>> https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
>> read-only now?
>>
>> Can anyone confirm?
>
> yes, I cannot send a commit as access is den
Am 12.08.19 um 23:39 schrieb Matthias Seidel:
https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
read-only now?
Can anyone confirm?
yes, I cannot send a commit as access is denied.
Marcus
-
To unsubscribe
Am 02.04.19 um 19:01 schrieb Damjan Jovanovic:
> On Tue, Apr 2, 2019 at 3:24 PM Matthias Seidel
> wrote:
>
>> Hi Damjan,
>>
>> Just for clarification, these tests are done automatically while
>> building unless I disable them explicitly with --disable-unit-tests?
>>
>> Regards,
>>
>>Matthias
>
On Tue, Apr 2, 2019 at 3:24 PM Matthias Seidel
wrote:
> Hi Damjan,
>
> Just for clarification, these tests are done automatically while
> building unless I disable them explicitly with --disable-unit-tests?
>
> Regards,
>
>Matthias
>
>
That's right.
Regards
Damjan
Hi Damjan,
Just for clarification, these tests are done automatically while
building unless I disable them explicitly with --disable-unit-tests?
Regards,
Matthias
Am 31.03.19 um 20:17 schrieb dam...@apache.org:
> Author: damjan
> Date: Sun Mar 31 18:17:42 2019
> New Revision: 1856677
>
> URL
Hi Andrea
> On March 31, 2019 at 10:43 PM Andrea Pescetti wrote:
> In the last command the user is actually supposed to install only the
> relevant package. Contents of this directory vary, so it might be that
> in some circumstances you only find one package there. But the generic
> rule is t
On 29/03/2019 Pedro Lino wrote:
I would like to ask if there is a reason why there is a desktop integration
folder?
We do have several possible desktop integrations (GNOME, KDE, etc), see
the RPM Linux64 packages for example.
This currently forces the Linux user to run 3 commands
sudo dpkg
> On March 29, 2019 at 1:39 PM Stehmann < o...@mechtilde.de
> mailto:o...@mechtilde.de > wrote:
>
>
> IMO for installing several versions of AOO it is better to have it in
> different directories
>
Ok that is a valid argument.
But this is making things more complicated for all just to
IMO for installing several versions of AOO it is better to have it in
different directories
Mechtilde
Am 29. März 2019 10:55:11 MEZ schrieb Pedro Lino :
>
>> On March 29, 2019 at 9:51 AM Stehmann < o...@mechtilde.de
>mailto:o...@mechtilde.de > wrote:
>>
>>
>> This was the behaviour si
> On March 29, 2019 at 9:51 AM Stehmann < o...@mechtilde.de
> mailto:o...@mechtilde.de > wrote:
>
>
> This was the behaviour since the begining of OpenOffice.org
>
Yes, I understand that.
But is there any limitation to having all the files in the same folder?
Can this be improved?
>
This was the behaviour since the begining of OpenOffice.org
Mechtilde
Am 29. März 2019 10:42:22 MEZ schrieb Pedro Lino :
>I would like to ask if there is a reason why there is a desktop
>integration folder?
>
>This currently forces the Linux user to run 3 commands
>sudo dpkg -i *.deb
>cd deskt
I would like to ask if there is a reason why there is a desktop integration
folder?
This currently forces the Linux user to run 3 commands
sudo dpkg -i *.deb
cd desktop-integration
sudo dpkg -i *.deb
In the downstream project the contents of the desktop-integration folder has
been moved to the
Am 28.03.19 um 22:09 schrieb Jim Jagielski:
> Do you see anything obvious in the config log for my build?
Indeed it seems to be in:
http://svn.apache.org/repos/asf/openoffice/tags/AOO420-Dev-m1/main/instsetoo_native/util/openoffice.lst
The "include" line for Apache_OpenOffice_Dev doesn't contain
Hi Rory,
Am 28.03.19 um 22:27 schrieb Rory O'Farrell:
> On Thu, 28 Mar 2019 21:18:02 +
> Rory O'Farrell wrote:
>
>> On Thu, 28 Mar 2019 22:01:26 +0100
>> Matthias Seidel wrote:
>>
>>> Hi Jim,
>>>
>>> I just installed the German version on Xubuntu 64-bit.
>>> Works great so far, but the deskt
Am 28.03.19 um 22:09 schrieb Jim Jagielski:
> Do you see anything obvious in the config log for my build?
No, I thought more of the build process, not your build in special.
Maybe desktop integration was never planned for Dev? We might check if
my recent changes to "openoffice.lst" are the cause.
On Thu, 28 Mar 2019 21:18:02 +
Rory O'Farrell wrote:
> On Thu, 28 Mar 2019 22:01:26 +0100
> Matthias Seidel wrote:
>
> > Hi Jim,
> >
> > I just installed the German version on Xubuntu 64-bit.
> > Works great so far, but the desktop integration is missing. I don't know
> > if this is intent
On Thu, 28 Mar 2019 22:01:26 +0100
Matthias Seidel wrote:
> Hi Jim,
>
> I just installed the German version on Xubuntu 64-bit.
> Works great so far, but the desktop integration is missing. I don't know
> if this is intentional or a build problem.
>
> That might not be a big issue but we should
Do you see anything obvious in the config log for my build?
> On Mar 28, 2019, at 5:01 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> I just installed the German version on Xubuntu 64-bit.
> Works great so far, but the desktop integration is missing. I don't know
> if this is intentional or a bu
Hi Jim,
I just installed the German version on Xubuntu 64-bit.
Works great so far, but the desktop integration is missing. I don't know
if this is intentional or a build problem.
That might not be a big issue but we should discuss it. And we should
point that out in our (planned) blogpost.
Regar
That's great :)
Well done!
On Thu, Feb 21, 2019 at 6:35 PM Jim Jagielski wrote:
> Resolved in r 1854065
Resolved in r 1854065
Here is the attempted build w/ --verbose
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
OK, actually it looks like there's nothing being compiled...
=
Building module apple_remote
=
Entering /Users/jim/src/asf/trunk/main/apple_remote/prj
cd .. && make -s -r -j6 && make -s -r deliverlog
[ info ALL ] LinkTarget Library/libc++.dylib not defined: Assuming hea
Unfortunately, no difference :
nm -a solver/450/unxmaccx.pro/lib/libAppleRemote.dylib
U dyld_stub_binder
% svn diff
Index: apple_remote/inc/AppleRemote.h
===
--- apple_remote/inc/AppleRemote.h (revision 1853980)
Looks like a lot of symbols may need exporting.
For starters, try the following:
In apple_remote/inc/AppleRemote.h,
change:
@interface AppleRemote : HIDRemoteControlDevice {
to:
@interface SAL_DLLPUBLIC_EXPORT AppleRemote : HIDRemoteControlDevice {
You may also need:
#include
See if you get thi
In both cases (using trunk and AOO42X) I get:
nm -D solver/450/unxmaccx.pro/lib/*AppleRe*
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/nm:
solver/450/unxmaccx.pro/lib/libAppleRemote.dylib: File format has no dynamic
symbol table.
/Applications/Xcode.app/
I wonder if the problem is that gbuild's default symbol visibility is
hidden, unlike dmake's which was public.
Can you post the output of:
nm -D solver/450//lib/*AppleRemote.dylib | grep ' T '
and compare against the same from any version before the gbuild commit?
In C/C++ we have to mark functio
The patch is applied (as well as some other changes) and apple_remote builds,
but it looks like even though it builds, some linking issues are still there:
[ build RES ] vclen-GB
Undefined symbols for architecture x86_64:
"_OBJC_CLASS_$_AppleRemoteMainController", referenced from:
objc-cl
Yes, changes to gbuild itself are largely made by experimentation. It's
beyond anyone's complete understanding.
Please try this patch, with the file extensions back on *.m.
On Tue, Feb 19, 2019 at 10:39 PM Jim Jagielski wrote:
>
>
> > On Feb 19, 2019, at 12:05 PM, Damjan Jovanovic
> wrote:
> >
I got curious about this module name, Apple_Remote, and here's what the
OpenOffice Wiki has to say...
https://wiki.openoffice.org/wiki/Mac_OS_X_Porting_-_Apple_Remote_implementation
So, is this a module that's actually in use anymore?
I do realize this is a module that has been able to build i
> On Feb 19, 2019, at 12:29 PM, Jim Jagielski wrote:
>
>
>
>> On Feb 19, 2019, at 12:05 PM, Damjan Jovanovic wrote:
>>
>> If
>> not, I'll have to make a gb_Library_add_objcobjects API instead.
>
> If I knew how, I'd do it. Looking over the add_objcxxobjects stuff it seems
> like a maze o
> On Feb 19, 2019, at 12:05 PM, Damjan Jovanovic wrote:
>
> If
> not, I'll have to make a gb_Library_add_objcobjects API instead.
If I knew how, I'd do it. Looking over the add_objcxxobjects stuff it seems
like a maze of twisty little passages
---
Well, making the change got be building, but w/ fatal errors:
=
Building module apple_remote
=
Entering /Users/jim/src/asf/trunk/main/apple_remote/prj
cd .. && make -s -r -j6 && make -s -r deliverlog
[ build OCX ] apple_remote/source/AppleRemote
[ build OCX ] apple_remo
I think .m files are Objective C, and gb_Library_add_objcxxobjects wants
Objective C++'s .mm.
I am completely unfamiliar with both languages.
Please try renaming apple_remote/source/*.m to *.mm and see if it works? If
not, I'll have to make a gb_Library_add_objcobjects API instead.
On Tue, Feb
Nope... that wasn't it. Even with a complete fresh-from-scratch build, I get
the same error.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Disregard this for now... I think it was a build error due to not fully
cleaning the apple_remote subdir
> On Feb 19, 2019, at 9:25 AM, Jim Jagielski wrote:
>
> =
> Building module apple_remote
> =
>
> Entering /Users/jim/src/asf/trunk/main/apple_remote/prj
>
> cd .. &
=
Building module apple_remote
=
Entering /Users/jim/src/asf/trunk/main/apple_remote/prj
cd .. && make -s -r -j6 && make -s -r deliverlog
[ info ALL ] LinkTarget Library/libc++.dylib not defined: Assuming headers to
be there!
[ build PKG ] apple_remote_inc
[ build DEP
That one looks really subtle ;)
> On Feb 12, 2019, at 10:35 AM, j...@apache.org wrote:
>
> Author: jim
> Date: Tue Feb 12 18:35:43 2019
> New Revision: 1853466
>
> URL: http://svn.apache.org/viewvc?rev=1853466&view=rev
> Log:
> balance parens here in ifeq
>
> Modified:
>openoffice/trunk/mai
Hi Jim,
Am 16.01.19 um 22:36 schrieb Jim Jagielski:
> I just picked a number that was big... maybe just use 1 ? :)
1 worked, AOO4.5.0 Windows builds are now installable...
Regards,
Matthias
>
>> On Jan 16, 2019, at 3:58 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> Am 09.01.1
Am 16.01.19 um 22:36 schrieb Jim Jagielski:
> I just picked a number that was big... maybe just use 1 ? :)
I will try with 1 for my next build...
>
>> On Jan 16, 2019, at 3:58 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> Am 09.01.19 um 20:40 schrieb j...@apache.org:
>>> Author: jim
>
I just picked a number that was big... maybe just use 1 ? :)
> On Jan 16, 2019, at 3:58 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 09.01.19 um 20:40 schrieb j...@apache.org:
>> Author: jim
>> Date: Wed Jan 9 19:40:25 2019
>> New Revision: 1850895
>>
>> URL: http://svn.apache.org/vie
Hi Jim,
Am 09.01.19 um 20:40 schrieb j...@apache.org:
> Author: jim
> Date: Wed Jan 9 19:40:25 2019
> New Revision: 1850895
>
> URL: http://svn.apache.org/viewvc?rev=1850895&view=rev
> Log:
> bump up to outrageous numbers...
>
> Modified:
> openoffice/trunk/main/solenv/inc/minor.mk
>
> Modifi
> On Jan 14, 2019, at 12:24 PM, Damjan Jovanovic wrote:
>
> That loop happens when one or more files can't be found.
>
Ahh... that makes perfect sense. #sarcasm
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.o
That loop happens when one or more files can't be found.
The problem was that the path was wrong:
bridges/source/cpp_uno/s5abi_macosx_x86_64
instead of:
bridges/source/cpp_uno/s5abi_macosx_x86-64
(the last separator is a minus, not an underscore).
Fix committed in 1851285.
Damjan
On Mon, Jan 14
=
Building module bridges
=
Entering /Users/jim/src/asf/trunk/main/bridges/prj
cd .. && make -s -r -j6 && make -s -r deliverlog
[ build PVTUNOTYPES ]
[ build PVTUNOTYPES ]
[ build CXX ] bridges/source/jni_uno/jni_bridge
[ build CXX ] bridges/source/jni_uno/jni_data
[ b
Please attach the text printed out in this infinite loop.
On Wed, Jan 9, 2019 at 3:47 PM Jim Jagielski wrote:
> FWIW, I'm having similar problems w/ bridges, which was ported to
> gbuild... I get an infinite loop while linking. There's something wonky
> with some edge cases here...
> ---
FWIW, I'm having similar problems w/ bridges, which was ported to gbuild... I
get an infinite loop while linking. There's something wonky with some edge
cases here...
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.or
Hi Damjan,
Am 25.11.18 um 14:45 schrieb Damjan Jovanovic:
> One problem was that GNU make 3.8.1, which we use on the Linux buildbots,
> doesn't have the:
> $(file < ...)
> function. I've now changed it to use:
> $(shell cat ...)
> instead. This doesn't however explain why the Windows buildbot also
One problem was that GNU make 3.8.1, which we use on the Linux buildbots,
doesn't have the:
$(file < ...)
function. I've now changed it to use:
$(shell cat ...)
instead. This doesn't however explain why the Windows buildbot also failed
in xmerge, as its GNU make is recent enough.
Another problem w
Hello,
now I'm able to create sdf files based on the source code and the files
in Pootle.
Source code ie r1847189.
Building with current trunk failed con Centos 7 as described in this thread.
So I think we need a branch whre we can work for the next release like 4.2.
@ Jim: Can you gererate a
Linux-32 and Windows builds also fail in xmerge.
Matthias
Am 24.11.18 um 16:08 schrieb Matthias Seidel:
> Hi Damjan,
>
> This commit breaks at least our Linux-64 builds:
>
> https://ci.apache.org/projects/openoffice/buildlogs/linux64/main/xmerge/unxlngx6.pro/misc/logs/prj.txt
>
> Regards,
>
>
Hi Damjan,
This commit breaks at least our Linux-64 builds:
https://ci.apache.org/projects/openoffice/buildlogs/linux64/main/xmerge/unxlngx6.pro/misc/logs/prj.txt
Regards,
Matthias
Am 24.11.18 um 08:58 schrieb dam...@apache.org:
> Author: damjan
> Date: Sat Nov 24 07:58:57 2018
> New Revisi
Hi Pedro,
Am 22.10.18 um 18:47 schrieb Pedro Lino:
> Hi all
>
>
>> On October 22, 2018 at 5:38 PM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>>
>>
>> Am 22.10.18 um 18:35 schrieb Jim Jagielski:
>>
>> > > The thing is, IMO, that these ARE community builds, and, as
>>
Hi all
> On October 22, 2018 at 5:38 PM Matthias Seidel mailto:matthias.sei...@hamburg.de > wrote:
>
>
> Am 22.10.18 um 18:35 schrieb Jim Jagielski:
>
> > > The thing is, IMO, that these ARE community builds, and, as such,
> should be noted as such on the About Page... But I'm fi
Am 22.10.18 um 18:35 schrieb Jim Jagielski:
> The thing is, IMO, that these ARE community builds, and, as such, should be
> noted as such on the About Page... But I'm fine w/ removing that depending on
> what people think.
The community is not a vendor. If you leave it out everything is OK:
"Th
The thing is, IMO, that these ARE community builds, and, as such, should be
noted as such on the About Page... But I'm fine w/ removing that depending on
what people think.
> On Oct 22, 2018, at 12:32 PM, Matthias Seidel
> wrote:
>
> Am 22.10.18 um 18:13 schrieb Jim Jagielski:
>> It was used
Am 22.10.18 um 18:13 schrieb Jim Jagielski:
> It was used for macOS. I was just making it consistent among all my builds.
Wouldn't it be better to make the macOS build consistent with the other
builds... ;-)
>> On Oct 22, 2018, at 12:08 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> --with-v
It was used for macOS. I was just making it consistent among all my builds.
> On Oct 22, 2018, at 12:08 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> --with-vendor="Apache OpenOffice Community Build" \
>
> results in weird wording:
>
> "This product was created by Apache OpenOffice Community
Hi Jim,
--with-vendor="Apache OpenOffice Community Build" \
results in weird wording:
"This product was created by Apache OpenOffice Community Build, based on
Apache OpenOffice"
And we didn't use --with-vendor for a release build before.
Regards,
Matthias
Am 22.10.18 um 14:31 schrieb j...
Am 14.10.2018 um 17:51 schrieb Matthias Seidel:
I am not sure why this had to be added again because I did it already on
30.12.2017...
Actually it is working right now on the download page.
OK, I haven't seen this.
Marcus
Am 14.10.2018 um 17:30 schrieb build...@apache.org:
Author: buildbo
Hi Marcus,
I am not sure why this had to be added again because I did it already on
30.12.2017...
Actually it is working right now on the download page.
Did you use the CMS?
Regards,
Matthias
Am 14.10.2018 um 17:30 schrieb build...@apache.org:
> Author: buildbot
> Date: Sun Oct 14 15:30:28
Hi Peter,
I have yet to find out. ;-)
Yes, they are macOS only, but they are the only changes in configure in
that commit.
Matthias
Am 09.10.2018 um 12:41 schrieb Peter Kovacs:
> Did reverting of the changes solve the issue?
>
> Because the changes there are only MacOSx related. ;)
>
>
> On 10
Did reverting of the changes solve the issue?
Because the changes there are only MacOSx related. ;)
On 10/8/18 8:56 PM, Matthias Seidel wrote:
I don't think so...
Maybe we can just revert the changes in configure.in?
I will try tomorrow.
Am 08.10.2018 um 20:06 schrieb Peter Kovacs:
I thoug
I don't think so...
Maybe we can just revert the changes in configure.in?
I will try tomorrow.
Am 08.10.2018 um 20:06 schrieb Peter Kovacs:
> I thought it is my stupidity. Maybe I have merged wrong?
>
> On 10/8/18 7:49 PM, Matthias Seidel wrote:
>> Hi all,
>>
>> This one breaks our builds in con
I thought it is my stupidity. Maybe I have merged wrong?
On 10/8/18 7:49 PM, Matthias Seidel wrote:
Hi all,
This one breaks our builds in configure:
https://ci.apache.org/builders/openoffice-linux64-41x/builds/158/steps/configure/logs/stdio
Regards,
Matthias
Am 08.10.2018 um 08:09 schr
Hi all,
This one breaks our builds in configure:
https://ci.apache.org/builders/openoffice-linux64-41x/builds/158/steps/configure/logs/stdio
Regards,
Matthias
Am 08.10.2018 um 08:09 schrieb pe...@apache.org:
> Author: petko
> Date: Mon Oct 8 06:09:21 2018
> New Revision: 1843108
>
> URL:
Hi Yuri,
Just out of curiousity.
Since you added the dependencies to WinResTarget_vcl.mk, is this file
still needed?
https://svn.apache.org/repos/asf/openoffice/trunk/main/vcl/os2/source/src/makefile.mk
Regards,
Matthias
Am 11.09.2018 um 16:01 schrieb yda...@apache.org:
> Author: ydario
>
Am 08.09.2018 um 13:32 schrieb Damjan Jovanovic:
> On Sat, Sep 8, 2018 at 10:47 AM Matthias Seidel
> wrote:
>
>> Am 08.09.2018 um 10:16 schrieb Damjan Jovanovic:
>>> It should be fixed in 1840343:
>>>
>>> "When building other languages (--with-lang="..."), the build was
>> breaking
>>> because rsc
On Sat, Sep 8, 2018 at 10:47 AM Matthias Seidel
wrote:
> Am 08.09.2018 um 10:16 schrieb Damjan Jovanovic:
> > It should be fixed in 1840343:
> >
> > "When building other languages (--with-lang="..."), the build was
> breaking
> > because rsc couldn't compile certain resources (usually in main/sfx
Am 08.09.2018 um 10:16 schrieb Damjan Jovanovic:
> It should be fixed in 1840343:
>
> "When building other languages (--with-lang="..."), the build was breaking
> because rsc couldn't compile certain resources (usually in main/sfx2).
>
> Apparently the RSC preprocessor, rscpp, uses very small buffe
1 - 100 of 352 matches
Mail list logo
