; instsetoo_native
> need(s) to be rebuilt
>
> ERROR: error 65280 occurred while making
> /home/mechtilde/aoo42x/main/instsetoo_native/util
>
> Kind regards
>
> Am 23.01.19 um 16:29 schrieb Mechtilde:
>> Hello Jim,
>>
>> Am 23.01.19 um 15:53 sch
The current 4.2.x test builds were done w/ an unpatched EPM. All later ones
will use a patched version.
> On Jan 23, 2019, at 5:47 PM, Kay Schenk wrote:
>
>
> On 1/20/19 7:28 AM, Jim Jagielski wrote:
>> I've uploaded the latest test builds for macOS and Linux 64
What does 'epm --version' say on both systems?
> On Jan 23, 2019, at 8:50 AM, Mechtilde wrote:
>
> Hello,
>
> I did it now under Debian 8 again. Tere it works as expected and builds
> DEBs and RPMs.
>
> Kind regards
>
> Am 23.01.19 um 07:40 schrieb Mechtilde:
>> Hello,
>>
>> to document the
After spending some more time w/ CentOS7 32bit, I'm pretty confident that we
can baseline it a our "primary" complimentary community build server OS.
So, from what I see, the move from AOO 4.1.x to 4.2.x (and above) will
mean that we baseline CentOS7 with Ubuntu 14.04 as secondary. This
does not m
FWIW, I have both CentOS7 64 and 32, and Ubuntu 14.04 64 and 32 setup to build.
All my builds have been using CentOS7. We may consider switching to Ubuntu
as our "official" community build server for 4.2.x and later.
-
To unsubscri
cutting it.
> On Jan 22, 2019, at 2:00 PM, Mechtilde wrote:
>
> Hello,
>
> Am 22.01.19 um 19:22 schrieb Jim Jagielski:
>> It's old and has been EOL for awhile. But we're just talking build server...
>> to support older systems we need to use an older syst
I am trying to understand the various numberings we have and where they count
and what they mean.
Of course, the X.Y.Z numbers make sense... but then we have a "BUILD" number
and a 'mX' number
What are they for? Can a 4.2.0 have a build of say 9810 and a 4.17 of 9812?
--
It's old and has been EOL for awhile. But we're just talking build server...
to support older systems we need to use an older system.
> On Jan 22, 2019, at 1:15 PM, Mechtilde wrote:
>
> Hello
>
> Am 22.01.19 um 19:09 schrieb Jim Jagielski:
>> I've bee
I've been playing around with using Fedora19 instead of
CentOS7 for the 4.2.0 ("official") builds... Mostly
due to CentOS7 not really supporting 32bit and it doesn't
seem wise to use 2 sep systems for the Linux builds
or an "AltArch" build.
Fed19 fully supports 64 and 32bit and, in fact, CentOS7 i
ng a
> ready-to-go 4.1.7. Any day, we could encounter a really serious,
> must-fix-immediately, security bug. Having as much as possible done ahead of
> time will reduce the delay from knowing the fix to end users having the fix.
>
> On 1/21/2019 8:36 AM, Jim Jagielski wrote:
>>
Gotcha. I was just thinking that if we had a 4.1.7 branch in a ready-to-go
stage, if we needed to do another 4.1.x release it would be already there.
But agree that the focus should be on 4.2.0
> On Jan 21, 2019, at 11:25 AM, Rory O'Farrell wrote:
>
> On Mon, 21 Jan 2019 11:12:
Does it make sense to create a branch of 4.1.7 from 4.1.6...?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
I'm in the process of uploading Linux 32bit builds
> On Jan 20, 2019, at 10:28 AM, Jim Jagielski wrote:
>
> I've uploaded the latest test builds for macOS and Linux 64.
> These are based on ~r1851640 and include 2 main updates from
> the earlier one:
>
> o beansh
I've uploaded the latest test builds for macOS and Linux 64.
These are based on ~r1851640 and include 2 main updates from
the earlier one:
o beanshell now included
o macOS path bug should now be squashed
(https://bz.apache.org/ooo/show_bug.cgi?id=127965)
Let me know if anyone wants me to kick
sure if this was/is in any way connected to the removal
from CatB.
Anyone else try building 4.2.x/trunk w/ beanshell?
> On Jan 17, 2019, at 2:58 PM, Jim Jagielski wrote:
>
> I just noticed that when including CatB components, beanshell
> is not included in trunk/4.2.x but IS with 4.
I just noticed that when including CatB components, beanshell
is not included in trunk/4.2.x but IS with 4.1.x
Any idea why the change?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-ma
Well, the error I was hitting is fixed, yeah.
You may need to blow away main/instsetoo_native/unxlngx6.pro/* and rebuild
> On Jan 17, 2019, at 9:32 AM, Mechtilde wrote:
>
> Hello,
>
> Am 15.01.19 um 19:42 schrieb Jim Jagielski:
>> As a reminder, w/ AOO 4.2.0, o
> On Jan 16, 2019, at 4:33 PM, Rory O'Farrell wrote:
>
> On Wed, 16 Jan 2019 15:41:38 -0500
> Jim Jagielski mailto:j...@jagunet.com>> wrote:
>
>> Now uploaded are test builds for macOS and Linux 64...
>>
>> The macOS builds include the proposed p
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
I know I should know this
Where do we post/document changes? There isn't a CHANGES file, so
is there a specific wiki page?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h
Now uploaded are test builds for macOS and Linux 64...
The macOS builds include the proposed patch for
https://bz.apache.org/ooo/show_bug.cgi?id=127965
> On Jan 15, 2019, at 11:48 AM, Jim Jagielski wrote:
>
> Currently, only macOS builds are available and only a handful
>
No doubt, something in the underlying implementation of __lxstat64 has
changed for those CentOS and Debian platforms that is causing
our hack to not work.
> On Jan 15, 2019, at 8:28 PM, Damjan Jovanovic wrote:
>
> Great work, thank you Jim!
>
> On Wed, Jan 16, 2019 at 3:29 A
OK, so I've been doing some digging and it looks like the reason for the above
is because we need to fool epm (and dpkg et. al.) into thinking we are root in
order to correctly build the DEB packages.
The problem is that this is really, really system specific and even OS version
specific.
Most
> On Jan 15, 2019, at 2:41 PM, Jim Jagielski wrote:
>
> OK... looking further, this is just a warning and even occurs w/ rpm.
>
> What I see is that the call for epm when doing a deb does a
> "LD_PRELOAD=/home/jim/src/asf/AOO42X/main/solver/420/unxlngx6.pro/bin/getuid
OK... looking further, this is just a warning and even occurs w/ rpm.
What I see is that the call for epm when doing a deb does a
"LD_PRELOAD=/home/jim/src/asf/AOO42X/main/solver/420/unxlngx6.pro/bin/getuid.so"
whereas that is not done when calling epm for rpms:
deb/logging/ast/log_AOO420_a
As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_OpenOffice"
Notice the "_" :(
I am guessing that's a dpg/deb restriction??
> On Jan 15, 2019, at 1:37 PM, Jim Jagielski wrote:
>
> OK... here are the pertinent sections of the log... Of particular n
Currently, the following langs are uploaded:
de | en-US | es | fr | nl | ru | tr
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_OpenOffice"
Notice the "_" :(
I am guessing that's a dpg/deb restriction??
OK... here are the pertinent sections of the log... Of particular note, look at
the "Product names should only contain letters and numbers!" error.
12.189364 : lang : ##
12.189396 : lang : epm call for openoffice-en-US-calc
12.189425 :
Currently, only macOS builds are available and only a handful
of languages have been uploaded. Let me know if there are
other langs people would like to test.
Working on Linux 64bit as we speak...
The location? Right here:
http://home.apache.org/~jim/AOO-builds/
Cheers!
--
> On Jan 15, 2019, at 8:13 AM, Jim Jagielski wrote:
>
>
>
>> On Jan 15, 2019, at 2:36 AM, Peter Kovacs wrote:
>>
>> Maybe it is a good point to ask infra to switch to git?
>>
>
> Or maybe encourage people to use git-svn?
>
There
> On Jan 15, 2019, at 2:36 AM, Peter Kovacs wrote:
>
> Maybe it is a good point to ask infra to switch to git?
>
Or maybe encourage people to use git-svn?
Let me do another build (verbose) and really dig thru the logs
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Yeah... getting this on my CentOS7 builds as well...
Just on debs... rpms are fine.
> On Jan 14, 2019, at 4:37 PM, Mechtilde wrote:
>
> Hello,
>
> Am 10.01.19 um 07:01 schrieb Mechtilde:
>>
>>
>> Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
>>> Hi
>>>
>>> I am glad it worked.
>>>
>>> Sur
> 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's great. thx
> On Jan 14, 2019, at 11:28 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 14.01.19 um 16:52 schrieb Jim Jagielski:
>> This week I plan on building AOO42X on our "official" Linux
>> and macOS build platforms (VMs)... just to a
This week I plan on building AOO42X on our "official" Linux
and macOS build platforms (VMs)... just to allow us to do a
quick check that all looks reasonable at this point in time.
-
To unsubscribe, e-mail: dev-unsubscr...@openoff
meone does the process.
This looks like what we have:
https://wiki.openoffice.org/wiki/Translation_from_4.2
> On Jan 14, 2019, at 10:25 AM, Mechtilde wrote:
>
> Hello Jim,
>
> Am 14.01.19 um 14:54 schrieb Jim Jagielski:
>> How does one update the SDF file? What'
; On Jan 14, 2019, at 10:40 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 09.01.19 um 21:54 schrieb Jim Jagielski:
>>
>>> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>>>
>>> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK i
an Jovanovic wrote:
>
> 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. T
How does one update the SDF file? What's the process?
tia
> On Jan 11, 2019, at 5:09 PM, Matthias Seidel
> wrote:
>
> Am 11.01.19 um 23:07 schrieb Marcus:
>> Am 11.01.19 um 23:02 schrieb Jim Jagielski:
>>> Just noticed this... not sure if it's just happeni
Just noticed this... not sure if it's just happening during my
macOS builds or with others (will kick off CentOS7 on monday).
Any ideas:
WARNING: mis-named or un-known %-variable in setup script at line 33453:
Description (kab) = "\u1e6c\u1e6def til\u0263uyin tiwurmanin mi ara
yewjed
+1 on doing what we can to move to gbuild as appropriate, but we also need
to find out what our long term plan is, esp as related to non-*Nix platforms.
I hope to get macOS more up-to-date and part of that is fixing the longstanding
confusion regarding UDK library versioning. Currently, AOO forces
hat seems to break is in
> main/solenv/bin/modules/installer/simplepackage.pm
> I suggest changing it to print out some debugging info and then "build
> --from instsetoo_native".
>
> On Wed, Jan 9, 2019 at 7:34 PM Jim Jagielski wrote:
>
>>
>>
>>> On Ja
> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>
> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
> thinking...
>
Yeppers... for sure it's the udk versioning, which is more a Linux thing than a
macOS (or Windows) thing.
Will look into
Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
thinking...
76.372903 : lang : ##
76.372943 : lang : Registering extensions:
76.372991 : lang : ##
76.381173
09.01.19 um 16:12 schrieb Jim Jagielski:
>> Let me go into more detail here :)
>> So my plan is to create a 42X branch off of trunk once trunk builds. This
>> branch will now be the development branch for the 4.2.x releases, at which
>> point trunk will be the futur
Request for help...
Any ideas would be helpful:
% build --all:instsetoo_native
build -- version: 1775979
=
Building module instsetoo_native
=
Entering
/Users/jim/src/asf/AOO42X/main/instsetoo_native/inc_openoffice/windows/msi_languages
Entering /Users/jim/src/asf/AOO
a little script for this? To identify all the places
> that need tobe changed? IMHO it should be somewhere in devtools.
>
> Marcus
>
>
>
>> Am 09.01.19 um 20:41 schrieb Jim Jagielski:
>>> All done
>>>
All done
> On Jan 9, 2019, at 2:21 PM, Matthias Seidel
> wrote:
>
> 9800
> On Jan 9, 2019, at 1:37 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 09.01.19 um 18:40 schrieb Jim Jagielski:
>> Trunk has been branched off to the (eventual) release branch
>> for the AOO 4.2.x series. The branch is:
>>
>>https://sv
Trunk has been branched off to the (eventual) release branch
for the AOO 4.2.x series. The branch is:
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Development can, and should, continue on trunk, but ONLY
approved backports should be applied to AOO42X.
Cheers!
> On Jan 9, 2019, at 12:18 PM, Jim Jagielski wrote:
>
> OK, so I *finally* got a version in which at least the thing builds, but I
> once again get hit with the instsetoo_native final packing problem that I had
> a few months ago...
>
Error: ERROR:
/Users/jim/s
OK, so I *finally* got a version in which at least the thing builds, but I once
again get hit with the instsetoo_native final packing problem that I had a few
months ago...
At this point, it seems prudent to branch... I'll do so in a few hours
branch will be re-applied). So the process
will be development on trunk w/ back ports to 42X. 4.2.0, 4.2.1, et.al.
releases will be branched and tagged from the 42X branch.
Sound OK?
> On Jan 9, 2019, at 10:02 AM, Jim Jagielski wrote:
>
> In another thread I mentioned a plan... Bringing i
In another thread I mentioned a plan... Bringing it up here for a wider
audience.
My plan is to branch a 4.20 branch off of trunk as soon as it is relatively
buildable on macOS.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffi
No worries at all, and sorry if I come off heavy handed... The macOS platform
is problematic, at some level, for AOO because it requires some older tech for
it to compile and run. For example, vcl still uses QTkit, which has been
deprecated for awhile, which means we can't fully utilize later SD
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
Which
> would make it easy for others to check on their work.
>
> Am Dienstag, 8. Januar 2019 schrieb Jim Jagielski:
>> One option we have is that we drop support for macOS 10.7 and older for
>> 4.20.x... this MIGHT help.
>>
>> I can/will test that assumption.
>
One option we have is that we drop support for macOS 10.7 and older for
4.20.x... this MIGHT help.
I can/will test that assumption.
> On Jan 8, 2019, at 9:54 AM, Jim Jagielski wrote:
>
> I've started playing around w/ getting 4.2.0-HEAD to build; as expected, so
> real is
I've started playing around w/ getting 4.2.0-HEAD to build; as expected, so
real issues w/ Ubuntu or CentOS7 but macOS is causing problems, what with the
migration to gbuild for various modules and how these migrations constantly
break macOS. I'll try to start hammering fixing/working-around the
I am looking into the 1st 2 and cannot find, at present, where these vars are
being set... will continue to look.
> On Dec 20, 2018, at 10:17 AM, Rony G. Flatscher
> wrote:
>
> Peter,
>
> as these are different problems to issue 117961 I opened three separate new
> issues for them to allow
>
I've been slammed both at work and personal and haven't had
time to do much AOO stuff... just a FYI in case people were
curious. Should free up by the end of the month.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.o
If/When there is a need, I can do it.
> On Dec 1, 2018, at 3:24 PM, Matthias Seidel
> wrote:
>
> Hi all,
>
> Am 13.11.18 um 21:38 schrieb Andrea Pescetti:
>> Peter Kovacs wrote:
>>> I am just saying a 4.1.7 release has nothing to do with the efforts we
>>> have to organize for 4.2.0.
>>
>> OK
FWIW, 4.1.5 and 4.1.6 were built w/ the exact same setup... same Xcode and SDK
> On Nov 27, 2018, at 6:38 AM, Jim Jagielski wrote:
>
> We build with MACOSX_DEPLOYMENT_TARGET=10.7 using Xcode7 and macosx10.11
>
>> On Nov 24, 2018, at 3:39 AM, Peter Kovacs wrote:
>>
>
We build with MACOSX_DEPLOYMENT_TARGET=10.7 using Xcode7 and macosx10.11
> On Nov 24, 2018, at 3:39 AM, Peter Kovacs wrote:
>
> Hi all,
>
> The guide offers something between 10.7 and 10.11.
>
> There is an issue with MacOSx 10.10.x which runs in trouble.
>
>
> Check https://bz.apache.org/oo
w00t!
> On Nov 23, 2018, at 4:52 PM, Peter Kovacs wrote:
>
> Hello all,
>
> I have successfully obtained a Developer ID from Infra. I will next week
> try to sign the Mac Version. Lets see if we can solve the gatekeeper
> Issue. :)
>
> Maybe Jim, would you also obtain a DeveloperID?
>
> Check
For Linux, Java7, for macOS, Java6
> On Nov 15, 2018, at 6:15 PM, Kay Schenk wrote:
>
> On 11/14/2018 09:29 PM, Don Lewis wrote:
>> On 15 Nov, Matthias Seidel wrote:
>>> Hi Kay,
>>>
>>> Am 15.11.18 um 00:48 schrieb Kay Schenk:
Two things --
* I see localization was set up for Kabyle.
> On Nov 13, 2018, at 4:40 PM, Branko Čibej wrote:
>
>
> That's OK, any kind of testing, even with OO trunk, would be welcome.
> The only other Serf consumer I can test is Subversion, adding even one
> more would make out real-life testing increase by 100%. :)
>
OT: IMO, Serf would have a m
> On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
>
> And I suggest also to branch 4.2.0 from trunk. Jim you still available
> to be the release manager on this branch? - Maybe we should branch from
> the latest dev build version if we can find out and then check on the
> commits.
That work
Could we/Should we have some of us tweet that 4.1.6-RC1 is available and "ask"
people to try it out...?
> On Nov 7, 2018, at 6:28 PM, Marcus wrote:
>
> Am 07.11.18 um 23:59 schrieb Andrea Pescetti:
>> On 06/11/2018 Marcus wrote:
>>> Why no own builds?
>>> At the moment I'm very busy with my day
Could we/Should we have some of us tweet that 4.1.6-RC1 is available and "ask"
people to try it out...?
> On Nov 7, 2018, at 6:28 PM, Marcus wrote:
>
> Am 07.11.18 um 23:59 schrieb Andrea Pescetti:
>> On 06/11/2018 Marcus wrote:
>>> Why no own builds?
>>> At the moment I'm very busy with my day
FWIW, it is very easy to request:
https://gitbox.apache.org/setup/newrepo.html
> On Nov 6, 2018, at 8:42 AM, Jim Jagielski wrote:
>
> To be clear, we're talking about moving to Gitbox, right?
>
>> On Nov 5, 2018, at 5:37 PM, Peter Kovacs wrote:
>>
&g
To be clear, we're talking about moving to Gitbox, right?
> On Nov 5, 2018, at 5:37 PM, Peter Kovacs wrote:
>
> Hello all,
>
> We had the discussion 1 year ago to move to git. For me it was a clear
> vote for this move. However nothing happened when we released 4.1.4.
>
> https://lists.apache.
> On Nov 5, 2018, at 12:17 PM, Matthias Seidel
> wrote:
>
>
> I did correct all sha512 files for the Windows builds, so the ones for
> macOS and Linux32/64 remain to be updated.
>
What needs to be done, exactly?
-
To uns
> On Nov 5, 2018, at 10:19 AM, Dave Fisher wrote:
>
> My practice had been to validate the source release and test the Mac
> releases. To me that was enough.
+1
I'm not exactly sure 100% what needs to be changed... Plus, if we change the
names of files, don't we need to ensure that the sourceforge links are correct
as well? Has that been looked at?
-
To unsubscribe, e-mail: dev-unsubscr.
+1 for release! Thx for RMing.
> On Nov 1, 2018, at 2:52 AM, Peter Kovacs wrote:
>
> Let's try again.
>
>
> Welcome to the vote on Release Candidate 1 for the 4.1.6 Release.
>
> The vote will close on Wednesday the 7.11.2018.
>
> The binaries and the source for testing are to be taken from:
> On Nov 1, 2018, at 7:49 AM, Pedro Lino wrote:
>
> Hi Patricia
>
> I'm taking this opportunity to write to you directly (I hope this is not a
> problem)
>
> Do you have experience building in Linux?
>
>
...
> libgstreamer-plugins-bad1.0-0 is already the newest version
> (1.8.3-1ubuntu0.
Did I miss it?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Isn't the main issue whether these are blockers or not?
> On Oct 26, 2018, at 3:39 PM, Don Lewis wrote:
>
> On 26 Oct, Jim Jagielski wrote:
>>
>>
>>> On Oct 26, 2018, at 2:30 PM, Don Lewis wrote:
>>>
>>> The redland/raptor/rasqal upgrade
> On Oct 26, 2018, at 2:30 PM, Don Lewis wrote:
>
> The redland/raptor/rasqal upgrade
> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
> Someone with a Mac needs to see if the configure.in changes are needed
> or if it builds on a Mac as-is.
I have no idea how to parse the a
It is most likely better if we start tagging RCs. Anytime we need to "record"
some version, a tag make sense, IMO.
> On Oct 26, 2018, at 2:16 PM, Andrea Pescetti wrote:
>
> Jim Jagielski wrote:
>> I went ahead and tagged AOO-4.1.6RC1. If it passes then we can co
23/10/2018 Matthias Seidel wrote:
>>>> Am 23.10.18 um 13:06 schrieb Jim Jagielski:
>>>>> r1844555 was the SVN version of HEAD at the time of the email.
>>>> Yes, and it increases by the time of writing...
>>>> So it gives no information about what
13:12:37 MESZ schrieb Matthias Seidel
> :
>> Am 23.10.18 um 13:06 schrieb Jim Jagielski:
>>> r1844555 was the SVN version of HEAD at the time of the email.
>>
>> Yes, and it increases by the time of writing...
>> So it gives no information about what revision the
1.6 was r1844436:
> https://svn.apache.org/viewvc?view=revision&revision=1844436
>
> I can start a new build, will this be a RC?
>
> And builds are signed by those who do the builds. ;-)
>
> Matthias
>
>>
>> Thank you all for your efforts!
>>
>>
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 Jagielsk
>
>>>>
>>>>> Signatures and checksums could be generated with:
>>>>>
>>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>>>>>
>>>>> [1] https://www.apache.org/dev/release-dis
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
I am ready to start building macOS and Linux 64&32bit builds of HEAD of AOO416,
which is m1 at r1844555
Just say the word :)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h..
>>> But my test build are always with --with-vendor in configure, so
>> I
>>>>>>>> didn't realize that it was missing from branch 4.1.6.
>>>>>>>>
>>>>>>>> Matthias
>>>>>>>>
&
All uploaded!
> On Oct 20, 2018, at 4:18 PM, Andrea Pescetti wrote:
>
> Jim Jagielski wrote:
>> Which langs would people like? I'll upload to my Apache people space.
>
> Italian please. And thanks to both you and Matthias for providing the builds.
>
> The R
That's what it looks like, yeah.
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
> wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>>
>> Fixed in r1844422 and r1844423
>
> That means, when using --vendor it is updated
Found it.
Fixed in r1844422 and r1844423
> On Oct 20, 2018, at 10:54 AM, Jim Jagielski wrote:
>
> Are we sure that that part of the splash screen isn't hardcoded in (ie: the
> Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice Communit
> On Oct 20, 2018, at 9:45 AM, Pedro Lino wrote:
>
> That is probably because your OS is named Darwin (more evolved?) :)
>
>
>
>
>
>
>
>> On October 20, 2018 at 2:35 PM Jim Jagielski wrote:
>>
>> Hmmm... The macOS builds are sh
The only customizing on my builds is:
--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`"
On Oct 20, 2018, at 7:04 AM, Pedro Lino wrote:
>
> Hi Matthias
>
>> On October 20, 2018 at 11:26 AM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote:
>>
>>
>>
I can
All done!
> On Oct 19, 2018, at 4:59 PM, Pedro Lino wrote:
>
> Hi Jim
>
> Can you please upload pt (European Portuguese)?
>
> Thanks
> Pedro
>
>> On October 19, 2018 at 9:14 PM Jim Jagielski wrote:
>>
>>
>> Builds for macOS and Li
; Hi Jim,
>
> Am 19.10.18 um 18:17 schrieb Jim Jagielski:
>> My macOS builds are almost done; next up CentOS5 (Linux) ones.
>>
>> Which langs would people like? I'll upload to my Apache people space.
>
> It would be great if you could provide German
My macOS builds are almost done; next up CentOS5 (Linux) ones.
Which langs would people like? I'll upload to my Apache people space.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:
Subj sez it all...
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
601 - 700 of 1170 matches
Mail list logo
