Re: Release-Planung

2016-09-20 Thread Dave
Danke habe den Blog gerade gelesen. Das macht einem Mut!

On Wednesday, 21 September 2016, Dr. Michael Stehmann <
anw...@rechtsanwalt-stehmann.de> wrote:

> Hallo,
>
> wer etwas über die Release-Planung unseres Projekts erfahren will, aber
> sich nicht durch die internationale dev-ML lesen möchte:
>
> https://blogs.apache.org/OOo/entry/stop_the_lazy_season_start
>
> Es ist nur ein grober Aufriss, aber es gilt auch das Motto: Erst wenn es
> fertig ist, wird es verbreitet.
>
> Gruß
> Michael
>
>


Re: Ready to setup release build machines?

2016-09-20 Thread Ariel Constenla-Haile
On Wed, Sep 21, 2016 at 12:10:29AM +0200, Andrea Pescetti wrote:
> On 04/09/2016 Andrea Pescetti wrote:
> >https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
> >Ideally, this would become a semi-scriptable recipe for preparing a
> >"standard" CentOS 5 VM for building OpenOffice releases, at least for
> >the 4.1.x series
> 
> The recipe has now been updated including some clarifications from Ariel at
> 
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
> 
> and (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 with CentOS 5 are too old.

With the commit for this bug, in AOO413 you can use Perl from CentOS
repos, see
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements

yum install \
perl-libwww-perl \
perl-Archive-Zip \
perl-Digest-SHA \
perl-XML-Parser \
perl-Crypt-SSLeay \


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: Digital signature


RE: Tools for building and checking a release candidate

2016-09-20 Thread Dennis E. Hamilton


> -Original Message-
> From: Andrea Pescetti [mailto:pesce...@apache.org]
> Sent: Tuesday, September 20, 2016 15:59
> To: dev@openoffice.apache.org
> Subject: Re: Tools for building and checking a release candidate
> 
> Dennis E. Hamilton wrote:
> >> From: Andrea Pescetti
> >> We are signing. ... Just, we do it in a way that Windows
> >> doesn't like.
> >
> > It is not about Windows not liking the PGP signatures.  It never sees
> them.
> 
> Sure. I wrote that Windows doesn't like the way we sign (detached), not
> that it doesn't like the signatures.
> 
> > To favorably compare a procedure that requires expert users to perform
> manually seems odd to me.
> 
> Just to be clear, and I have written it multiple times:
> Windows-compatible signatures would be nice to have. On the other hand,
> this would also need significant effort; and experience shows that it is
> not a major priority for Windows users (we've received only a few
> requests about it; Mac users, on the contrary, seem to ask for it more
> often, probably because of a stricter behavior on Mac OS X).
[orcmid] 

So, there is no need to provide greater user protection because casual users 
don't [know to] ask for it?

And the Operating System doesn't complain strongly enough?  

I think this would also give us more ability to discourage unscrupulous 
producers from wrapping AOO in their own .exe for their mercantile purposes, 
something that concerns us as a project.  We fairly regularly have to request 
that users be certain that they get their downloads from mirrors that we feed.

Most of all it demonstrates care in an observable form and is an aspect of 
being trustworthy.

I agree there are activities that trump this, such as data-loss crashers, 
saved-file corruption cases, and security-vulnerability fixes. 

I think we should keep our eye on this. 

 - Dennis


> 
> Regards,
>Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



RE: Tools for building and checking a release candidate

2016-09-20 Thread Dennis E. Hamilton


> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Tuesday, September 20, 2016 15:18
> To: dev@openoffice.apache.org
> Subject: RE: Tools for building and checking a release candidate
> 
> 
> 
> > -Original Message-
> > From: Andrea Pescetti [mailto:pesce...@apache.org]
> > Sent: Tuesday, September 20, 2016 14:37
> > To: dev@openoffice.apache.org
> > Subject: Re: Tools for building and checking a release candidate
> >
[ ... ]
> > We are signing. We always did. Just, we do it in a way that Windows
> > doesn't like. The "signed installers" discussion comes from this
> > incompatibility.
> [orcmid]
> 
> A little touch-up on the situation.
> 
> It is not about Windows not liking the PGP signatures.  It never sees
> them.
> What Windows sees are Windows-specified signatures embedded in the
> downloaded software itself (and also on the DLLs and such that are
> installed.
> 
> These are part of the file properties.  Those properties that can be
> inspected by users and, even better, operating system software.  That is
> what we don't do (although other producers of OpenOffice-lineage
> software do).
> 
> To favorably compare a procedure that requires expert users to perform
> manually seems odd to me.
[orcmid] 

PS. What the embedded signature provides to not-so-expert users is an easy way 
to check that a download from any site is signed by an authentic source.  It 
also may pacify anti-virus and browser download tools. Those message requesting 
administrator permission to perform an install will also be more re-assuring.

Although not so foolproof *after* a download has been installed, with a little 
more expertise users can also verify whether soffice.exe, etc., are also 
authentic.   That could be true even though an installer delivered 
adware/malware on the side.

> 
> > But, security-wise, we are already providing a detached
> > GPG (or PGP) signature for all files. See
> > https://www.apache.org/dev/release-signing#sign-release
> >
> > Regards,
> >Andrea.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Last call for 4.1.3 patches

2016-09-20 Thread 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 available?

I forgot:
my system is Debian 64-bit


Buildbots aside (they were not working last time I checked), you can use 
the 4.1.3-dev builds at


http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761552/

...and I've already spammed three different threads, so I'll stop here!

DEBs are completely untested, so testing is at your own risk as usual.

Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Tools for building and checking a release candidate

2016-09-20 Thread Andrea Pescetti

Dennis E. Hamilton wrote:

From: Andrea Pescetti
We are signing. ... Just, we do it in a way that Windows
doesn't like.


It is not about Windows not liking the PGP signatures.  It never sees them.


Sure. I wrote that Windows doesn't like the way we sign (detached), not 
that it doesn't like the signatures.



To favorably compare a procedure that requires expert users to perform manually 
seems odd to me.


Just to be clear, and I have written it multiple times: 
Windows-compatible signatures would be nice to have. On the other hand, 
this would also need significant effort; and experience shows that it is 
not a major priority for Windows users (we've received only a few 
requests about it; Mac users, on the contrary, seem to ask for it more 
often, probably because of a stricter behavior on Mac OS X).


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: How do all the binaries get built?

2016-09-20 Thread Andrea Pescetti

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/Building_Guide_AOO/Step_by_step#CentOS_5
on a 32-bit VM, and adapting -it's trivial- the script at
http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/
to check that we have a good recipe to obtain Linux-32 binaries as well 
as the Linux-64 binaries I've just uploaded to

http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761552

Thanks,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



RE: Tools for building and checking a release candidate

2016-09-20 Thread Dennis E. Hamilton


> -Original Message-
> From: Andrea Pescetti [mailto:pesce...@apache.org]
> Sent: Tuesday, September 20, 2016 14:37
> To: dev@openoffice.apache.org
> Subject: Re: Tools for building and checking a release candidate
> 
> On 18/09/2016 Marcus wrote:
> > Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:
> >> Are there any tools to help put together an AOO release? If so, where
> >> are they?
> 
> We don't have any. But I've provided a script that I've just used for a
> test 4.1.3 build. It will find packages in a build tree (after the build
> has completed), arrange them in the appropriate directories, compute the
> hashes and sign.
> 
> It's currently located here:
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/
> 
> It only works on Linux-64 but it is trivial to extend it to cover
> Linux-32, probably Mac OS X and maybe also Windows (provided one has a
> Bash environment).
> 
> > Maybe Andrea can help you as he has more experience, e.g., with
> uploads
> > to Sourceforge.
> 
> Uploads to SourceForge are trivial (just a rsync); but anyway they
> happen after the tree has already been arranged properly, so they are
> unrelated to arranging the tree.
> 
> >> Each binary needs to be signed, presumably by the person building it.
> > IMHO we haven't done any signing until now - at least not officially.
> 
> We are signing. We always did. Just, we do it in a way that Windows
> doesn't like. The "signed installers" discussion comes from this
> incompatibility. 
[orcmid] 

A little touch-up on the situation.

It is not about Windows not liking the PGP signatures.  It never sees them.
What Windows sees are Windows-specified signatures embedded in the downloaded 
software itself (and also on the DLLs and such that are installed.

These are part of the file properties.  Those properties that can be inspected 
by users and, even better, operating system software.  That is what we don't do 
(although other producers of OpenOffice-lineage software do).

To favorably compare a procedure that requires expert users to perform manually 
seems odd to me.

> But, security-wise, we are already providing a detached
> GPG (or PGP) signature for all files. See
> https://www.apache.org/dev/release-signing#sign-release
> 
> Regards,
>Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Ready to setup release build machines?

2016-09-20 Thread Andrea Pescetti

On 04/09/2016 Andrea Pescetti wrote:

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
Ideally, this would become a semi-scriptable recipe for preparing a
"standard" CentOS 5 VM for building OpenOffice releases, at least for
the 4.1.x series


The recipe has now been updated including some clarifications from Ariel at

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5

and (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 with CentOS 5 are too old.


With these fixes, I was able to build on CentOS 5 with the release build 
options.


A few resulting Linux-64 builds (English, German, Italian) are at

http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761552/

and it would be good if someone can test that they work. They already 
identify themselves as 4.1.3 since I used release options, but of course 
they are dev builds as the directory name implies.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Tools for building and checking a release candidate

2016-09-20 Thread Patricia Shanahan

On 9/20/2016 2:37 PM, Andrea Pescetti wrote:

On 18/09/2016 Marcus wrote:

Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:

Are there any tools to help put together an AOO release? If so, where
are they?


We don't have any. But I've provided a script that I've just used for a
test 4.1.3 build. It will find packages in a build tree (after the build
has completed), arrange them in the appropriate directories, compute the
hashes and sign.

It's currently located here:
http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/

It only works on Linux-64 but it is trivial to extend it to cover
Linux-32, probably Mac OS X and maybe also Windows (provided one has a
Bash environment).


Cygwin provides a bash environment. I was asking because I was thinking 
of writing a similar script, but did not want to reinvent the wheel.





Maybe Andrea can help you as he has more experience, e.g., with uploads
to Sourceforge.


Uploads to SourceForge are trivial (just a rsync); but anyway they
happen after the tree has already been arranged properly, so they are
unrelated to arranging the tree.


Each binary needs to be signed, presumably by the person building it.

IMHO we haven't done any signing until now - at least not officially.


We are signing. We always did. Just, we do it in a way that Windows
doesn't like. The "signed installers" discussion comes from this
incompatibility. But, security-wise, we are already providing a detached
GPG (or PGP) signature for all files. See
https://www.apache.org/dev/release-signing#sign-release

Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Tools for building and checking a release candidate

2016-09-20 Thread Andrea Pescetti

On 18/09/2016 Marcus wrote:

Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:

Are there any tools to help put together an AOO release? If so, where
are they?


We don't have any. But I've provided a script that I've just used for a 
test 4.1.3 build. It will find packages in a build tree (after the build 
has completed), arrange them in the appropriate directories, compute the 
hashes and sign.


It's currently located here:
http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/

It only works on Linux-64 but it is trivial to extend it to cover 
Linux-32, probably Mac OS X and maybe also Windows (provided one has a 
Bash environment).



Maybe Andrea can help you as he has more experience, e.g., with uploads
to Sourceforge.


Uploads to SourceForge are trivial (just a rsync); but anyway they 
happen after the tree has already been arranged properly, so they are 
unrelated to arranging the tree.



Each binary needs to be signed, presumably by the person building it.

IMHO we haven't done any signing until now - at least not officially.


We are signing. We always did. Just, we do it in a way that Windows 
doesn't like. The "signed installers" discussion comes from this 
incompatibility. But, security-wise, we are already providing a detached 
GPG (or PGP) signature for all files. See

https://www.apache.org/dev/release-signing#sign-release

Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Help building custom app using headless UNO OpenOffice 4.1.2 SDK using C++ Ubunutu 14.04.01 LTS Server

2016-09-20 Thread Jim Hogg
I seek advice on what is causing a server fault in our code. I have a "generic"
part of our spreadsheet server app for connecting to the Open Office SDK
4.1.2 service. The "generic" part is represented in the code fragment below
(*Code*). We require however the XDesktop and XComponentLoader features to
work, but they are giving us problems. What have I done wrongly? How do I
get them to work or what is a better alternative?

I provide a summary and example.cxx code below before the segmentation
fault occurs.


*Summary: *

Sample application fails at the end with a segmentation violation with
backtrace:

#0  0x7489b723 in cpp_vtable_call ()
   from /opt/libreoffice5.2/program/libgcc3_uno.so
#1  0x748a26ea in privateSnippetExecutor ()
   from /opt/libreoffice5.2/program/libgcc3_uno.so
#2  0x00401ea9 in main ()

The simple example was built adapting the Libreoffice 5.2 SDK. Code and
makefile below.

The same code, embedded into a larger application, fails at the
XComponentLoader call --- with the same backtrace.

A somewhat similar example fails on the
xComponentLoader->loadComponentFromURL call (backtrace terminating on that
line; the file and directory parameters passed into that method look good
on inspection; flag is 0, property sequence is void).

We have tried this on Libreoffice 4 (as per ubuntu trusty repo) and on
headless Openoffice SDK 4.1.2, with very similar results. Despite the fact
that the simple example code runs to the end before crashing, we suspect
based on the other evidence an issue with XComponentLoader.

We have tried many different ways of compiling the source code but cannot
succeed in getting a successful built.  Any ideas about what might be
causing the problem would be gratefully appreaciated.


*Code *(ooexample.cxx)*:*

#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::bridge;
using namespace com::sun::star::beans;
using namespace com::sun::star::frame;
using namespace com::sun::star::container;
using namespace com::sun::star::document;
using namespace rtl;
using namespace cppu;

#define DIAG(s) printf("%s\n",s)
#define OOCHECKREF(x) if (!x.is()){printf("Error: "#x"\n");return 1;}

int main (int argc, char *argv[]) {
  try {
DIAG("mComponentContext");
Reference< XComponentContext > mComponentContext
  = defaultBootstrap_InitialComponentContext();

DIAG("mServiceManager");
Reference< XMultiComponentFactory > mServiceManager
  = mComponentContext->getServiceManager();

DIAG("rResolverInstance");
Reference< XInterface > rResolverInstance
  = mServiceManager->createInstanceWithContext (
OUString::createFromAscii("com.sun.star.bridge.UnoUrlResolver") ,
mComponentContext);

DIAG("rResolver");
Reference< XUnoUrlResolver > rResolver (rResolverInstance, UNO_QUERY);
OOCHECKREF(rResolver)

DIAG("rOfficeInstance");Reference< XInterface > rOfficeInstance
  = rResolver->resolve (
OUString::createFromAscii
("uno:socket,host=localhost,port=8199;urp;StarOffice.ServiceManager")) ;
OOCHECKREF(rOfficeInstance)

DIAG("rOfficeServiceManager");
Reference< XMultiServiceFactory > rOfficeServiceManager (
  rOfficeInstance, UNO_QUERY);
OOCHECKREF(rOfficeServiceManager)

DIAG("xPropSet");
Reference< XPropertySet > xPropSet (rOfficeInstance, UNO_QUERY) ;
  xPropSet->getPropertyValue
(OUString::createFromAscii("DefaultContext"))  >>= mComponentContext;

DIAG("xMultiComponentFactoryServer");
Reference< XMultiComponentFactory > xMultiComponentFactoryServer(
  mComponentContext->getServiceManager());

DIAG("rDesktop");
Reference rDesktop = rOfficeServiceManager->createInstance(
  OUString::createFromAscii("com.sun.star.frame.Desktop"));
OOCHECKREF(rDesktop)

DIAG("mComponentLoader");
Reference< XComponentLoader > mComponentLoader (rDesktop, UNO_QUERY);
OOCHECKREF(mComponentLoader)

DIAG("rFiltersInt");
Reference< XInterface > rFiltersInt =
rOfficeServiceManager->createInstance(
OUString::createFromAscii("com.sun.star.document.FilterFactory"));
OOCHECKREF(rFiltersInt)

DIAG("mFilterFactory");
Reference mFilterFactory = Reference< XNameAccess
>(rFiltersInt, UNO_QUERY);
OOCHECKREF(mFilterFactory)

DIAG("rTypeDetectInt");
Reference< XInterface > rTypeDetectInt =
rOfficeServiceManager->createInstance(
OUString::createFromAscii("com.sun.star.document.TypeDetection"));
OOCHECKREF(rTypeDetectInt)

DIAG("mTypeDetect");
Reference< XTypeDetection > mTypeDetect = Reference< XTypeDetection
>(rTypeDetectInt, UNO_QUERY);
OOCHECKREF(mTypeDetect)

DIAG ("Connected successfully to the office - press enter to exit");
getchar();
  } catch (Exception ) {
OString o = OUStringToOString 

Re: New blog post about the the upcoming 4.1.3 release

2016-09-20 Thread Marcus

Am 09/20/2016 09:33 PM, schrieb Matthias Seidel:

I posted the link on "the official Google+ Community for the Apache
OpenOffice project"

https://plus.google.com/u/0/communities/103683488250592271079


Thanks

Marcus




Am 20.09.2016 um 21:14 schrieb Marcus:

I've created a new blog post about the upcoming release Apache
OpenOffice 4.1.3 that we are currently planning. No more words here,
read there:

https://blogs.apache.org/OOo/


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Apache OpenOffice on google+

2016-09-20 Thread Marcus

Am 09/19/2016 01:11 PM, schrieb Matthias Seidel:

Is anyone actually moderating the AOO-profile on google+? (This
mailadress is listed as contact)
https://plus.google.com/u/0/+openoffice/posts


IMHO Rob Weir has managed this until he has left. I don't know who is 
managing this now or is able to access the account. Does anybody else know?



It has been quite active sometimes but now there is no news since
29.10.2015.

Maybe a good place to announce the upcoming 4.1.3?


Yes, sure. Thanks in the meantime. :-)

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: New blog post about the the upcoming 4.1.3 release

2016-09-20 Thread Matthias Seidel
I posted the link on "the official Google+ Community for the Apache
OpenOffice project"

https://plus.google.com/u/0/communities/103683488250592271079

Matthias


Am 20.09.2016 um 21:14 schrieb Marcus:
> I've created a new blog post about the upcoming release Apache
> OpenOffice 4.1.3 that we are currently planning. No more words here,
> read there:
>
> https://blogs.apache.org/OOo/
>
> Marcus
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature


New blog post about the the upcoming 4.1.3 release

2016-09-20 Thread Marcus
I've created a new blog post about the upcoming release Apache 
OpenOffice 4.1.3 that we are currently planning. No more words here, 
read there:


https://blogs.apache.org/OOo/

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Reporting broken download link

2016-09-20 Thread Marcus

Am 09/20/2016 03:47 PM, schrieb Ferry Winkler:


Problem description

Exchange this text to describe the problem

(What does not work? What do you expect?)

Browser variables

Values

[...]

My PC has crased, and I can’t download it, because the message is, account 
already excist


I cannot reproduce the reported problem.

When the PC is restarted - or in the worst case new installed - it 
should be possible to download OpenOffice. You don't need any user 
account or serial number or registration for downloading, starting or 
running the software.


Please try again. Maybe it was just a temporarily problem with something.

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [RESULT][VOTE] Recommend Marcus Lange (marcus) as the New Vice President for Apache OpenOffice

2016-09-20 Thread Peter Kovacs
I am looking also forward to work with everybody. I voted to show my
interest in AOO but I am new and I did not feel I can vote now.
Still I am super excited!

Marcus  schrieb am Mo., 19. Sep. 2016, 21:05:

> A big thank you to all of you for your votes, that you are putting your
> trust in me.
>
> However, I'm especially happy about the amount of votes (regardless of
> where in the ballot the cross was made). For me this should clearly show
> that the interest of a healthy Apache OpenOffice is still of a big
> interest. Now it also depends on all of us to fill this interest with life.
>
> I'm happy to go on to work together with you. :-)
>
> Marcus
>
>
>
> Am 09/19/2016 06:11 PM, schrieb Dennis E. Hamilton:
> > [BCC to PMC]
> >
> > The [VOTE] to recommend Marcus Lange (marcus) as the New Vice President
> for Apache OpenOffice has passed.
> >
> > Tally
> >
> > +1 Jan Høydahl
> > +1 Dennis E. Hamilton
> > +1 Gavin McDonald
> > +1 Herbert Duerr
> > +1 Patricia Shanahan
> > +1 Louis Suárez-Potts
> > +1 Mechtilde Stehmann
> > +1 Stuart Swales
> > +1 Kazunari Hirano
> > +1 Dr. Michael Stehmann
> > +1 Carl Marcum
> > +1 Andrea Pescetti
> > +1 Jörg Schmidt
> > +1 Olaf Felka
> > +1 Dave Fisher
> > +1 Dave Barton
> > +1 Regina Henschel
> > +1 Ariel Constenla-Haile
> > +1 Roberto Galoppini
> > +1 Phillip Rhodes
> > +1 Keith N. McKenna
> >
> >  0 Marcus Lange
> >  0 Peter Kovacs
> >
> > 21  +1 Approvals
> >  2   0 Abstentions
> >  0  -1 Disapprovals
> >
> >
> > I will submit the resolution to the Board of the Apache Software
> Foundation for consideration at the Wednesday, 2016-09-21 meeting.
> >
> >   - Dennis
> >
> >> -Original Message-
> >> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> >> Sent: Thursday, September 15, 2016 08:36
> >> To: dev@openoffice.apache.org
> >> Subject: [VOTE] Recommend Marcus Lange (marcus) as the New Vice
> >> President for Apache OpenOffice
> >>
> >> [BCC to PMC]
> >>
> >>  RESOLUTION: That Marcus Lange (marcus) be recommended to the
> >>  Apache Software Foundation Board to serve as Vice President
> >>  for Apache OpenOffice.
> >>
> >> The Vice President for Apache OpenOffice serves in accordance with and
> >> subject to the direction of the Board of Directors and the Bylaws of the
> >> Foundation.  The Vice President for Apache OpenOffice is the Chair of
> >> the OpenOffice Project Management Committee.
> >>
> >> Please vote by reply to this dev@-list thread on approval of the
> >> resolution.
> >>
> >>   [  ] +1 Approve
> >>   [  ]  0 Abstain
> >>   [  ] -1 Disapprove, with explanation
> >>
> >> This is a procedural vote and a majority of binding votes is sufficient
> >> to carry the resolution.
> >>
> >> Please do not do anything but [VOTE] (with any -1 explanations) on this
> >> thread.
> >>
> >> To discuss this vote or the process, please use a [DISCUSS][VOTE] reply
> >> rather than discussing on the [VOTE] thread.
> >>
> >> The [VOTE] will conclude no sooner than Monday, 2016-09-19T16:00Z.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
> --

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.


Re: Become the IMAP client for documents [Re: Differentiate or Die]

2016-09-20 Thread Peter Kovacs
Yeah I mean weird.

Xen  schrieb am So., 18. Sep. 2016, 15:17:

> Peter Kovacs schreef op 18-09-2016 5:38:
>
> >> I don't know how much can be gained by simply using an alternative
> >> that is in essence, the same kind of program. I still won't have cloud
> >> access and will be far away from using something like Google Drive or
> >> OneDrive.
> > btw. have you tried dropbox?
> > they have an official Linux client.
>
>
> I wouldn't really ever feel safe with Dropbox.
>
> That's just disaster waiting to happen, in a way.
>
>
>
> > I recommend the documentary: indi games: the movie. Gives you an Idea
> > on why people do wired things.
>
> You mean weird?
>
> I am not really talking about those kinda guys. I am really talking
> about games that have no market at all. Downloading the film though.
> When Diablo II was released it was not a many-million-dollar budget
> game. Of course they had professional musicians and all of that.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
> --

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.


Reporting broken download link

2016-09-20 Thread Ferry Winkler

Problem description

Exchange this text to describe the problem

(What does not work? What do you expect?)

Browser variables

Values

navigator.appCodeName

Mozilla

navigator.appName

Netscape

navigator.appVersion

5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 
2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; rv:11.0) like Gecko

navigator.platform

Win32

navigator.oscpu

undefined

navigator.cpuClass

x86

navigator.product

Gecko

navigator.productSub

undefined

navigator.vendor

navigator.vendorSub

undefined

navigator.language

nl-NL

navigator.browserLanguage

nl-NL

navigator.userLanguage

nl-NL

navigator.systemLanguage

nl-NL

navigator.userAgent

Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 
2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; rv:11.0) like Gecko

Debian / Ubuntu / IceWeasel ?

No / No / No

Stable Release



JavaScript functions/variables

Values

Language ISO code

Language ISO code (from select box)

Release matrix platform position (full)

Release matrix platform position (lp)

Release matrix platform array data

Release matrix language array data

UI platform name

UI platform name (not supported)

Platform (short)

URL platform name (full)

URL platform name (lp)

URL platform name (from select box)

Version (from select box)

File name (full)

File name (lp)

File extension

File size (full) (MByte)

File size (lp) (MByte)

Release info

Download file link (full)

Download file link (lp)

Checksum file link (full) (here for MD5)

Checksum file link (lp) (here for MD5)

Base URL to Sourceforge.net

Base URL to Apache Archive

getLinkSelection() (download URL)

isLanguageSupported() (true/false) ?

Show the sub-box (true/false) ?

General error (true/false) ?

My PC has crased, and I can’t download it, because the message is, account 
already excist

Verzonden vanuit Mail voor 
Windows 10



Re: building on Windows 10 breaks at guistdio.exe

2016-09-20 Thread Patricia Shanahan

On 9/20/2016 12:56 AM, John D'Orazio wrote:

On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile 
wrote:


On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote:

4.1.3 does have changes to the language library URLs. Has anyone else

done a

build that included Italian?


His logs say aoo-trunk, so I assume John isn't building branch AOO413.
NSIS >= 3.* is only on that branch.

In fact I followed the instructions I found at

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10

   - Check out source from Apache SVN repository

   svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk
   cd aoo-trunk/main


So yes I am evidently building from aoo-trunk. I'll update the wiki with
the info about NSIS >= 3.* being compatible only with the AOO413 branch.


Next person to edit the step-by-step should add a note clarifying the
checkout. Specifically, replace "trunk" with "branches/AOO413" to get
the 4.1.3 source.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: building on Windows 10 breaks at guistdio.exe

2016-09-20 Thread John D'Orazio
On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile 
wrote:

> On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote:
> > 4.1.3 does have changes to the language library URLs. Has anyone else
> done a
> > build that included Italian?
>
> His logs say aoo-trunk, so I assume John isn't building branch AOO413.
> NSIS >= 3.* is only on that branch.
>
> In fact I followed the instructions I found at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10

   - Check out source from Apache SVN repository

   svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk
   cd aoo-trunk/main


So yes I am evidently building from aoo-trunk. I'll update the wiki with
the info about NSIS >= 3.* being compatible only with the AOO413 branch.


> Regards
> --
> Ariel Constenla-Haile
>

-- 
don John R. D'Orazio


Re: building on Windows 10 breaks at guistdio.exe

2016-09-20 Thread John D'Orazio
On Tue, Sep 20, 2016 at 7:44 AM, Ariel Constenla-Haile 
wrote:

> On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote:
> > I wound up building in stages, since the build was breaking here and
> there.
> > I just picked it up from where it left off as I fixed things. So I don't
> > have a single output... unless there is a log file that collects various
> > build stages together into one single output?
> > I would also recommend installing as many packages in cygwin as possible
> > without going through the extra step of installing lynx or apt-cyg...
> While
> > that does make the environment more similar to a linux build environment,
> > it's still an extra step and I believe it could be indicated as a second
> > possibliity. Somewhere in the Step by Step guide I added which packages
> to
> > choose in the cygwin interface if installing them from the cygwin
> > interface. I think installing the packages from the cygwin interface
> should
> > be indicated as the first step to take when first installing cygwin,
> adding
> > all the necessary packages along with the first install.
> > The only package I couldn't find from the cygwin interface was the Perl
> > LWP::UserAgent package, so I installed that using "cpan -i
> LWP::UserAgent".
>
> That is perl-LWP-Protocol-https, please see the updated version of
> https://wiki.openoffice.org/wiki/Documentation/Building_
> Guide_AOO#General_Build_Requirements


Yes in fact I saw that right after my last message and I've already updated
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10

The process indicated in this last page should be a lot cleaner now I
believe.


> Regards
> --
> Ariel Constenla-Haile

-- 
John R. D'Orazio