Great work, thank you Jim!
On Wed, Jan 16, 2019 at 3:29 AM Jim Jagielski wrote:
> 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
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.
On 09/01/2019 Jim Jagielski wrote:
Trunk
|> New branch for 4.2.x
| |---> Branch and/or Tag for 4.2.0
| |---> Branch and/or Tag for 4.2.1
That is, 4.2.2, for example, is not branched from 4.2.1 but rather from the
ever existing 4.2.x branch.
This can work, provided
Ahh nice. We should update the editing cms-guide.
On 15.01.19 22:31, Keith N. McKenna wrote:
> On 1/15/2019 4:00 PM, Peter Kovacs wrote:
>> I am think I do something wrong.
>>
>> https://www.openoffice.org/security/bulletin.html
>>
>> should be then
>>
>>
On 1/15/2019 4:00 PM, Peter Kovacs wrote:
> I am think I do something wrong.
>
> https://www.openoffice.org/security/bulletin.html
>
> should be then
>
> http://openofficeorg.staging.apache.org/openofficeorg/security/bulletin.html
>
> This leads to 404. So what is the right path to the
Awesome Jörg. This worked. Murphies law. YAY.
The right link for publish something is: https://cms.apache.org/ooo-site/
you get a login page and then have a simple form for publishing the
latest build.
thanks to all efforts.
On 15.01.19 11:12, Jörg Schmidt wrote:
> Hello,
>
>> -Original
I fail with
javascript:void(location.href='https://cms.apache.org/redirect?
uri='+escape(location.href
))
Firefox does not return anything. I do not have an Internet explorer on
my OS.
On 15.01.19 21:27, Jörg Schmidt wrote:
>
>
>> -Original Message-
>> From: Marcus
I am think I do something wrong.
https://www.openoffice.org/security/bulletin.html
should be then
http://openofficeorg.staging.apache.org/openofficeorg/security/bulletin.html
This leads to 404. So what is the right path to the bulletin?
I try Jörg's approach too.
On 15.01.19 20:44, Marcus
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Tuesday, January 15, 2019 8:44 PM
> To: dev@openoffice.apache.org
> Subject: Re: what do i need to do to update our static websides
>
> Am 15.01.19 um 08:38 schrieb Peter Kovacs:
> > I committed a change to
Am 15.01.19 um 21:17 schrieb daze2...@nym.hush.com.INVALID:
> My point standsHave a great day :)
Dream on... ;-)
>
> _--_
> On 2019-01-15 at 3:14 PM, "Marcus" wrote:Am 15.01.19 um 20:56 schrieb
> daze2...@nym.hush.com.INVALID:
>> My apologies ...The link
> 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.so"
> whereas that is
My point standsHave a great day :)
_--_
On 2019-01-15 at 3:14 PM, "Marcus" wrote:Am 15.01.19 um 20:56 schrieb
daze2...@nym.hush.com.INVALID:
> My apologies ...The link below indicates AndrOpen Office as an
Apache
> element with the Apache logo clearly
Am 15.01.19 um 20:56 schrieb daze2...@nym.hush.com.INVALID:
My apologies ...The link below indicates AndrOpen Office as an Apache
element with the Apache logo clearly indicated.
https://www.openoffice.org/porting/
OK, but the first 2 sentences on that page are:
"The following list of
My apologies ...The link below indicates AndrOpen Office as an Apache
element with the Apache logo clearly indicated.
https://www.openoffice.org/porting/
_--_
On 2019-01-15 at 2:30 PM, "Marcus" wrote:Am 15.01.19 um 17:35 schrieb
daze2...@nym.hush.com.INVALID:
Am 15.01.19 um 08:38 schrieb Peter Kovacs:
I committed a change to ooo_sites and after 6h the changes are still not
visible.
Are there additional steps needed?
yes, committing a website change goes to SVN which triggers an automatic
build for the staging area.
But to get it published you
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:
Am 15.01.19 um 19:40 schrieb Jim Jagielski:
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??
was there a change compared to 4.1.6? If so, what was it and why was it
necessary? Is it possible to revert
Am 15.01.19 um 17:35 schrieb daze2...@nym.hush.com.INVALID:
"AndrOpen Office (Android port of Apache
OpenOffice) AndrOpen Office is the world's first port of
OpenOffice for Android, It is made available on Google Play by the
AndrOpen Office team and it
Please note that this is an English-only list, so that everybody has a
chance to follow the mails.
Make sure that you are using the correct download link. For OpenOffice
its: "https://www.openoffice.org/download/;.
HTH
Marcus
Am 15.01.19 um 12:13 schrieb Ing.Harald Schimpl:
wollte Open
Sg. Damen und Herren,
wollte Open Office downloaden, bekomme aber bei dem Link die Fehlermeldung:
Leider können wir nicht auf diese Seite zugreifen.
Probieren Sie Folgendes
* Stellen Sie sicher, dass Sie die richtige URL verwenden:
https://sourceforge.net
* Seite
"AndrOpen Office (Android port of Apache
OpenOffice) AndrOpen Office is the world's first port of
OpenOffice for Android, It is made available on Google Play by the
AndrOpen Office team and it requires Android 4.0.3 or later. "
Greetings,As a Linux user
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 note, look
> at the "Product names
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 :
Am 15. Januar 2019 18:27:27 MEZ schrieb Damjan Jovanovic :
>Does 4.1.x build on Debian 9?
I never test it.
>> >Mechtilde Stehmann
>> >## Apache OpenOffice
>> >## Freie Office Suite für Linux, MacOSX, Windows
>> >## Debian Developer
>> >## PGP encryption welcome
>> >## F0E3 7F3D C87A 4998
Can you also prepare de.So if it works I will test.
Mechtilde
Am 15. Januar 2019 18:34:09 MEZ schrieb Rory O'Farrell :
>On Tue, 15 Jan 2019 11:48:09 -0500
>Jim Jagielski wrote:
>
>> Currently, only macOS builds are available and only a handful
>> of languages have been uploaded. Let me know if
On Tue, 15 Jan 2019 11:48:09 -0500
Jim Jagielski wrote:
> 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:
>
Does 4.1.x build on Debian 9?
On Tue, Jan 15, 2019 at 1:17 PM Stehmann wrote:
> it does't build with epm 4.2 too. As I described before it works under
> Debian 8. So I habe no idea where to start with bisect.
>
> Mechtilde
>
> Am 15. Januar 2019 08:13:50 MEZ schrieb Mechtilde :
> >the same
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!
Hello Devs!
You're receiving this email because you are subscribed to one or more
Apache developer email lists.
I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago. It will be held May 13th and 14th at
three bars in the Logan Square
> 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 is this... never tried it though:
> 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
it does't build with epm 4.2 too. As I described before it works under Debian
8. So I habe no idea where to start with bisect.
Mechtilde
Am 15. Januar 2019 08:13:50 MEZ schrieb Mechtilde :
>the same revision buids under Debian 8 with epm version 3.7 which is
>shipped in the source code.
>
Hi Peter,
Am 15.01.19 um 08:38 schrieb Peter Kovacs:
> Hello all,
>
> I committed a change to ooo_sites and after 6h the changes are still not
> visible.
>
> Are there additional steps needed?
As Jörg already wrote, the CMS needs an additional step of publishing.
The changes look good to me and
Hello,
> -Original Message-
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Tuesday, January 15, 2019 8:39 AM
> To: dev
> Subject: what do i need to do to update our static websides
>
> Hello all,
>
> I committed a change to ooo_sites and after 6h the changes
> are still not
>
37 matches
Mail list logo