Re: Task #d7d4b55f: Profile Tool Utility (Windows) Project: openoffice

[Peter kovacs]

Great. So which direction are you interested in?
You want to Do something in the scripting area?
We could maybe use forum developer.
Or do you want to go into the open office code itself? - if you want to go in 
this direction you should make yourself familiar with the build environment we 
currently use.
We have a guide on the wiki.

Remember you decide what you want to do. I am only a servant leader who does 
his best to enable you to reach your goals.
Others might help too as they seem fit.
Please bring patience. Have no fear in asking questions. The journey is a bit 
more difficult the way we work, but way more rewarding.

Wiki entries for building oo:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

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


All the best
Peter

Am 22. März 2018 22:47:00 MEZ schrieb bolanle egbedokun 
<bolanlebenja...@gmail.com>:
>Hi Peter,
>
>Thank you for your prompt respond & apologies for the delaySure,
>I'd be
>happy to help.
>
>I'm eager to contribute to Open Source Projects and I will really
>appreciate if you will guide me through.
>
>Looking forward to hearing from you.
>
>
>
>
>
>
>
>Regards.
>
>
>
>
>
>On Mar 18, 2018 12:08, "Peter Kovacs" <pe...@apache.org> wrote:
>
>> Welcome Bolanle Egbedokun!
>>
>> I was not aware of this request. lol.
>>
>> To be honest I am not sure if we have already solved the request as
>such.
>> I think there has been a discussion about adding something like this
>to AOO
>> 4.1.5. But can not remember its resolution. Anyone else remember
>maybe? It
>> was a script from a community Member Hanah or something similar. I
>forgot
>> the name I am sorry.
>>
>> I try now to figure it out, what the situation is.
>>
>>
>> In the mean while, would you be willing to help us in other topics?
>If so
>> where do you want to help?
>>
>> We have a lot of topics to solve. I assume you would like to code
>> something, right?
>>
>> We can find something that you like. I am sure.
>>
>>
>> All the best
>>
>> Peter
>>
>>
>> On 16.03.2018 11:32, bolanle egbedokun wrote:
>>
>>> Hi, Good day,
>>>
>>> Bolanle Egbedokun is my name from Nigeria,  A full-time Data
>>> Scientist/Analyst that utilizes machine learning and Business
>Intelligence
>>> skills for advance cutting-edge technologies, developing robust
>>> applications.
>>>
>>> I came across this project on Apache opensource website and I'm
>willing to
>>> contribute.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Regards.
>>>
>>>
>>

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

Re: Status on 4.2.0?

[Peter Kovacs]

Why do we need nsis again?

Am 3. März 2018 12:39:32 MEZ schrieb Matthias Seidel 
<matthias.sei...@hamburg.de>:
>Hi Peter,
>
>Am 01.03.2018 um 07:38 schrieb Peter kovacs:
>> Hello all,
>>
>> What is the current status on 4.2.0?
>> I have seen one bug that fires when opening a document. We got more?
>
>You probably think of:
>https://bz.apache.org/ooo/show_bug.cgi?id=127315
>
>I would like to have this one solved: ;-)
>https://bz.apache.org/ooo/show_bug.cgi?id=127628
>
>Although it is not a critical one it is a regression on Windows since
>4.1.3 and it confuses new users.
>
>Regards,
>   Matthias
>
>>
>> All the best
>> Peter
>>
>> -
>> 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: Status on 4.2.0?

[Peter Kovacs]

I think it is better to renew the installer completely. I have found a open 
source framework that simplifies the creation of the installer and builds the 
msi file for us.
It offers .net framework for writing a installer screens (MSI does not provide 
such a thing). The tutorials I have read looked pretty streight forward, at 
least for the standard installer stuff.

I think I read that you can include a dependance msi package in the msi package.
But I forgot again. I looked into msi a month ago. The last month has been 
quite intense for me.

We could deliver a single MSI file in future and even create the patch file 
from it.

I am currently unsure concerning the package signing, but once we have a pure 
MSI  setup it should be easy to add too, right?

 

Am 3. März 2018 16:55:32 MEZ schrieb Pedro Lino :
>
>> Technically seen:
>> To unpack the installation files and to start the installation
>with MSI.
>> 
>> Historically seen:
>> I don't know! ;-)
>> 
>
>
>The nsis installer extracts and runs the MSVC runtime libraries
>installer before running the AOO installer. Since AOO is compiled with
>MSVC it requires these libraries are installed first. I don't know how
>TDF got rid of that step  but possibly they are including the MSVC
>libraries needed in the program folder?
>
>
>Maybe AOO can do the same and skip the nsis installer?

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

build script perl code strangeness

[Peter Kovacs]

Hi all,


I know perl, but I am not a real expert that knows all possible styles.
The following code looks doubious to me (build.pl line 265).

   provide_consistency() if (defined $ENV{CWS_WORK_STAMP} &&
   defined($ENV{COMMON_ENV_TOOLS}));

I would assume that provide_consistency is always called, and the if 
clause does nothing. What sense has this code?
Or is perl now that smart to read it like a sentence? - Have no hint for 
this. But I rather ask.


Thanks.

All the best
Peter

Re: Openoffice and unsupported gstreamer 0.10 branch (for openoffice libavmediagst.so library)

[Peter Kovacs]

sorry dont have much time. I added a bug to bugtracker and added roughly 
the situation.


Thanks Damjan, and thanks everyone else.


can someone look at the bugs

https://bz.apache.org/ooo/show_bug.cgi?id=44114

and

https://bz.apache.org/ooo/show_bug.cgi?id=89802


I think they are related and can be closed?!


All the best

Peter


On 02.03.2018 07:14, Damjan Jovanovic wrote:

I finally cracked it. The gstreamer pipeline gets created early, during
construction of the avmedia/source/gstreamer's Player object, yet the
window to play in is only created later, when createPlayerWindow() is
called. To use that window and thus embed video into the document, we have
to set that window's handle to the GstVideoOverlay using
gst_video_overlay_set_window_handle(), but by then it's too late. Either
the pipeline creation would have to be deferred until createPlayerWindow(),
when we know the window to use, or we would have to switch windows
with gst_video_overlay_set_window_handle() a live pipeline. I've done the
latter and it works well. I don't know how it ever worked before, maybe in
gstreamer 0.1 the "prepare-window-handle" event is generated during
createPlayerWindow() but in 1.0 it isn't.

My changes have been committed to SVN trunk in revision 1825700.

Torokhov, Jose, Peter: thank you for all your support. Please test and
report any problems.

Damjan

On Thu, Mar 1, 2018 at 9:25 AM, Damjan Jovanovic  wrote:


Unfortunately it looks like the problem is harder than just getting it to
build. Even after fixing some more APIs and getting it to play, a separate
player window is created. To get the player window to embed like it should,
we need to set the X window id on the GstVideoOverlay using
gst_video_overlay_set_window_handle() when a "prepare-window-handle"
event is delivered for which 
gst_is_video_overlay_prepare_window_handle_message()
returns true. But for some mysterious reason 
gst_is_video_overlay_prepare_window_handle_message()
never returns true. Forcefully setting the X window id on all events does
get it to embed, badly, with lots of warnings, and the window gets
distorted when scrolling and doesn't respond to mouse clicks .

Damjan


On Thu, Mar 1, 2018 at 4:53 AM, Damjan Jovanovic 
wrote:


Thank you. The video plays, but in a separate window instead of being
embedded in the document. I'll continue trying.

Distributing the library separately from the rest of AOO would be
difficult. Binary compatibility between Ubuntu and Gentoo, bitness, trunk
vs 4.1.5. New UNO components also have to be registered in AOO somehow; I
only know how to do it with .component files at compile time.

It will likely only end up in SVN trunk, possibly version 4.2.0.


On Thu, Mar 1, 2018 at 2:01 AM, Torokhov Sergey 
wrote:


Hello,

I created simple presentation file with title and video frame
("Agent 237:operation barbershop" from Blender Animation Studio).

https://yadi.sk/d/shOKuCcS3StDk

The archive contains 327.odp and 327.webm files that must be placed in
the same directory before presentation file .odp is opening.

The video is playing automatically after pressing F5 key (fullscreen
presentation mode). Or after pressing "Play" button on the bar that
usually appears at the bottom then video-frame of presentation is
selected.
I't work for me in current Apache OpenOffice 4.1.5 and
gstreamer-plugins:0.10.

As I use Gentoo I installed "gst-plugins-meta:0.10" with next options:

USE="ffmpeg quicktime http wavpack dv dvb vcd musepack vpx oss libass
lame theora v4l" emerge gst-plugins-meta:0.10

Also I installed "gst-plugins-ivorbis:0.10" and
"gst-plugins-pango:0.10".


Could you also share rebuilded library for testing? Is it compatible
with current AOO 4.1.5 build?

Thank yo in advance.

--
Sergey



On Wed, 28 Feb 2018 19:56:42 +0200
Damjan Jovanovic  wrote:


I've successfully patched our gstreamer plugin to build with
gstreamer-1.0, but how do I test it? Does someone have a sample
document that uses gstreamer?

The patch is attached for anyone interested. Parts may still be
wrong, eg. filter names. Changes between GStreamer 0.1 and 1.0 are
documented here:
https://gstreamer.freedesktop.org/documentation/application-

development/appendix/porting-1-0.html

https://cgit.freedesktop.org/gstreamer/gstreamer/plain/docs/

random/porting-to-1.0.txt



On Wed, Feb 28, 2018 at 10:22 AM, Damjan Jovanovic 
wrote:


Hi

I've begun having a look.

We currently test for gstreamer in configure.ac but don't use the
result, re-running pkg-config in a main/avmedia's makefile.

Changing the version number to 1.0 breaks the build due a missing
header file. Removing that "#include" gets it a little further, but
it breaks due to changed gstreamer API functions. There is also
lots of warnings about deprecated GDK functions. I'll continue
trying later.

We should really get rid of gstreamer 0.1 ASAP one way or the
other: given how it's been 

Re: Other build ideas (was: Re: Windows Build Environment futures

[Peter Kovacs]

Hi Damjan,

I o not understand the MSVC part. If we separate UNO it's own world. 
(Independent of the Idea to spin it of into its own project)


will the update of the MSVC be easier?


All the best

Peter


On 10/5/18 10:15 AM, Damjan Jovanovic wrote:

Hi

I now have a few other ideas regarding the building story.

The gbuild migration has been extraordinarily long and painful. Sadly I've
had to learn so much about gbuild, and implement so many new features in it
(symlinks, UNO IDL, Ant, bison, flex, now assembly...), that I am getting
good at it now :(. A lot of what I've done would have to be reimplemented
on SCons. But there are advantages to redoing stuff in SCons: for example,
we could run code in Python instead of calling external tools like awk, tr
and sed, and thus gain more portability, reduce dependencies, and ditch
Cygwin.

However I consider SCons lower priority than a 64 bit Windows build, and a
newer MSVC (especially given our MSVC version is now unavailable!).

Also one of the things that's made work on all of those projects difficult
is the sheer size of AOO, the number and diversity of modules. One of my
ideas is to split up AOO into 2 layers: an UNO layer at the bottom, and an
office layer at the top. This is something that's been in the pipeline from
the OOo days, and at one stage I think OOo was distributed with a separate
UNO installation, and there's even a file in main/ure/source/README that
describes how the split would be done. These layers would be in separate
directories, along the lines of ext_sources/, main/ and test/ now, and
would build separately: first UNO, then office.

How does this help? Changes can be contained. Different build systems could
be experimented with, for each. A Win64 bit UNO could be developed and
tested before we begin porting office modules to Win64. Ultimately, UNO is
a general framework for cross-platform multi-language component-based
development, similar to Microsoft's COM and Mozilla's XPCOM, and I think it
should be a completely separate project, that is hosted, developed, and
packaged independently of AOO (eg. http://uno.apache.org), and is a just a
compile-time and run-time dependency for us, that we download, use, and
ship just like zlib and libjpeg.

I really think the world needs a cross-platform multi-language
component-based framework. Microsoft's COM is Windows-only, and Mozilla is
gradually getting rid of XPCOM. There are few other implementations, and we
have what seems to be the only permissively licensed one, and the only one
supporting exception handling between different languages (I think both COM
and XPCOM don't support exceptions and require return codes; the infamous
HRESULT with its bitfields).

Almost all the UNO modules are using gbuild already (it's mostly office
that is troublesome and does lots of custom things during the build :-), so
a 100% gbuild UNO can be split off soon, and UNO can then potentially start
using SCons, a newer MSVC, and/or producing a Win64 build, before office
even finishes the gbuild migration.

There is some work involved. We would have to split up configure.ac,
duplicate some of the build scripts, somehow deliver UNO files into the
office build. Quite a few of the office prj/build.lst would have to change
to not depend on the modules that move. Nothing would initially improve;
only after other changes could dependencies be reduced. Not needing Cygwin
requires both UNO and office to use SCons, a Win64 office also requires
both. The biggest initial benefit might be that since UNO doesn't change
often, rebuilding would be faster, as only office modules would rebuild.
And the office source code tree would be smaller and clearer.

On the downside, the same version of MSVC must compile both UNO and office,
as C++ symbols from different MSVC versions are incompatible. This pretty
much means we have to build UNO from source inside office.

Anyway, what do you think?

Damjan


On Sun, Sep 23, 2018 at 10:46 AM Peter Kovacs  wrote:


At the same time, the migration from Windows 32bit Version to support
64bit has been started. The build currently breaks somewhere. A
continuation would be awesome.

And we are moving the build environment from dmake to gmake. There are
65 modules left. This activity has a huge impact because all platforms
are effected. And according to Damjan, the low fruits have been already
migrated, and the ones left are not easy.

@Damjan, you still would like to migrate then to SCON after gmake, btw?
I would still like to, even I do not count my voice much, because I did
not drive this topic much. :(




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

Chat Channel (was [Discussion] Program for Sandro)

[Peter Kovacs]

Hi all,

I am traveling a lot. The classic irc channel never worked for me, 
because I get disconnects all the time.


So currently from my perspective we could set something up in threema, 
slack or discord for real time chat.


I am also open for other mobile capable options. Just keep in mind it 
has to work with a shitty german mobile connection.


If anyone knows a solution for IRC I would gladly participate in a 
channel there.



All the best

Peter

On 9/26/18 3:13 AM, sandro wrote:

Dear Peter

It is an amazing idea, very nice. Maybe one of those kind services ( Dropbox or 
Google) have a nice and amazing chat service so we could communicate in real 
time while working. It is nice to interact and it is glad, certainly it will 
drive us to joy.

I would like to try Dropbox and I would like to know if this service has means 
of communication in real time, like a chat?

Glad,
Sandro Suzart



De: Peter Kovacs 
Enviado: domingo, 23 de setembro de 2018 12:29
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Dear Sandro,

Glad to read about your determination. :) Lets get you doing something.

You can send it directly to my address if you like. I personally would
appreciate if we could store it somewhere more cloudy.

How about google drive or Dropbox. They offer free cloud space. And you
can setup the space easy.


Yea it is really cool that we are a cloud Project. I think it is great
that you are with us. Maybe we can make OpenOffice a bit more Cloudy. ;)

All the best

Peter

On 9/22/18 7:32 PM, sandro wrote:

Dear Peter,

It is always amazing to show my commitment and passion for this project, I feel 
that it is so good to build together that it certainly drives all of us to 
happiness.

I just have been looking for sending a work plan to you, as I told in my last 
message. I will ask an user for the wiki project.

Well, I have the wish and I feel that I am plenty able to go on with long term 
perspective with this volunteering. Because since the time schedule is flexible 
and since I can work from anywhere (school, park, home ...) there is probably 
no interference in the activity and I think that nothing will prevent me from 
collaborate. If a have to move to another city, or if I work more in another 
project, I can always collaborate; the only thing that would stop would be 
internet connection ( if I do not have it at home) but it is easy to find free 
wifi anywhere, there are libraries and other buildings that offer internet 
access for free and also a computer to access.

So I will always be here, I just was doing the work plan while handling other 
tasks (such as a university test to September, 24. It is a calculus test, 
macroeconomics test and a management test in the same week... rs). I plan to 
always collaborate with you, always hold hands.

Glad,
Sandro Suzart



De: Peter Kovacs 
Enviado: sábado, 22 de setembro de 2018 01:04
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Dear,

Have you asked a user Request? - Use a new thread for that please. -
Hope you are still with us, it would be sad if you already stop.

All the best

Peter

On 9/11/18 5:15 PM, sandro wrote:

Dear,


It is amazing, a really exciting journey that follows the pumps of heart beat 
is a glad and fantastic way, this certainly guides us through patterns of 
satisfaction.


Well, I have posted here a working schedule, also I will post a work plan of 
the WikiProject that I feel that will bring achievements to the page. I will 
upload it here because it helps and guides me for the work, and I can update it 
every 2-3 weeks.


Glad,

Sandro Suzart





De: Andrea Pescetti 
Enviado: segunda-feira, 10 de setembro de 2018 02:08
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Peter kovacs wrote:

If you see something on our wiki-pages.
You can decide on yourself. There is no real command structure here.
If you need a user for editing the wiki, just write a request here.

Right. Sandro, if we haven't created a MWiki account for you yet, please
ask here. Otherwise, please give us your username so that we can (if
needed) extend permissions for you in order to be able to do some
configuration tasks.

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

[discussion] Release process

[Peter Kovacs]

Hi Jim,

Hi Matthias,


I had a little off list discussion with Matthias about the goal of 4.1.6.

I would like to return this discussion to the list, and start a 
discussion on our process to do releases.


We have said we want to make a Release once a year and try to get in 
sync with trunk quickly by making a big jump and have a beta phase. And 
then all will be easier.


This plan is stuck, and as a reaction I have initiated a 4.1.6 in order 
to avoid security patches and updates of dependencies are affected by 
our release being stuck with this big jump.



Matthias would really like to put also more functional code and feature 
updates in. I would like to keep the 4.1.6 release as narrow as it is now.


I suggest we burry the plan in making a big jump to 4.2.0 in a single 
Jump. Instead we make a create a release process that does not get stuck 
by development as long as there are code changes that can be released.


In order to honor the stay independent from development in trunk, we 
create a release branch. In the release branch we test "development 
ready" patches. If they are fine, they move into the next scheduled release.


A release is then tailored as we are used to do today. If they are not 
okay, we revert the patch, or fix the code. Depending on severity and 
available resources.


Maybe it would be a good Idea to also limit the size of a release to a 
number of patches (i.e. 10. By that we limit the Release size for testing.)



We could do offer an early adopter build based, in order to provide a 
simple test access.


How about we try this? We could use a trello board to test the approach, 
and if this works out we talk how to change Bugzilla to follow the process.



What do you think? Any other Ideas? I am open for all. But I would like 
to get on a base where we can move.


Also a benefit I see from this approach I think is that we can let new 
people build on the release branch. Which should stay more stable then 
trunk. Especially with the updates we are currently doing within the 
build environment.



All the best

Peter



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

Re: external_debs.lst not found on 4.1.6

[Peter Kovacs]

Okay, it seems I managed to break my svn local checkout.

On 10/7/18 9:44 AM, Matthias Seidel wrote:

Hi Peter,

Maybe you are looking for "external_deps.lst"?

https://svn.apache.org/repos/asf/openoffice/branches/AOO416/main/external_deps.lst

Regards,

    Matthias


Am 07.10.2018 um 09:19 schrieb Peter Kovacs:

Hi all,

I try to move patches from trunk to 4.1.6 and found that the file
external_debs.lst is missing.

What to do with the changes? Did the file change?


all the best

Peter


-
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: Other build ideas

[Peter Kovacs]

Hi all,

I am a bit skeptical about the 2 Layer approach. OpenOffice has been 
designed in a 3 Layer Architecture. This can be seen here.


https://wiki.openoffice.org/wiki/File:ArchOverview.jpg

As this documentation states the Lower Layer does not only consists of 
the UNO Group but also of UCB, ConfigManager, GSL.


I do prefer actually to maybe build a containment along these "old" 
Layers instead of cutting UNO out. I hope it causes less refactoring work.



Of course we would not be able do start a UNO - SpinOff Project right 
away, but we would get similar advantages, with maybe less work.


We can do a Spinoff maybe later, I like the Idea in general to have some 
of the Contrsucts that make OpenOffice so awesome offer to other 
Projects in order to get people with different goals to colaborate.


our BASIC Language is also such a topic. But I think this are lower 
priorities with the project power we currently have.



Damjan, George do you see any Issues with my plan or would you prefer 
the initial Idea?



Thanks guys for the thoughts. They are really good IMHO.

On 10/5/18 8:45 PM, George Karalis wrote:

Hello everyone,

Since am new to the project and working on understanding the build process this 
past
week, I agree with Damjan that the build system needs that overhaul. I also 
agree that
a MSVC upgrade and a 64-bit windows build, is of high priority. Changing the 
build
system will take months.

As of the MSVC upgrade I have figured out how the whole configure works and I ‘m
now integrating MSVC++ 14.15 to oowintool script, and trying to integrate 
Windows 10
SDK to the configure pipeline as well. After that I 'll try to figure out the 
build errors and
fix everything to a successful build. If and when the upgrade completes, we 
should also
investigate implementing targets - if there are none - for the build tool.

e.g. To compile for windows XP, we need the Windows XP platform toolset, which 
installs
Windows 7.1 SDK, among other things and can build for Windows XP using MSCV++
2017 and run something like: build —all —target=“winXP”.

Since I am unfamiliar with UNO, I can’t provide any points there, but I agree 
with that
separation of concerns, to keep only office functionality at the core of the 
project. Also
another future idea would be to split - I don’t know if it's possible - each 
application,
Writer, Calc, Impress etc. in its own separate module, so they can build 
independently
and, maybe?, debug easier, since someone can work on features on only the app 
he/she
wants.

As for the build system, after some research, I concluded on three modern build 
pipelines,
CMake, SCons and Meson. Personally, I am in favour of CMake, with the only 
argument
that it’s backed by many large companies and that provides a safety for the 
future. The two
systems are almost identical, SCons is more extensible due to Python, but all 
in all
it’s just a weight of each build system's pros and cons. Also, how KDE switched  
<https://lwn.net/Articles/188693/>
to CMake <https://lwn.net/Articles/188693/> was an interesting read. But, I 
think Damjan knows better about the project, so
we can have an open discussion about which build system is better for 
OpenOffice.

I think that for now we should focus on upgrading our tools, new compilers, 
SDKs, because
it's easier, it has been a week and I have done some progress already, and it 
will ease
development a little, but ultimately changing to a modern build system can have 
tremendous
potential for the project, modern build systems integrate perfect with Visual 
Studio,
Xcode, working on an IDE it’s always nice .

Kind regards,
George



On 5 Oct 2018, at 20:32, Damjan Jovanovic  wrote:

The split wouldn't help us with newer MSVC as such.

What would help us there a lot, is SCons, as SCons supports many MSVC
versions already, including MSVC 2017. It would be so wonderful if we were
on SCons already: not only would we build with a wider range of MSVC
versions, but we would need less work to keep up with future MSVC versions.
But unfortunately I think it's a lot easier to move to a new MSVC, than it
is to move to SCons. Especially given how heavy build development and
testing would be necessary on all platforms, and we don't have a Mac or
OS/2 or Solaris setup available...

On Fri, Oct 5, 2018 at 6:38 PM Peter Kovacs  wrote:


Hi Damjan,

I o not understand the MSVC part. If we separate UNO it's own world.
(Independent of the Idea to spin it of into its own project)

will the update of the MSVC be easier?


All the best

Peter


On 10/5/18 10:15 AM, Damjan Jovanovic wrote:

Hi

I now have a few other ideas regarding the building story.

The gbuild migration has been extraordinarily long and painful. Sadly

I've

had to learn so much about gbuild, and implement so many new features in

it

(symlinks, UNO IDL, Ant, bison, flex, now assembly...), that I am getting
good at it now :(. A lot of what I've done would have to be 

Re: Please, an improvment for Open Office : by default "print" should concern ONLY the CURRENT page

[Peter Kovacs]

Hi Agnes,


Thank you that you like our software. What is your work process. Are you 
using, Calc, draw or writer? Maybe all of them?


Can you elaborate? -It helps to understand what you face, in order to 
come up with an idea to enhance the Printing function. I believe that a 
lot of people want to print the hole document instead.


I would like to understand more where you are coming from and what your 
use case is.


I can not promise a quick fix, but maybe I can put your request on the 
list, for Stuff that we look into.



Thank you for your time

All the best

Peter

On 10/8/18 3:23 PM, agnes.troull...@free.fr wrote:

Please, an improvment for Open Office : by defautt "print" should concern ONLY 
the CURRENT page !

Otherwise, thanks for the software.



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

Re: svn commit: r1843108 - in /openoffice/branches/AOO416: ./ ext_libraries/serf/ main/ main/redland/ main/redland/prj/ main/redland/raptor/ main/redland/rasqal/ main/redland/redland/ main/scp2/source

[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 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: http://svn.apache.org/viewvc?rev=1843108=rev
Log:
merged in: Issue 127887 - update bundled redland/raptor/rasqal

Added:
 openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.dmake
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.dmake
 openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.os2
   - copied unchanged from r1818098, 
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.os2
 openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.win32
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.win32
 openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.dmake
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.dmake
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.ooo_build
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.ooo_build
 openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.win32
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.win32
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.autotools
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.autotools
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.dmake
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.dmake
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.ooo_build
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.ooo_build
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.os2
   - copied unchanged from r1818098, 
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.os2
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.win32
   - copied unchanged from r1757789, 
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.win32
Removed:
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.autotools
 openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.dmake
 openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.fixes
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.ooo_build
 openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.os2
 openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.win32
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.autotools
 openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.dmake
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.ooo_build
 openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.os2
 openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.win32
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.autotools
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.dmake
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.ooo_build
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.os2
 openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.win32
Modified:
 openoffice/branches/AOO416/   (props changed)
 openoffice/branches/AOO416/ext_libraries/serf/makefile.mk
 openoffice/branches/AOO416/main/   (props changed)
 openoffice/branches/AOO416/main/configure.in
 openoffice/branches/AOO416/main/external_deps.lst
 openoffice/branches/AOO416/main/redland/   (props changed)
 openoffice/branches/AOO416/main/redland/prj/d.lst
 openoffice/branches/AOO416/main/redland/raptor/makefile.mk
 openoffice/branches/AOO416/main/redland/rasqal/makefile.mk
 openoffice/branches/AOO416/main/redland/redland/makefile.mk
 openoffice/branches/AOO416/main/redland/redlandversion.mk
 openoffice/branches/AOO416/main/scp2/source/ooo/file_library_ooo.scp

Propchange: openoffice/branches/AOO416/
--
--- svn:mergeinfo (original)
+++ svn:mergeinfo Mon Oct  8 06:09:21 2018
@@ -2,5 +2,5 @@
  /openoffice/branches/ia2:1417739-1541842
  
/openoffice/branches/ooxml-osba:1546391,1546395,1546574,1546934,1547030,1547392,1551920,1551954,1551958,1552283
  

Re: current OpenOffice Flyers

[Peter Kovacs]

Hi Carl,

On the Link the text are now available in odt form. You can edit.

Please, answer when you are done so the correction can be integrated.

All the best

Peter

On 10/11/18 2:20 AM, Carl Marcum wrote:



On 10/09/2018 05:41 AM, Peter Kovacs wrote:

Hi all,

the german community has updated our flyers.

Current Version can be found at [1]

If you are french or english native speaker, please have a look.

And give some feedback, thanks.


All the best

Peter

[1] 
https://drive.google.com/drive/folders/1kpVknzJfZwuV5TOFvezg1V_TZLoSgYaY




Hi Peter,

I can help with the English version if I can get it in a format I can 
cut/paste paragraphs out of without going across the tri-folds.


A few quick ones...

change:
WasWhat is Apache OpenOffice?
to:
What is Apache OpenOffice?

change:
Apache OpenOffice is portabel :
to:
Apache OpenOffice is portable :

Thanks,
Carl

-
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: Help building AOO416 on Ubuntu 16.04

[Peter Kovacs]

I have been able to build OpenOffice with latest gcc . That has been a while go 
before my Laptop migration.
You have to set the fix to the right standard and you might have to set some 
behaviour flags.
I check for my config and post it. 

Am 14. Oktober 2018 14:49:26 MESZ schrieb Matthias Seidel 
:
>Hi Pedro,
>
>Am 14.10.2018 um 12:47 schrieb Pedro Lino:
>> Hi Matthias
>>
>>> On October 14, 2018 at 11:34 AM Matthias Seidel
>mailto:matthias.sei...@hamburg.de > wrote:
>>>
>>> I think I managed it with these instructions. But ignored most
>of the
>>> warnings, as they are fixed already (either in Ubuntu or in AOO
>branch).
>>>
>> Ok. So any instructions on how to solve the dependencies problems I
>run into?
>
>I still have a 16.04 VM, so I could try to set up an environment...
>But I *think* I just never downgraded g++/gcc but took the provided
>one.
>
>Regards,
>   Matthias
>
>>
>>
>>> > > Yes, I am aware of that. But it was suggested in this
>mailing list that since 14.04 is EOL and 16.04 will be supported until
>2021, this should be the next move.
 > 14.04 is still supported until 2019 (5 years for an LTS).
>>> But 16.04 would be the next step.
>>>
>> Thank you for the correction.
>>
>> I also manage a laptop running 18.04 so I can also try it at a later
>stage but I prefer to learn how to find/solve problems in my daily
>usage 16.04 machine.
>>
>>
>> Regards,
>>
>> Pedro
>>

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

Re: Chat Channel (was [Discussion] Program for Sandro)

[Peter kovacs]

I am online now too.  Thanks Gavin.

Am 14. Oktober 2018 13:21:04 MESZ schrieb Matthias Seidel 
:
>Hi Gavin,
>
>Am 14.10.2018 um 11:46 schrieb Gavin McDonald:
>> Install the Slack app, or via the web goto the-asf.slack.com you will
>find
>> an #openoffice slack channel ready and waiting, been there quite some
>time
>> unused.
>
>Thank you for the pointer, I didn't know of it.
>
>>
>> With HipChat going away, Slack is the option to use now.
>>
>> I am there, lets see you all there too!
>
>I'm in! ;-)
>
>Matthias
>
>>
>> HTH
>>
>> Gav...
>>
>>
>> On Sun, Oct 14, 2018 at 2:12 AM Howard Cary Morris <
>> howard_cary_mor...@hotmail.com> wrote:
>>
>>> I can create a chat room to share or you can use another service to
>do the
>>> same thing
>>> Howard
>>>
>>> From: sandro<mailto:sandro_suz...@hotmail.com>
>>> Sent: Friday, October 12, 2018 6:59 PM
>>> To: dev@openoffice.apache.org<mailto:dev@openoffice.apache.org>
>>> Subject: Re: Chat Channel (was [Discussion] Program for Sandro)
>>>
>>> Hi,
>>>
>>> I feel that the chat channel (real time chat) can really improve our
>>> experience to more creativity, we could be able to communicate and
>interact
>>> in real time, certainly our productivity would soar, it would lead
>us to
>>> greater satisfaction.
>>>
>>> Has anyone felt the same way about that idea? What is your opinion?
>>>
>>> When I first gave the idea I was thinking about a communication
>between me
>>> and Peter, but as other guys liked that idea then I feel it could be
>an
>>> amazing experience to all of us.
>>>
>>> Glad,
>>> Sandro Suzart
>>>
>>> 
>>> De: Peter Kovacs 
>>> Enviado: segunda-feira, 8 de outubro de 2018 04:11
>>> Para: dev@openoffice.apache.org
>>> Assunto: Chat Channel (was [Discussion] Program for Sandro)
>>>
>>> Hi all,
>>>
>>> I am traveling a lot. The classic irc channel never worked for me,
>>> because I get disconnects all the time.
>>>
>>> So currently from my perspective we could set something up in
>threema,
>>> slack or discord for real time chat.
>>>
>>> I am also open for other mobile capable options. Just keep in mind
>it
>>> has to work with a shitty german mobile connection.
>>>
>>> If anyone knows a solution for IRC I would gladly participate in a
>>> channel there.
>>>
>>>
>>> All the best
>>>
>>> Peter
>>>
>>> On 9/26/18 3:13 AM, sandro wrote:
>>>> Dear Peter
>>>>
>>>> It is an amazing idea, very nice. Maybe one of those kind services
>(
>>> Dropbox or Google) have a nice and amazing chat service so we could
>>> communicate in real time while working. It is nice to interact and
>it is
>>> glad, certainly it will drive us to joy.
>>>> I would like to try Dropbox and I would like to know if this
>service has
>>> means of communication in real time, like a chat?
>>>> Glad,
>>>> Sandro Suzart
>>>>
>>>>
>>>> 
>>>> De: Peter Kovacs 
>>>> Enviado: domingo, 23 de setembro de 2018 12:29
>>>> Para: dev@openoffice.apache.org
>>>> Assunto: Re: [Discussion] Program for Sandro
>>>>
>>>> Dear Sandro,
>>>>
>>>> Glad to read about your determination. :) Lets get you doing
>something.
>>>>
>>>> You can send it directly to my address if you like. I personally
>would
>>>> appreciate if we could store it somewhere more cloudy.
>>>>
>>>> How about google drive or Dropbox. They offer free cloud space. And
>you
>>>> can setup the space easy.
>>>>
>>>>
>>>> Yea it is really cool that we are a cloud Project. I think it is
>great
>>>> that you are with us. Maybe we can make OpenOffice a bit more
>Cloudy. ;)
>>>>
>>>> All the best
>>>>
>>>> Peter
>>>>
>>>> On 9/22/18 7:32 PM, sandro wrote:
>>>>> Dear Peter,
>>>>>
>>>>> It is always amazing to show my commitment and passion for this
>>> project, I feel that it is so good to build together that it
>certainly
>>> drives all of us to happiness.
>>&g

compile error

[Peter Kovacs]

I get the following error while trying to build on Linux:


/home/legine/workspace/ApacheOpenOffice/svn/main/codemaker/source/commonjava/commonjava.cxx:27:10: 
fatal error: sal/config.h: No such file or directory

 #include "sal/config.h"
  ^~

Is there some todo here? I do not understand why the compiler can not 
find sal/config.h


Thanks any pointers.


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

Re: compile error

[Peter Kovacs]

It is not there.

I did a build --from solenv --prepare in order to start over. Did not 
know how to reset the process.


There is no make clean. So I thought if I take the first module then I 
can go. seems that I did not take the first module.


On 10/15/18 11:49 PM, Damjan Jovanovic wrote:

Is there a main/solver/420//inc/sal/config.h?

If not, main/sal didn't deliver. Did you do a rebuild from scratch?

On Mon, Oct 15, 2018 at 10:57 PM Peter Kovacs  wrote:


I get the following error while trying to build on Linux:


/home/legine/workspace/ApacheOpenOffice/svn/main/codemaker/source/commonjava/commonjava.cxx:27:10:

fatal error: sal/config.h: No such file or directory
   #include "sal/config.h"
^~

Is there some todo here? I do not understand why the compiler can not
find sal/config.h

Thanks any pointers.


-
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: Update for Step by Step Build Guide for Ubuntu?

[Peter Kovacs]

Okay, I did a really poor and hasty migration when I switched machines. 
And the additional script I used to build OO went missing.


Basically you need to tweak the gcc compiler by changing the compiler 
flags. What you do is you extend/override the Variables CFLAG and CXXFLAG.


The best ressource is gentoo to understand the topic in general, since 
their users have to understand the topic to some degree.


https://wiki.gentoo.org/wiki/GCC_optimization


What you must set is the standard: -std=gnu99, maybe gnu++98 I do not 
remember exactly. Important is you use gnu++98 instead of c++98, because 
we use the gnu extensions.


So you run before you start export CFLAG="${CFGLAG} -std=gnu++98"


You have to set also some behavior flags. However I do not remember 
these. One was important to allow numbers to be interpret in logical 
operations and another error message I cant remember.


Maybe when you post, I will know.

I searched some documents on the net but I did not find the options I 
used on first glance. Also note that you should check the Options preset 
by Ubuntu.


I am sorry, i whish I had more pointers or the script available.


On 10/15/18 12:38 AM, Pedro Lino wrote:

Hi Keith



Thanks for taking on this experiment. I have created a 16.04 stub in the
 step by step building guide. I am more than willing to help with adding
 information to the guide.



Thanks!

I'm waiting on Peter Kovac's feedback to move forward.

If anyone else has some pointers on how to solve the dependencies problem, 
please let me know.


Regards,

Pedro



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

FOSDEM 2019 Booth Request for OpenOffice

[Peter Kovacs]

Hello all,

I do not find my last approach. So Lets start a new run.

I rewrote the argumentation to maybe now better Ideas. Please help to
finish this.

So the draft looks currently like this:


  Project Name

Apache OpenOffice


  Description of project(s) for publication:

Apache OpenOffice™ is the free and open productivity suite from the
Apache Software Foundation .

Apache OpenOffice  features six personal
productivity applications: a word processor (and its web-authoring
component), spreadsheet, presentation graphics, drawing, equation
editor, and database. OpenOffice is released on Windows, Linux and
macOS, with more communities joining, including ports for FreeBSD and
OS/2. OpenOffice is localized, supporting over 110 languages worldwide.

OpenOffice.org was donated

to the Apache Software Foundation (ASF) on June 1, 2011. As with any
code base brought to the ASF, OpenOffice.org underwent incubation before
graduating

to a top-level project on 2012-10-17.


  Why does it fit FOSDEM?

The Apache OpenOffice™ Project is one of view Projects that have fame
beyond the OpenSource movement. With an average download over 1.9
million copies per month and a peak download after release of
3.244.447.We are a popular project in user space.

We would like to show of the latest progress of our Software, by show
the latest stable and unstable versions. We would like to have some
Discussions with visitors about the Future of OpenOffice, how it could
evolve.

We were not as present on FOSDEM in the Last years, sharing our Booth
with the Apache Foundation. We would like to stand out this year again
in order to start some discussions.

We require one table for our representation of the Project.

Re: current OpenOffice Flyers

[Peter Kovacs]

Thanks Carl, Thanks Nancy,

I will pass that to the initiators of the fliers and pass their answer
back to this list.

On 10/16/18 3:28 AM, Nancy K wrote:
> What do you think about adding a QR code to some of the links in the 
> flyer?Free QR code generator: https://www.qr-code-generator.com/
> NancyK
>      Nancy       Web Design        
> Free 24 hour pass to lynda.com.
> Video courses on SEO, CMS,
> Design and Software Courses 
>
> On Monday, October 15, 2018, 5:20:20 PM PDT, Carl Marcum 
>  wrote:  
>  
>  I have an edited English version here:
>
> https://drive.google.com/open?id=1WtZVmknkM-hE5OwVdCgHSHJ3gnic9Piz
>
> Please review and update as needed.
>
> Thanks,
> Carl
>
>
> -
> 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

FOSDEM 2019: UNO Project as an Idea for Main track or fast talk? (was: FOSDEM 2019: no Open Document Editors devroom?)

[Peter Kovacs]

Hello all

How about the Idea we make a main track to introduce the Idea from
Damjan, to create an own UNO Project.

We would need to explain

# What it does

# Examples of how can it be used.

# what Features and benefits it has.

We could get a first feedback of interest from the audience.

I think this is a good talk for a main track in general.


All the best

Peter


On 10/13/18 7:22 PM, Matthias Seidel wrote:
> Hi Andrea,
>
> Am 13.10.2018 um 19:12 schrieb Andrea Pescetti:
>> On 11/10/2018 Andrea Pescetti wrote:
>>> While I haven't received any feedback from FOSDEM organizers yet (the
>>> two contact addresses I had given were mine and Peter's), I am not
>>> seeing the Open Document Editors devroom listed at
>>> https://fosdem.org/2019/schedule/
>> The organizers confirmed that the devroom won't run in 2019, so
>> neither OpenOffice nor similar programs will get a devroom (i.e., a
>> day-long conference track, for those unfamiliar with FOSDEM jargon).
>>
>> It is normal that FOSDEM rotates subjects of their devrooms and we
>> should be grateful to organizers for having given us a devroom in
>> several years so far, and possibly in future years beyond 2019.
> Thanks for the info!
> So we have more time to talk and (hopefully) for our booth. ;-)
>
>> There is still the opportunity to propose presentations for the
>> so-called "Main Track":
>> https://fosdem.org/2019/news/2018-08-10-call-for-participation/
> "Lightning talks" could also be interesting...
>
> Regards,
>    Matthias
>
>> 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: AOO 4.1.6-RC1 m1 r1844555

[Peter Kovacs]

I am a bit confused where we all are now. I think all Issues are
resolved and currently we are not aware on regressions right?

If r1844555 has not been build yet, then please start. :) I would like
to do some signing.

Thank you all for your efforts!

On 22.10.18 15:12, Jim Jagielski wrote:
> 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...@openoffice.apache.org
>

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

Re: Test builds of AOO 4.1.6 HEAD

[Peter Kovacs]

thanks Jim!

On 10/20/18 12:24 AM, Jim Jagielski wrote:
> 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 Linux 64bit (CentOS5) can be found at:
>>>
>>>http://home.apache.org/~jim/AOO-builds/
>>>
>>> 32bit CentOS will either be over the weekend or Monday. If I didn't upload 
>>> your lang of choice, let me know!
>>>
 On Oct 19, 2018, at 12:36 PM, Matthias Seidel  
 wrote:

 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 for Linux.

 I'd like to test it on a daily base...

 Matthias

> -
> 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
>>
>
> -
> 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: Test builds of AOO 4.1.6 HEAD

[Peter kovacs]

Hi all.

When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.

All the best
 Peter

Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 20:08 schrieb Marcus:
>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>> Am 21.10.18 um 19:59 schrieb Marcus:
 Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
> That's what it looks like, yeah.

 copyright years are always forgotten to update. Every year the
>same.
 ;-)
>>>
>>> In fact I *did* update it for trunk in January... ;-)
>>
>> hm, OK. Are you sure that you have updated it everywhere it is
>needed?
>> Even here the script could be helpful.
>
>I did update it where we always(TM) updated it:
>https://svn.apache.org/viewvc?view=revisionrevision=1780015
>
>But there are several parts (ODK, Linux packaging) which should get
>some
>attention.
>In 4.1.x they were not updated in all these years...
>
>So +1 for a script from me!
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> 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
>>>

 We now have a script to update version numbers; somewhere in the
 devtools I think.

 What about to create a new script to list all the code lines with a
 the year number. Then someone can have a look and compare it with
>the
 current calendar year and if needed create a patch to update all
 affected year numbers at ones.

 Maybe a good first step because no year number is forgotten. The
>next
 one would be to automate this update. But I've not yet an idea how
>to
 do this.

 What do you think?

 Marcus



>> 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 automatically,
>> otherwise not?
>>
>>>
 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 Community
 Build" \' for macOS and I am guessing the buildbots also use
>that
 configure option, so maybe that's a clue.

> 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 showing 2018:
>>
>> 
>>
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>>> pedro.l...@mailbox.org >
>wrote:
>>>
    But even if I wanted, I can not change the copyright
>year...
    That's what I am wondering about. ;-)

>>> Ok. I (wrongly) assumed it was all editable :)
>>>
>>>
    BTW: Can you confirm 2017 as copyright year in Jim's
>Linux
 builds?


>>> Yes, Jim's build is showing 2017.
>>>
>>>
>>> Regards,
>>>
>>> Pedro
>>
>>
>> -
>> 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: Test builds of AOO 4.1.6 HEAD

[Peter kovacs]

Stupid question where is the script?

Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 23:55 schrieb Marcus:
>> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>>> Am 21.10.18 um 22:43 schrieb Peter kovacs:
>>>>
>>>> When the year issue has been fixed, I think we can call it an RC1.
>I
>>>> check tomorrow evening. Sorry had no energy for stuff on the
>weekend.
>>>
>>> How do we want to sign the builds?
>>>
>>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>SHOULD
>>> NOT supply MD5 or SHA-1" [1]
>>>
>>> My suggestion would be to only supply SHA512.
>>
>> I don't see a problem to support also SHA256. And it's less work to
>> re-write the download scripting.
>
>OK, then someone has to work on the signing script... ;-)
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> 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-distribution#sigs-and-sums
>>>
>>>> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
>>>> :
>>>>> Am 21.10.18 um 20:08 schrieb Marcus:
>>>>>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>>>>>> Am 21.10.18 um 19:59 schrieb Marcus:
>>>>>>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>>>>>>>>> That's what it looks like, yeah.
>>>>>>>> copyright years are always forgotten to update. Every year the
>>>>> same.
>>>>>>>> ;-)
>>>>>>> In fact I *did* update it for trunk in January... ;-)
>>>>>> hm, OK. Are you sure that you have updated it everywhere it is
>>>>> needed?
>>>>>> Even here the script could be helpful.
>>>>> I did update it where we always(TM) updated it:
>>>>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>>>>>
>>>>> But there are several parts (ODK, Linux packaging) which should
>get
>>>>> some
>>>>> attention.
>>>>> In 4.1.x they were not updated in all these years...
>>>>>
>>>>> So +1 for a script from me!
>>>>>
>>>>> Matthias
>>>>>
>>>>>> Marcus
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>>> We now have a script to update version numbers; somewhere in
>the
>>>>>>>> devtools I think.
>>>>>>>>
>>>>>>>> What about to create a new script to list all the code lines
>with a
>>>>>>>> the year number. Then someone can have a look and compare it
>with
>>>>> the
>>>>>>>> current calendar year and if needed create a patch to update
>all
>>>>>>>> affected year numbers at ones.
>>>>>>>>
>>>>>>>> Maybe a good first step because no year number is forgotten.
>The
>>>>> next
>>>>>>>> one would be to automate this update. But I've not yet an idea
>how
>>>>> to
>>>>>>>> do this.
>>>>>>>>
>>>>>>>> What do you think?
>>>>>>>>
>>>>>>>> Marcus
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>> 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 automatically,
>>>>>>>>>> otherwise not?
>>>>>>>>>>
>>>>>>>>>>>> On Oct 20, 2018, at 10:54 AM, Jim Jagie

Re: AOO 4.1.6-RC1 m1 r1844555

[Peter kovacs]

Important is we build with the same revision. 
Are all builds now with r1844436?

Great if I do not have to sign anything. I gladly delegate that to the 
builders. ;-)


Am 23. Oktober 2018 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 RC should be build
>upon?
>
>>
>> FWIW, my macOS builds of RC1 are ready... CentOS5-64 are in progress.
>
>My build is also running (r1844436), just in case. ;-)
>
>Regards,
>
>Matthias
>
>>
>>> On Oct 23, 2018, at 6:03 AM, Matthias Seidel
> wrote:
>>>
>>> Hi Peter,
>>>
>>> Am 23.10.18 um 05:03 schrieb Peter Kovacs:
>>>> I am a bit confused where we all are now. I think all Issues are
>>>> resolved and currently we are not aware on regressions right?
>>>>
>>>> If r1844555 has not been build yet, then please start. :) I would
>like
>>>> to do some signing.
>>> Now I am a bit confused. The last commit in 4.1.6 was r1844436:
>>> https://svn.apache.org/viewvc?view=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!
>>>>
>>>> On 22.10.18 15:12, Jim Jagielski wrote:
>>>>> 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...@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
>>

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

[help] Booth for FOSDEM 2019 additional Info.

[Peter Kovacs]

Hello all,


I need some help. could someone collect these?

Additional links (e.g. IRC, Google+, RSS, Twitter, Facebook, YouTube,
mailing list etc.):


And our public email contact is dev or private or press address? I am
not sure.

Thanks!

All the best

Peter


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

Re: Blocker issue 127789: Server error when looking for updates

[Peter Kovacs]

Hi Pedro,

just to be clear. We should solve this issue with or before 4.1.6. Thats
why I have linked it to the release.

There is no other reason for the link. We just need some pressure (which
is not bad) it seems in order to get this done.

All the best

Peter

On 29.10.18 00:15, Pedro Lino wrote:
> Hi Andrea, all
>
> This is clearly a server side error (and an intermitent one)
> I rolled back to 4.1.4 (which was correctly reporting an update available 
> last week) but today all versions I tested (4.1.6, 4.1.5 and 4.1.4) all 
> report "Checking for an update failed."
>
> This is not a 4.1.6 problem.
>
> Regards,
> Pedro
>
>
>> On October 28, 2018 at 9:53 PM Andrea Pescetti  wrote:
>>
>>
>> I've taken a look at the few 4.1.6 accepted blockers that are still 
>> open. Don already discussed the ones affecting libraries.
>>
>> I'm especially interested in this one (server error when looking for 
>> updates)
>> https://bz.apache.org/ooo/show_bug.cgi?id=127789
>> that should be investigated properly unless someone is already doing it 
>> and can report here.
>>
>> As I wrote in the issue, this could be an issue just with the ASF 
>> network configuration and it may not require a fix at all.
>>
>> Usually, as part of my release voting, I simulate the updates server on 
>> my local machine, create a feed and check that OpenOffice displays the 
>> right message. So 4.1.5 was not broken, and actually error reports 
>> started to come only when 4.1.5 had already been available for months.
>>
>> Did anyone else make enough progress on this to rule out (at least) that 
>> we need code changes, so that this can be addressed by gathering data 
>> and talking to Infra?
>>
>> 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

[vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

Hello all,


This is about a small maintenance Release. We fix various Issues.

Please take your vote.

The Release Candidate is good for production:

[ ] yes / +1

[ ] no / -1

My vote is based on

[ ] binding (member of PMC)

[ ] I have build and tested the RC from source

[ ] I have tested the binary RC


Thanks for your patience and participation!

All the Best

Peter Kovacs

Release Manager of 4.1.6



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

Re: AOO 4.1.6 and MacOS Mojave

[Peter Kovacs]

Which Problems? I am not sure what they refer to.

On 30.10.18 15:56, FR web forum wrote:
> Hello,
>
> We have some questions about compatibility with MacOS 10.14
> https://roaringapps.com/apps displays "some problems" 
> This next build will be OK?
>
> -
> 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: AOO 4.1.6-RC1 vote

[Peter Kovacs]

The release Manager has to much load at the moment. I have initiated the
vote just now.

I am sorry. For the slow speed.

On 31.10.18 20:48, Keith N. McKenna wrote:
> On 10/31/2018 2:46 PM, Jim Jagielski wrote:
>> Did I miss it?
>>
> As far as I know the Release Manager has not yet issued the call for a vote.
>
> Regards
> Keith
>
>

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

Re: AOO 4.1.6-RC1 vote

[Peter Kovacs]

aye!

On 31.10.18 23:10, Pedro Lino wrote:
> Hi Peter, all
>
>> The release Manager has to much load at the moment. I have initiated the
>> vote just now.
> Just to make sure we are all on the same page: 4.1.6-RC1 refers to Rev. 
> 1844227 available from
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/
> right?
>
>
> Regards,
> Pedro
>
> -
> 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

[vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

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:
https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/

We follow the policy for the Apache policy on Release Approval at
http://www.apache.org/legal/release-policy.html#release-approval

In order to create a binding vote individuals are REQUIRED to

* download all signed _source code_ packages onto their own hardware,

* verify that they meet all requirements of ASF policy on releases
as described below,

* validate all cryptographic signatures,

* compile as provided, and test the result on their own platform.

In order to create a normal vote individuals are REQUIRED to

* download all signed _binary_ packages onto their own hardware,

* verify that they meet all requirements of ASF policy on releases
as described below,

* validate all cryptographic signatures,

* compile as provided, and test the result on their own platform.



The Release Candidate 1 for 4.1.6 has passed my tests.

[ ] yes / +1

[ ] no / -1

I have tested

Windows Release

[ ] source / binding

[ ] binary

Linux Release 32 bit

[ ] source / binding

[ ] binary

Linux Release 64 bit

[ ] source / binding

[ ] binary

MacOSX Release

[ ] source / binding

[ ] binary

Re: OO & Mojave issue?

[Peter Kovacs]

Looping in Users.

OpenOffice on Mac can react wired when the scrolling is setup do not
match. I returned to Linux so I forgot where the settings has to be set
and how.Maybe someone on users can help?

I think it was not scrolling line by line, or something similar.


All the Best

Peter


On 01.11.18 11:20, Michael Turner wrote:
> Hi, can you assist,  I note on my 2018 iMac, with Mojave Ver 1014 running 
> that O O's Ver 4.1.5 video frames, or if scrolling through a project that 
> movement has become very jerky.   There seems to be a slight time lag between 
> mouse input and screen activity.  
>
> I wondered if Apache is aware and is working on or updating OO to run 
> smoothly on Mojave, or do I have a problem?
>
> My regards
>
> Michael Turner
> Cambridge
> UK
>
>
> -
> 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: OO & Mojave issue?

[Peter Kovacs]

FYI: my mailing service refuses to sent to Michael turner, because his
mailing service does not support TLS.


On 01.11.18 12:38, Peter Kovacs wrote:
> Looping in Users.
>
> OpenOffice on Mac can react wired when the scrolling is setup do not
> match. I returned to Linux so I forgot where the settings has to be set
> and how.Maybe someone on users can help?
>
> I think it was not scrolling line by line, or something similar.
>
>
> All the Best
>
> Peter
>
>
> On 01.11.18 11:20, Michael Turner wrote:
>> Hi, can you assist,  I note on my 2018 iMac, with Mojave Ver 1014 running 
>> that O O's Ver 4.1.5 video frames, or if scrolling through a project that 
>> movement has become very jerky.   There seems to be a slight time lag 
>> between mouse input and screen activity.  
>>
>> I wondered if Apache is aware and is working on or updating OO to run 
>> smoothly on Mojave, or do I have a problem?
>>
>> My regards
>>
>> Michael Turner
>> Cambridge
>> UK
>>
>>
>> -
>> 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: [vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

I did not see this post from you.

Which Distro do you use?

You need Gstreamer 0.1.0 for OpenOffice 4.1.x series, if you want
Multimedia.

Support for Gstreamer 1.0.0 is included in 4.2.0.


All the best

Peter

On 01.11.18 12:49, 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?
>
> I have found this obstacle but no one on the dev mailing list answered (which 
> worries me since I have been trying to contribute to this project...)
>
> Any idea how to solve these dependencies problem?
>
> Thank you in advance!
>
> Best,
> Pedro
>
> plino@Latitude-E6520:/$ sudo apt-get install bison flex libarchive-zip-perl 
> libcups2-devlibpam0g-dev gperf libfreetype6-dev libxaw7-dev 
> libfontconfig1-devlibxrandr-dev patch libgconf2-dev libgnomevfs2-dev 
> ant libgtk2.0-devjunit junit4 libidl-dev liborbit2-dev libwww-perl
> libxml-parser-perl autoconf libssl-dev libpam-dev libgstreamer\*
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Note, selecting 'libpam0g-dev' instead of 'libpam-dev'
> Note, selecting 'libgstreamer-plugins-base1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer0.10-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-vaapi1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamermm-1.0-0v5' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-base0.10-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer1.0-0-dbg' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-base0.10-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamermm-1.0-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamermm-1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamermm-1.0-doc' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml-dev-5f1y4:i386' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-good1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-good1.0-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer0.10-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-bad0.10-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml-dev-dh5s9' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-base1.0-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml-5f1y4:i386' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer0.10-0-dbg' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-java' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-bad1.0-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml-dev' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-plugins-bad1.0-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer1.0-0' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml-dh5s9' for glob 'libgstreamer*'
> Note, selecting 'libgstreamer-ocaml' instead of 'libgstreamer-ocaml-dh5s9'
> Note, selecting 'libgstreamer-ocaml-dev' instead of 
> 'libgstreamer-ocaml-dev-dh5s9'
> Note, selecting 'libgstreamer-ocaml:i386' instead of 
> 'libgstreamer-ocaml-5f1y4:i386'
> Note, selecting 'libgstreamer-ocaml-dev:i386' instead of 
> 'libgstreamer-ocaml-dev-5f1y4:i386'
> autoconf is already the newest version (2.69-9).
> autoconf set to manually installed.
> libwww-perl is already the newest version (6.15-1).
> libwww-perl set to manually installed.
> libxml-parser-perl is already the newest version (2.44-1build1).
> libxml-parser-perl set to manually installed.
> libgstreamer-ocaml is already the newest version (0.2.0-2build2).
> libgstreamer0.10-0 is already the newest version (0.10.36-1.5ubuntu1).
> libgstreamer0.10-0 set to manually installed.
> libarchive-zip-perl is already the newest version (1.56-2ubuntu0.1).
> libarchive-zip-perl set to manually installed.
> libfontconfig1-dev is already the newest version (2.11.94-0ubuntu1.1).
> libfontconfig1-dev set to manually installed.
> libfreetype6-dev is already the newest version (2.6.1-0.1ubuntu2.3).
> libfreetype6-dev set to manually installed.
> libgstreamer-plugins-base1.0-0 is already the newest version 
> (1.8.3-1ubuntu0.2).
> libgstreamer-plugins-base1.0-0 set to manually installed.
> libgstreamer-plugins-base1.0-dev is already the newest version 
> (1.8.3-1ubuntu0.2).
> libgstreamer-plugins-good1.0-0 is already the newest version 
> (1.8.3-1ubuntu0.4).
> libgstreamer-plugins-good1.0-0 set to manually installed.
> libgstreamer1.0-0 is already the newest version (1.8.3-1~ubuntu0.1).
> libgstreamer1.0-0 set to manually installed.
> libgstreamer1.0-dev is already the newest version (1.8.3-1~ubuntu0.1).
> libssl-dev is already the newest version (1.0.2g-1ubuntu4.13).
> libssl-dev set to manually installed.
> patch 

Re: [help] Booth for FOSDEM 2019 additional Info.

[Peter kovacs]

I think so am fine now. There is the link and I think press is best suited.
Yesterday I got distracted. I want to finish this point tomorrow.

Am 30. Oktober 2018 12:03:40 MEZ schrieb Matthias Seidel 
:
>Am 26.10.18 um 00:21 schrieb Andrea Pescetti:
>> Marcus wrote:
>>> Am 25.10.2018 um 12:48 schrieb Peter kovacs:
>>>> All I can add it is fields to enter on the booth registration.
>>> hm, OK.
>>> For the social media link, our project page could be helpful - as
>>> Matthias stated:
>>> https://openoffice.apache.org/social.html
>>
>> I assume the form we are talking about is this one:
>> https://submission.fosdem.org/stands.php
>
>Deadline is 2 November...
>
>@Peter: Do you still need more info?
>
>Regards,
>
>   Matthias
>
>>
>>> As I cannot imagine what mails could be sent to the "public email
>>> contact" (e.g., password, confirmation code) I would prefer privat@
>-
>>> just to be sure.
>>
>> I believe pr...@openoffice.org will do. In the context, I assume this
>> would be used in a listing page such as (previous edition)
>> https://archive.fosdem.org/2018/stands/ in the, very rare,
>> circumstances when a project does not have a web site.
>>
>> 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: AOO 4.1.6-RC1 m1 r1844555

[Peter kovacs]

Yes I applied them manually. And I took only changes from the version that I 
thought the change is about.

Am 27. Oktober 2018 00:22:55 MESZ schrieb Don Lewis :
>On 27 Oct, Matthias Seidel wrote:
>> Am 27.10.18 um 00:10 schrieb Don Lewis:
>>> On 27 Oct, Matthias Seidel wrote:
 Am 26.10.18 um 21:39 schrieb Don Lewis:
> On 26 Oct, Jim Jagielski wrote:
>>> 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.
> When we upgraded those in trunk, it broke the Mac build.  You
>committed
> this change
>https://svn.apache.org/viewvc?view=revision=1805089
> to unbreak things on the Mac, which include some changes to
> configure.ac.  AOO416 has configure.in instead of configure.ac, so
>in my
> instructions for merging this upgrade back to AOO416 here:
> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand
>apply
> the configure.ac changes to configure.in.  That broke the buildbot
> builds at the configure stage due to shell syntax errors:
>
>https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
> so the entire upgrade was backed out of AOO416 with r1843571.
>
> The question is whether we can merge the four commits from trunk
>to
> AOO416 and skip the configure changes and get a successful build
>on the
> Mac, or do we need to do some other change to configure.in to get
>a
> successful build.  My testing without any configure.in changes
>worked on
> Linux and Windows.
 I am building for Windows at the moment (omitting the changes in
 configure.in).

 No problems so far...
>>> As I previously mentioned, I built and tested that on both Windows
>and
>>> Linux, specifically CentOS 6.  I didn't test CentOS 5 since my VM
>broke
>>> and it's difficult to set up a new CentOS 5 VM since that release
>has
>>> been archived.
>> 
>> So macOS remains to be tested...
>> 
>> I am not sure now what caused the buildbots to break, but they all
>> stopped early in configure.
>
>I think it was the step where the configure.ac changes for the Mac were
>manually applied to configure.in.  It is unclear whether they are
>actually required for the Mac or if they need to be reworked for
>configure.in.
>
>
>-
>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: AOO 4.1.6-RC1 m1 r1844555

[Peter kovacs]

Well it is a bummer we can not fix it with 4.1.6. However this one is 6 year 
old. It can wait a view month. It is not worth to backport if the same effort 
can bring 4.2.0 to live.

Am 26. Oktober 2018 22:04:54 MESZ schrieb Don Lewis :
>raptor 1.4.18 has CVE-2012-0037, otherwise I would not have bothered
>with the upgrade.
>
>On 26 Oct, Jim Jagielski wrote:
>> 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
> 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.
>>> 
>>> When we upgraded those in trunk, it broke the Mac build.  You
>committed
>>> this change
>https://svn.apache.org/viewvc?view=revision=1805089
>>> to unbreak things on the Mac, which include some changes to
>>> configure.ac.  AOO416 has configure.in instead of configure.ac, so
>in my
>>> instructions for merging this upgrade back to AOO416 here:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand
>apply
>>> the configure.ac changes to configure.in.  That broke the buildbot
>>> builds at the configure stage due to shell syntax errors:
>>>
>https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>>> so the entire upgrade was backed out of AOO416 with r1843571.
>>> 
>>> The question is whether we can merge the four commits from trunk to
>>> AOO416 and skip the configure changes and get a successful build on
>the
>>> Mac, or do we need to do some other change to configure.in to get a
>>> successful build.  My testing without any configure.in changes
>worked on
>>> Linux and Windows.
>>> 
>>> 
>>>
>-
>>> 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

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

Re: [help] Booth for FOSDEM 2019 additional Info.

[Peter kovacs]

All I can add it is fields to enter on the booth registration.

Am 24. Oktober 2018 23:56:54 MESZ schrieb Marcus :
>Am 24.10.2018 um 23:36 schrieb Peter Kovacs:
>> I need some help. could someone collect these?
>> 
>> Additional links (e.g. IRC, Google+, RSS, Twitter, Facebook, YouTube,
>> mailing list etc.):
>
>IMHO it would be easier when we have some more context why/where these 
>information is needed.
>
>> And our public email contact is dev or private or press address? I am
>> not sure.
>
>Also here: What is meant with "public"? Also here some more context is 
>helpful.
>
>Thanks
>
>Marcus
>
>
>-
>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: [vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter kovacs]

Source signing will be done tonight.
Thanks Andrea for the detailed line-up.
Also I hope all requirements are met in the second mail.
However there seems a misunderstanding on Keith side. It is not required to 
vote all test marks.
It is required to fill in general and then what OS  Version you have tested and 
if you have tested from source or not.
Simone state in order to create a binding vote it has to be tested from source.
We need 3 of those.
Also we should have an overview which Binaries has been reviewed.

That is all.
All the best
Peter

Am 5. November 2018 00:22:33 MEZ schrieb Matthias Seidel 
:
>Hi Andrea,
>
>Am 05.11.18 um 00:07 schrieb Andrea Pescetti:
>> On 31/10/2018 Marcus wrote:
>>> To make it an official vote I miss the following information:
>>> - What exactly do we vote for (link to the source and binaries)?
>>
>> Yes please, let's try to be reasonably serious about releases: due to
>> legal implications (among other things), there are some formalities
>> that are required; nothing more than what we did for any other
>Release
>> Candidate in history.
>>
>> I assume we are voting on (this is the only 4.1.6-RC1 available, but
>> it needs to be recorded in the vote discussion!)
>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/
>>
>>> - What is the time for the vote? Please more than just the normal 72
>>> hours so that we all can use a weekend for more testing.
>>
>> Elsewhere Peter mentioned until Wednesday 7 November but again this
>> should be in the vote thread (so, here).
>>
>> And most important: the Release Manager (Peter) must sign the source
>> files. I've just spent a lot of time trying to make sense of various
>> ways to have multiple signature in one file, concluding that it is
>> easy to do that for a binary signature, but it is a hack to do so for
>> the ASCII-armored signatures we use.
>>
>> So, in short, Peter as the Release Manager should rectify things by:
>>
>> 1) Confirming that the URL and deadline above are correct
>>
>> 2) Replace, before the vote ends, current signatures with only his
>> signature as follows:
>>
>> $ svn checkout
>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/source
>> $ rm *.asc
>> $ gpg -a -b --digest-algo=SHA512 *.bz2
>> $ gpg -a -b --digest-algo=SHA512 *.gz
>> $ gpg -a -b --digest-algo=SHA512 *.zip
>> $ svn commit
>>
>> About this second item, I see that Matthias concatenated his
>signature
>> to Jim's one: this is possible for the binary format but GPG will
>> complain if this is done for the ASCII format, and as you can see by
>> searching the net there is no clean way to do it. I checked back in
>> version 4.1.2 (that was signed by Juergen and me) and I found out
>that
>> I had simply replaced Juergen's signature with mine in that case (I
>> was the Release Manager for 4.1.2). We can do the same this time.
>
>I found double signatures in 4.1.3:
>https://archive.apache.org/dist/openoffice/4.1.3/source/apache-openoffice-4.1.3-r1761381-src.zip.asc
>
>But yes, GPG complains about it and will only verify the first. So
>Peter's signature should be the only one...
>
>(Of course he could also use our hash-sign.sh, which is fixed now for
>SHA512).
>
>Regards,
>
>   Matthias
>
>>
>> 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: [vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

actually I tried to make a clear form and got confused all the way.

Since there is no change in process, please follow the instructions below.

We should have a fixed email for this, maybe we have and I just lacked
the memory to remeber.


So now the rules state I should sign all artifacts. Others may
concatenate their signature if they want. Do we follow this?

On 05.11.18 17:54, Andrea Pescetti wrote:
> Keith N. McKenna wrote:
>> In his second vote announcement Peter also specified that to cast a
>> non-binding vote one still had to download and compile the source on
>> ones own machine and then test that binary. This is far over and above
>> anything that has ever been required for a non-binding vote.
>
> Whether a vote is binding or not depends entirely on the role: due to
> legal issues, votes from PMC members are (always) "binding", meaning
> that they are counted separately, even though everyone is welcome to
> vote.
>
> We need to have on record at least three PMC members who built from
> source and tested for the vote to be considered valid. The threshold
> of three is a hard requirement.
>
> While building would be required of other people too, we've
> historically not been very rigid on this, provided that voters in
> general, so both PMC members and people from the community at large,
> simply write (a subset of) what they did.
>
> Summarizing:
>
> - If you, PMC member or not, feel that the release is good enough,
> please do vote and say something "+1; I tested the Italian version on
> MacOS, opened ODF and .docx files, everything was OK" and nobody will
> ask you whether you built from source or not; this is very valuable
> feedback as we would have very limited platform/language coverage
> otherwise.
>
> - In order to close the vote successfully, at least 3 PMC members must
> explicitly write in their statement that they built from source and
> tested their own builds. This ensures we meet the minimum requirements.
>
> 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

moving to git !?

[Peter Kovacs]

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.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E


It was somewhat unlucky. We should start to prepare the move. I think it
is okay to do this now. After that we should start with 4.1.7 release
and 4.2.0 release preparations.

We can also start the uno split if Damjan is still in this idea.


Also we need to check on the pull workflow with infra. Any volunteers to
do this?

Any Concerns with this initiative?



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

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

Hi Andrea,

I extend the deadline until Saturday Morning CET. I hope this gives
everybody who wants to check another view days.


All the best

Peter

On 08.11.18 00:28, 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 job and just recently I got
>>> back a repaired laptop. So, had not yet the time to update my build
>>> system
>>
>> Since I see that we don't have many people who built from source yet
>> and the vote deadline is approaching: I've also setup a new build
>> system from scratch (CentOS 7, so that I could fix and update the
>> wiki instructions since that will be our baseline for 4.2.0). But
>> I'll need about 24 hours more to complete my tests.
>
> it's up to Peter as release manager if he will wait a few hours more. ;-)
>
>> On the other hand (binaries), I'm not tracking feedback, but have we
>> received any feedback from people who installed the binaries on
>> MacOS? My tests will be on Linux64 so I won't contribute anything new
>> in terms of platforms.
>
> From the vote replies I see that at least Jim and Roberto have tested
> binaries and source for MacOS. And also Linux 32-bit which is also
> underrepresented.
>
> Marcus
>
>
> -
> 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

Impress masterpage issue, has someone time to test?

[Peter Kovacs]

There is a patch for this issue. Can someone check it out?

https://bz.apache.org/ooo/show_bug.cgi?id=127929

Thanks!


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

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1 - Vote resolution

[Peter Kovacs]

Thanks for your efforts and participation. It is no issue if you are
early or late. Important is that you believe in the release.

We have following test results:

*Who*   *Passed**Binding*   *Windows*   *
*   *Linunx**
*   *MacOs* *
*   *Language Attention**Specials*



*Binary**Source**Binary**Source*
*Binary**Source*

khirano 1   
1   




Japanese
Andrea  1   1   

1   1   

Italian 
Marcus  1   1   1   
1   


US / German 
Matthias1   1   1   1   1   



Included 32 bit Linux
Josef   1   


1   




Pedro   1   
1   
1   1   

US / Portugese  
Jim 1   1   

1   1   1   1   
Included 32 bit Linux
*summary*   *7* *4* *4* *1* *6* *3* *1* *1* 



We have the necessary Binding votes. All Target systems have been tested
from source and binary. We have a test coverage on diverse Languages.

The Vote has been made in favor for Release.


All the Best

Peter

On 09.11.18 01:25, Kazunari Hirano wrote:
> Hi Peter and all,
>
> +1
> The Release Candidate 1 for 4.1.6 has passed my tests.
>
> I am sorry but I am late.
>
> I installed japanese version and en-GB langpack on my Windows 10 machine.
>
> They looks good.
>
> Thanks.
>
> khirano
>
>
> On Thu, Nov 1, 2018 at 3:52 PM 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:
>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/
>>
>> We follow the policy for the Apache policy on Release Approval at
>> http://www.apache.org/legal/release-policy.html#release-approval
>>
>> In order to create a binding vote individuals are REQUIRED to
>>
>> * download all signed _source code_ packages onto their own hardware,
>>
>> * verify that they meet all requirements of ASF policy on releases
>> as described below,
>>
>> * validate all cryptographic signatures,
>>
>> * compile as provided, and test the result on their own platform.
>>
>> In order to create a normal vote individuals are REQUIRED to
>>
>> * download all signed _binary_ packages onto their own hardware,
>>
>> * verify that they meet all requirements of ASF policy on releases
>> as described below,
>>
>> * validate all cryptographic signatures,
>>
>> * compile as provided, and test the result on their own platform.
>>
>>
>> 
>>
>> The Release Candidate 1 for 4.1.6 has passed my tests.
>>
>> [ ] yes / +1
>>
>> [ ] no / -1
>>
>> I have tested
>>
>> Windows Release
>>
>> [ ] source / binding
>>
>> [ ] binary
>>
>> Linux Release 32 bit
>>
>> [ ] source / binding
>>
>> [ ] binary
>>
>> Linux Release 64 bit
>>
>> [ ] source / binding
>>
>> [ ] binary
>>
>> MacOSX Release
>>
>> [ ] source / binding
>>
>> [ ] binary
>>
>>

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1 - Vote resolution

[Peter Kovacs]

Formating was fine in my Email client...

Wired. I just copied it quickly from a calc sheet. I upload it on the
release page.

All the best

Peter

On 11.11.18 11:56, Matthias Seidel wrote:
> Hi Peter,
>
> Am 10.11.18 um 14:06 schrieb Peter Kovacs:
>> Thanks for your efforts and participation. It is no issue if you are
>> early or late. Important is that you believe in the release.
>>
>> We have following test results:
>>
>> *Who**Passed**Binding*   *Windows*   *
>> **Linunx**
>> **MacOs* *
>> **Language Attention**Specials*
>>
>>  
>>  
>>  *Binary**Source**Binary**Source*
>> *Binary**Source*
>>  
>> khirano  1   
>>  1   
>>  
>>  
>>  
>>  
>>  Japanese
>> Andrea   1   1   
>>  
>>  1   1   
>>  
>>  Italian 
>> Marcus   1   1   1   
>>  1   
>>  
>>  
>>  US / German 
>> Matthias 1   1   1   1   1   
>>  
>>  
>>  
>>  Included 32 bit Linux
>> Josef1   
>>  
>>  
>>  1   
>>  
>>  
>>  
>>  
>> Pedro1   
>>  1   
>>  1   1   
>>  
>>  US / Portugese  
>> Jim  1   1   
>>  
>>  1   1   1   1   
>>  Included 32 bit Linux
>> *summary**7* *4* *4* *1* *6* *3* *1* *1* 
> Formatting is a bit weird...
>>  
>>
>>
>> We have the necessary Binding votes. All Target systems have been tested
>> from source and binary. We have a test coverage on diverse Languages.
>>
>> The Vote has been made in favor for Release.
> Great, then let us get this thing out! ;-)
>
> Follow the steps described here:
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6
>
> Regards,
>
>    Matthias
>
>>
>> All the Best
>>
>> Peter
>>
>> On 09.11.18 01:25, Kazunari Hirano wrote:
>>> Hi Peter and all,
>>>
>>> +1
>>> The Release Candidate 1 for 4.1.6 has passed my tests.
>>>
>>> I am sorry but I am late.
>>>
>>> I installed japanese version and en-GB langpack on my Windows 10 machine.
>>>
>>> They looks good.
>>>
>>> Thanks.
>>>
>>> khirano
>>>
>>>
>>> On Thu, Nov 1, 2018 at 3:52 PM 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:
>>>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/
>>>>
>>>> We follow the policy for the Apache policy on Release Approval at
>>>> http://www.apache.org/legal/release-policy.html#release-approval
>>>>
>>>> In order to create a binding vote individuals are REQUIRED to
>>>>
>>>> * download all signed _source code_ packages onto their own hardware,
>>>>
>>>> * verify that they meet all requirements of ASF policy on releases
>>>> as described below,
>>>>
>>>> * validate all cryptographic signatures,
>>>>
>>>> * compile as provided, and test the result on their own platform.
>>>>
>>>> In order to create a normal vote individuals are REQUIRED to
>>>>
>>>> * download all signed _binary_ packages onto their own hardware,
>>>>
>>>> * verify that they meet all requirements of ASF policy on releases
>>>> as described below,
>>>>
>>>> * validate all cryptographic signatures,
>>>>
>>>> * compile as provided, and test the result on their own platform.
>>>>
>>>>
>>>> 
>>>>
>>>> The Release Candidate 1 for 4.1.6 has passed my tests.
>>>>
>>>> [ ] yes / +1
>>>>
>>>> [ ] no / -1
>>>>
>>>> I have tested
>>>>
>>>> Windows Release
>>>>
>>>> [ ] source / binding
>>>>
>>>> [ ] binary
>>>>
>>>> Linux Release 32 bit
>>>>
>>>> [ ] source / binding
>>>>
>>>> [ ] binary
>>>>
>>>> Linux Release 64 bit
>>>>
>>>> [ ] source / binding
>>>>
>>>> [ ] binary
>>>>
>>>> MacOSX Release
>>>>
>>>> [ ] source / binding
>>>>
>>>> [ ] binary
>>>>
>>>>

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

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1 - Vote resolution

[Peter Kovacs]

I think the next topic is writing release notes.

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6+Release+Notes


Who is available for this? The release blocker 4.1.6 "+" is telling you
what is in the release.

There is one exception. One Bug about updates is about our update
facility, and has no relevance to the Code.


All the Best

Peter

On 11.11.18 15:58, Peter Kovacs wrote:
> Formating was fine in my Email client...
>
> Wired. I just copied it quickly from a calc sheet. I upload it on the
> release page.
>
> All the best
>
> Peter
>
> On 11.11.18 11:56, Matthias Seidel wrote:
>> Hi Peter,
>>
>> Am 10.11.18 um 14:06 schrieb Peter Kovacs:
>>> Thanks for your efforts and participation. It is no issue if you are
>>> early or late. Important is that you believe in the release.
>>>
>>> We have following test results:
>>>
>>> *Who*   *Passed**Binding*   *Windows*   *
>>> *   *Linunx**
>>> *   *MacOs* *
>>> *   *Language Attention**Specials*
>>>
>>> 
>>> 
>>> *Binary**Source**Binary**Source*
>>> *Binary**Source*
>>> 
>>> khirano 1   
>>> 1   
>>> 
>>> 
>>> 
>>> 
>>> Japanese
>>> Andrea  1   1   
>>> 
>>> 1   1   
>>> 
>>> Italian 
>>> Marcus  1   1   1   
>>> 1   
>>> 
>>> 
>>> US / German 
>>> Matthias1   1   1   1   1   
>>> 
>>> 
>>> 
>>> Included 32 bit Linux
>>> Josef   1   
>>> 
>>> 
>>> 1   
>>> 
>>> 
>>> 
>>> 
>>> Pedro   1   
>>> 1   
>>> 1   1   
>>> 
>>> US / Portugese  
>>> Jim 1   1   
>>> 
>>> 1   1   1   1   
>>> Included 32 bit Linux
>>> *summary*   *7* *4* *4* *1* *6* *3* *1* *1* 
>> Formatting is a bit weird...
>>> 
>>>
>>>
>>> We have the necessary Binding votes. All Target systems have been tested
>>> from source and binary. We have a test coverage on diverse Languages.
>>>
>>> The Vote has been made in favor for Release.
>> Great, then let us get this thing out! ;-)
>>
>> Follow the steps described here:
>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6
>>
>> Regards,
>>
>>    Matthias
>>
>>> All the Best
>>>
>>> Peter
>>>
>>> On 09.11.18 01:25, Kazunari Hirano wrote:
>>>> Hi Peter and all,
>>>>
>>>> +1
>>>> The Release Candidate 1 for 4.1.6 has passed my tests.
>>>>
>>>> I am sorry but I am late.
>>>>
>>>> I installed japanese version and en-GB langpack on my Windows 10 machine.
>>>>
>>>> They looks good.
>>>>
>>>> Thanks.
>>>>
>>>> khirano
>>>>
>>>>
>>>> On Thu, Nov 1, 2018 at 3:52 PM 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:
>>>>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/
>>>>>
>>>>> We follow the policy for the Apache policy on Release Approval at
>>>>> http://www.apache.org/legal/release-policy.html#release-approval
>>>>>
>>>>> In order to create a binding vote individuals are REQUIRED to
>>>>>
>>>>> * download all signed _source code_ packages onto their own hardware,
>>>>>
>>>>> * verify that they meet all requirements of ASF policy on releases
>>>>> as described below,
>>>>>
>>>>> * validate all cryptographic signatures,
>>>>>
>>>>> * compile as provided, and test the result on their own platform.
>>

New OpenOffice Release 4.1.6 Release Preperations

[Peter Kovacs]

Hello Infra,

we have a new Release ready. Can you prepare the Servers for the new
Update? (On our Release Sheet it mentions you have to do something.)

Please inform us on the time needed, and when ready.


Thank you.


All the best

Peter


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

Re: New OpenOffice Release 4.1.6 Release Preperations

[Peter Kovacs]

Normally the package manager knows the right order. That why you have it.

you load everything you want to update in one folder and then say *rpm
-Uvih *rpm*.

As it is mentioned in our Howto [1], btw.


All the best

Peter

[1]
https://wiki.openoffice.org/wiki/Documentation/FAQ/Installation/How_do_I_install_OpenOffice.org_on_Linux%3f

On 11.11.18 17:14, JD wrote:

> Since there are several rpm files in each release,
> do you have a script that will install the rpm files
> in the correct order, rather than leaving it to the
> user to provide the filenames to dnf, or yum or whatver
> installation program is available?
>
> On 11/11/2018 08:04 AM, Daniel Gruno wrote:
>> On 11/11/2018 09.02, Peter Kovacs wrote:
>>> Hello Infra,
>>>
>>> we have a new Release ready. Can you prepare the Servers for the new
>>> Update? (On our Release Sheet it mentions you have to do something.)
>>>
>>> Please inform us on the time needed, and when ready.
>>
>> There shouldn't be anything needed on our end, presuming you're using
>> the standard process. We have consolidated services a while back, in
>> part to not have to worry about things like AOO releases.
>>
>>>
>>>
>>> Thank you.
>>>
>>>
>>> All the best
>>>
>>> Peter
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
>
>

starting 4.1.7 and 4.2.0 Releases

[Peter Kovacs]

Hello all,

I suggest that we start right away with an Parallel development of 4.1.7
Release branch. I nominate Matthias to be release manager. Are you
willing to go on this?

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.


I am not available at the moment for release manager. But it would be
good to continue, to be able to have release versions prepared.


All the best

Peter




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

Re: starting 4.1.7 and 4.2.0 Releases

[Peter Kovacs]

I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.

And to train releases is vital for us. 4.1.6 did not really bind any
developer, beyond security issues.

A 4.1.7 will keep the routine and knowledge active while we develop 4.2.0.


All the best

Peter

On 13.11.18 00:15, Andrea Pescetti wrote:
> On 12/11/2018 Patricia Shanahan wrote:
>> The way I see it, we should be keeping 4.1.x for security fixes that
>> cannot wait until 4.2.0. As such, we may need to decide to release
>> 4.1.7 at any time.
>
> Sure, this is obvious. Thanks for pointing it out and of course I
> agree with it. I was commenting on the idea to plan a 4.1.7 release,
> outside the "emergency mode" you mention.
>
> 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: starting 4.1.7 and 4.2.0 Releases

[Peter Kovacs]

Andrea,

I am just saying a 4.1.7 release has nothing to do with the efforts we
have to organize for 4.2.0.

I hope I upload now into the right place, but I have initiated the task.

All the best

Peter

On 13.11.18 00:48, Andrea Pescetti wrote:
> Peter Kovacs wrote:
>> I do not see your issue. Our release team works much faster then the dev
>> team progresses on 4.2.0.
>
> There is a major difference between a 4.1.x and a new release like
> 4.2.0: for 4.2.0 we need the entire community, not only what you call
> the "release team" and developers (read: localization efforts,
> organized QA efforts, a possible public beta, a baseline update...).
> If you believe that 4.2.0 is only for developers you are
> underestimating the task.
>
>> A 4.1.7 will keep the routine and knowledge active while we develop
>> 4.2.0.
>
> We have many millions of users. We must provide some value with a
> release. This meant waiting 11 months (and counting) between 4.1.5 and
> 4.1.6; if 4.1.6 has no major regressions, we can surely wait some
> months before considering a 4.1.7 (again, in a non-emergency situation).
>
> But I would really like that we stop talking about this virtual 4.1.7
> release and actually release 4.1.6 for real.
>
> 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: do I need 2 disk images of Apache Open Office?

[Peter Kovacs]

Hi RonS

What is a disk image? OpenOffice is packed as one executable dmg file.

These questions are better asked on us...@openoffice.apache.org.

All the best

Peter

On 13.11.18 01:22, Ron Slayton wrote:
> I see in finder on my MacBook Pro that I have 2 disk images on my MacBook. Is 
> that normal. years ago when I started using AOO I may have mistakingly loaded 
> 2 versions, although I'm not sure. If I delete one version for disk space 
> reasons is that likely anything negative could happen?
>
>
> RonS

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

***UNCHECKED*** Re: starting 4.1.7 and 4.2.0 Releases

[Peter Kovacs]

Release is now in the svn branch.

I remove tonight the 4.1.5 release, any objections?

So how much time do we need? is release date 16th November feasable?

On 13.11.18 01:30, Peter Kovacs wrote:
> Andrea,
>
> I am just saying a 4.1.7 release has nothing to do with the efforts we
> have to organize for 4.2.0.
>
> I hope I upload now into the right place, but I have initiated the task.
>
> All the best
>
> Peter
>
> On 13.11.18 00:48, Andrea Pescetti wrote:
>> Peter Kovacs wrote:
>>> I do not see your issue. Our release team works much faster then the dev
>>> team progresses on 4.2.0.
>> There is a major difference between a 4.1.x and a new release like
>> 4.2.0: for 4.2.0 we need the entire community, not only what you call
>> the "release team" and developers (read: localization efforts,
>> organized QA efforts, a possible public beta, a baseline update...).
>> If you believe that 4.2.0 is only for developers you are
>> underestimating the task.
>>
>>> A 4.1.7 will keep the routine and knowledge active while we develop
>>> 4.2.0.
>> We have many millions of users. We must provide some value with a
>> release. This meant waiting 11 months (and counting) between 4.1.5 and
>> 4.1.6; if 4.1.6 has no major regressions, we can surely wait some
>> months before considering a 4.1.7 (again, in a non-emergency situation).
>>
>> But I would really like that we stop talking about this virtual 4.1.7
>> release and actually release 4.1.6 for real.
>>
>> 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: ***UNCHECKED*** Re: starting 4.1.7 and 4.2.0 Releases

[Peter kovacs]

Okay I need to check.
4.1.5 delete as last step, check.

Am 13. November 2018 11:32:20 MEZ schrieb Matthias Seidel 
:
>Hi Peter,
>
>Am 13.11.18 um 08:04 schrieb Peter Kovacs:
>> Release is now in the svn branch.
>
>There are a lot of languages missing...
>
>https://dist.apache.org/repos/dist/release/openoffice/4.1.6/binaries/
>
>https://www.apache.org/dist/openoffice/4.1.6/binaries/
>
>Regards,
>
>   Matthias
>
>>
>> I remove tonight the 4.1.5 release, any objections?
>>
>> So how much time do we need? is release date 16th November feasable?
>>
>> On 13.11.18 01:30, Peter Kovacs wrote:
>>> Andrea,
>>>
>>> I am just saying a 4.1.7 release has nothing to do with the efforts
>we
>>> have to organize for 4.2.0.
>>>
>>> I hope I upload now into the right place, but I have initiated the
>task.
>>>
>>> All the best
>>>
>>> Peter
>>>
>>> On 13.11.18 00:48, Andrea Pescetti wrote:
>>>> Peter Kovacs wrote:
>>>>> I do not see your issue. Our release team works much faster then
>the dev
>>>>> team progresses on 4.2.0.
>>>> There is a major difference between a 4.1.x and a new release like
>>>> 4.2.0: for 4.2.0 we need the entire community, not only what you
>call
>>>> the "release team" and developers (read: localization efforts,
>>>> organized QA efforts, a possible public beta, a baseline
>update...).
>>>> If you believe that 4.2.0 is only for developers you are
>>>> underestimating the task.
>>>>
>>>>> A 4.1.7 will keep the routine and knowledge active while we
>develop
>>>>> 4.2.0.
>>>> We have many millions of users. We must provide some value with a
>>>> release. This meant waiting 11 months (and counting) between 4.1.5
>and
>>>> 4.1.6; if 4.1.6 has no major regressions, we can surely wait some
>>>> months before considering a 4.1.7 (again, in a non-emergency
>situation).
>>>>
>>>> But I would really like that we stop talking about this virtual
>4.1.7
>>>> release and actually release 4.1.6 for real.
>>>>
>>>> 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
>>
>>

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

Report from OpenRheinRuhr 2018 convention

[Peter Kovacs]

Hi all,

The OpenRheinRuhr [0] event is a local convention around open source
software in Germany. The program is a mix of talks and booth
presentations. The event took place this year on the 3rd and 4th November.

Our booth team usually visits this event every year. This year has been
special. On initiative of Uwe Altmann from the LibreOffice Community the
booth has been shared between Apache Open Office, EGroupware and
LibreOffice. (sorted in alphabetical order) The booth teams have a long
tradition to meet on events, and this year is the first official
collaboration between all 3 projects.

For Apache OpenOffice have represented by our volunteers Mechtilde,
Michaela und Michael Stehmann. LibreOffice has been represented by
Regina Henschel and Uwe Altmann. EGroupware have been represented by
Stefan. The booth have been visited by various people known in the
german Office Community. From our dev community Matthias Seidel and I
visited on Sunday. The atmosphere on the common booth has been relaxed
and coined by friendship.

Uwe Altman held a talk on the advantages of the ODF format on Saturday,
while Stefan talked about LibreOfficeOnline in EGroupware.

Because of a no show for a talk around LibreOffice, from an unknown
speaker to everyone present at the time at the booth, Uwe Altmann
invited us to share the replacement talk, which Michael and I gladly
accepted. Michael talked about the history of OpenOffice, I said one or
2 sentence about our presence situation, while Uwe Altmann and Regina
Henschel represented the LibreOffice side. In the second part of the
talk we improvised a short writer workshop with Regina Henschel as main
talker supported by the rest of us. Uwe Altmann finished the talk with a
short compare between ODF and OOXML.

The composed booth teams agreed that the cooperation and collaboration
of all three teams (LibreOffice, EGroupware and Apache OpenOffice
(reversed alphabetical order ;) )) were a success and that this should
be continued and extended if possible. In total we all have left the
event with the feeling that bonds have been strengthened.


This is a rough conversion from Michael's german report [1]. The Report
of Uwe Altmann on the german LibreOffice List [ 2]. Both reports are in
german (of course).


All the best

Peter Kovacs

[0] https://openrheinruhr.de/

[1]
https://lists.apache.org/thread.html/9a7fb9d2b666d2d06fb684aa0cb3bb61dc53c43ae620af79f9b8e674@%3Cdev-de.openoffice.apache.org%3E

[2]  https://listarchives.libreoffice.org/de/discuss/msg22530.html



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

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1

[Peter Kovacs]

Ok. This is done.

On 05.11.18 23:21, Andrea Pescetti wrote:
> Peter Kovacs wrote:
>> So now the rules state I should sign all artifacts. Others may
>> concatenate their signature if they want. Do we follow this?
>
> No, you need to sign only three files, the three source files. And you
> should remove the existing three corresponding .asc files since
> multiple signatures in the same .asc file are not officially
> supported. So others should not append signatures. All details are in
> my message.
>
> 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: moving to git !?

[Peter Kovacs]

Maybe it is nice to be aware on the differences between svn and git [0]

As a quick start comparison of commands is helpful [1]

For Windows there is also a tortoise client [2]. However if you use
tortoise for svn too, be careful. Last time I wanted to use both I had
some trouble.

github [3] and atlasians bitbucket [4] have some tutorials. Even both
refer to their own cloud, but that is I think not big deal to think of
our online repo instead.

[0] https://git.wiki.kernel.org/index.php/GitSvnComparison

[1] http://git.or.cz/course/svn.html

[2] https://tortoisegit.org/

[3] https://try.github.io/

[4] https://www.atlassian.com/git/tutorials/learn-git-with-bitbucket-cloud

On 06.11.18 06:16, Patricia Shanahan wrote:
> I am going to have to learn git. No big deal - revision control
> systems go out of fashion every few years and it becomes time to learn
> a currently fashionable one.
>
> Can you recommend a book or tutorial? I've used RCS and SCCS as well
> as, obviously, Subversion.
>
> On 11/5/2018 2: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.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E
>>
>>
>>
>> It was somewhat unlucky. We should start to prepare the move. I think it
>> is okay to do this now. After that we should start with 4.1.7 release
>> and 4.2.0 release preparations.
>>
>> We can also start the uno split if Damjan is still in this idea.
>>
>>
>> Also we need to check on the pull workflow with infra. Any volunteers to
>> do this?
>>
>> Any Concerns with this initiative?
>>
>>
>>
>> -
>> 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: Does OpenOffice still use Serf?

[Peter kovacs]

How about trying to open an URL as a test case?

Is serf moving away from SCONs? I ask since we want to move to SCONs. An 
experience exchange would be great.

All the best
Peter


Am 13. November 2018 22:43:03 MEZ schrieb Matthias Seidel 
:
>Hi Andrea,
>
>Am 13.11.18 um 22:23 schrieb Andrea Pescetti:
>> Matthias Seidel wrote:
>>> I think it would be a good idea to upgrade Serf in our builds.
>>> What about the others (real developers)? ;-)
>>
>> Years ago, we had to avoid upgrading Serf in 4.1.x as Serf had
>started
>> to require SCons for the build and we didn't want to introduce yet
>> another build system since we already had too many.
>>
>> I see it still requires SCons, but probably we've included support
>for
>> SCons in trunk in the meantime, so... well, we decided we can live
>> with yet another build system! Still, I doubt we can use it for 4.1.x
>> as SCons integration would be needed and I don't think we support it
>> in 4.1.x.
>
>I forgot to mention that I indeed build with trunk. And the build is
>still going on, so anything can happen... ;-)
>
>I will keep you updated!
>
>Regards,
>
>   Matthias
>
>>
>> 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: New OpenOffice Release 4.1.6 Release Preperations

[Peter Kovacs]

No you are responsible for doing so.

These are highly experimental test versions. Even when we agreed that
the code revision is good for release.

May I ask what do you want to do with OpenOffice-4.1.6-RC1?


On 11.11.18 19:07, JD wrote:
> But you have a directory in the directory where the rpm's are.
> How are the rpm's in the subdirectory chosen, since only one of them
> should be selected?
>
> For example, in the directory
> OO-en-US/RPMS
> exists the directory desktop-integration/
> which in turn contains
> openoffice.org3.4-freedesktop-menus-3.4-9593.noarch.rpm
> openoffice.org3.4-redhat-menus-3.4-9593.noarch.rpm
> openoffice.org3.4-mandriva-menus-3.4-9593.noarch.rpm
> openoffice.org3.4-suse-menus-3.4-9593.noarch.rpm
>
> So, does the package install manager know which of these
> desktop integration menus to pick up for the OS at hand?
>
>
>
>
>
> On 11/11/2018 09:47 AM, Peter Kovacs wrote:
>>
>> Normally the package manager knows the right order. That why you have it.
>>
>> you load everything you want to update in one folder and then say
>> *rpm -Uvih *rpm*.
>>
>> As it is mentioned in our Howto [1], btw.
>>
>>
>> All the best
>>
>> Peter
>>
>> [1]
>> https://wiki.openoffice.org/wiki/Documentation/FAQ/Installation/How_do_I_install_OpenOffice.org_on_Linux%3f
>>
>> On 11.11.18 17:14, JD wrote:
>>
>>> Since there are several rpm files in each release,
>>> do you have a script that will install the rpm files
>>> in the correct order, rather than leaving it to the
>>> user to provide the filenames to dnf, or yum or whatver
>>> installation program is available?
>>>
>>> On 11/11/2018 08:04 AM, Daniel Gruno wrote:
>>>> On 11/11/2018 09.02, Peter Kovacs wrote:
>>>>> Hello Infra,
>>>>>
>>>>> we have a new Release ready. Can you prepare the Servers for the new
>>>>> Update? (On our Release Sheet it mentions you have to do something.)
>>>>>
>>>>> Please inform us on the time needed, and when ready.
>>>>
>>>> There shouldn't be anything needed on our end, presuming you're
>>>> using the standard process. We have consolidated services a while
>>>> back, in part to not have to worry about things like AOO releases.
>>>>
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>> All the best
>>>>>
>>>>> Peter
>>>>>
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>
>>>>
>>>
>>>
>

Re: Does OpenOffice still use Serf?

[Peter kovacs]

Yea platform specific code should be avoided. But in my humble opinion that is 
not an issue of the build system itself but of suboptimal usage.

Thanks for your view! :)

Am 14. November 2018 13:08:21 MEZ schrieb "Branko Čibej" :
>On 14.11.2018 08:16, Peter kovacs wrote:
>> How about trying to open an URL as a test case?
>>
>> Is serf moving away from SCONs?
>
>I surely hope so.
>
>> I ask since we want to move to SCONs. An experience exchange would be
>great.
>
>Well ... SCons looks amazingly good in tiny examples, but when it comes
>to doing anything less than trivial, it's a nightmare. For example, I'm
>not thrilled that we have platform-specific Python code in Serf's
>SConstruct, and that's not even a very complex build at all. So, whilst
>I really hate CMake for its inconsistencies and homegrown horrible
>macro
>language, I like SCons quite a bit less.
>
>All of the above is my "humble" opinion of course.
>
>-- Brane
>
>
>> Am 13. November 2018 22:43:03 MEZ schrieb Matthias Seidel
>:
>>> Hi Andrea,
>>>
>>> Am 13.11.18 um 22:23 schrieb Andrea Pescetti:
>>>> Matthias Seidel wrote:
>>>>> I think it would be a good idea to upgrade Serf in our builds.
>>>>> What about the others (real developers)? ;-)
>>>> Years ago, we had to avoid upgrading Serf in 4.1.x as Serf had
>>> started
>>>> to require SCons for the build and we didn't want to introduce yet
>>>> another build system since we already had too many.
>>>>
>>>> I see it still requires SCons, but probably we've included support
>>> for
>>>> SCons in trunk in the meantime, so... well, we decided we can live
>>>> with yet another build system! Still, I doubt we can use it for
>4.1.x
>>>> as SCons integration would be needed and I don't think we support
>it
>>>> in 4.1.x.
>>> I forgot to mention that I indeed build with trunk. And the build is
>>> still going on, so anything can happen... ;-)
>>>
>>> I will keep you updated!
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>> 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

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

build errors when building 4.1.6

[Peter Kovacs]

Hi all,

 when building python I get a segementation fault error.

Does anyone has a solution for this:

/usr/bin/ld: Modules/posixmodule.o: in function `posix_tmpnam':
/home/legine/workspace/ApacheOpenOffice/svn/main/python/unxlngx6.pro/misc/build/Python-2.7.6/./Modules/posixmodule.c:7545: 
warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'

/usr/bin/ld: Modules/posixmodule.o: in function `posix_tempnam':
/home/legine/workspace/ApacheOpenOffice/svn/main/python/unxlngx6.pro/misc/build/Python-2.7.6/./Modules/posixmodule.c:7492: 
warning: the use of `tempnam' is dangerous, better use `mkstemp'

gcc -pthread  -Xlinker -export-dynamic -o python \
    Modules/python.o \
    -L. -lpython2.7 -lpthread -ldl  -lutil   -lm
LD_LIBRARY_PATH=/home/legine/workspace/ApacheOpenOffice/svn/main/python/unxlngx6.pro/misc/build/Python-2.7.6:/home/legine/workspace/ApacheOpenOffice/svn/main/solver/416/unxlngx6.pro/lib 
./python -E -S -m sysconfig --generate-posix-vars

Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
make: *** [Makefile:468: pybuilddir.txt] Segmentation fault (core dumped)
dmake:  Error code 2, while making 
'./unxlngx6.pro/misc/build/so_built_so_python'



All the best

Thanks

Peter


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

Re: OO 4.2.0 problem Page Background

[Peter Kovacs]

Rory do you refer to this Issue 
https://bz.apache.org/ooo/show_bug.cgi?id=127805.


Matthias has posted some crash analysis pointing to a function. I 
reviewed the code tonight. Just read it and analyzed it. It looked fine 
on first glance.


I think it could be an Binary Issue between FreeType 2.6.x and 2.8.x. I 
guess it happened in 2.7.x because I had this issue before FOSDEM 2017, 
and Arch Linux has used 2.7 at that time.



On 10/9/18 10:11 AM, Rory O'Farrell wrote:

For information:

On a Windows XP machine (32 bit) I have installed AOO 4.2.0 (en-US) version 1842967.  The Page 
Format shows "Area" (not "Background", as on Linux 64 version) as a tab, and I 
can change a page background on the Windows version.  The crash in Impress, when selecting a Master 
Page, does not occur on that Windows version.

On my preferred machine, running AOO 4.2.0 (en-US) 2018-10-05_08:36:16 - Rev. 
184287 on Xubuntu 18.04.1 64 bit I find the following differences from the 
Windows version.

1) Page Background tab in Linux is called Area tab in Windows
2) Page Background does not work in Writer in Linux (i.e., that tab is 
inactive).  Works OK (as Area tab) in Windows
3) Selecting Master Page sidebar in Impress Linux DEB 64 crashes OO.  Works OK 
in Windows.

Matthias Seidel tells me that his version of OO on Linux uses Area, not Page to 
apply the Page backgrounds.

The Page background problem also showed up on AOO 4.1.6 (linux DEB 64 version); 
others have reported the crash with Master Pages in Impress on that version.  I 
have not investigated the 4.1.6 version on a Windows machine.



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

[discussion] unmaintained and unsupported Apache CMS

[Peter Kovacs]

Well it turns out the Apache CMS system we use for our download side is 
unmaintained and unsupported.


If the system breaks it takes weeks to get someone to fix it. This 
turned up in a discussion on the private list.


I start / move the discussion to the dev list because stuff that turns 
up in private tends to get stuck there.


It is something we should address mid term.

If you have made some suggestions it would be great if you could repeat.


infra has no suggestions how to deal with the issue. They tend to use 
Pelican for building from markdown.


We use rewrapped html. So thats not working out for us I guess.

Dave suggested to use the CMS build script within Github, or maybe 
Jenkins. (Mentioning Dave, because he mentioned to move the discussion 
should move to dev. So I assume it is fine to mention him.)



I hope I did not spoil anything, and do not get hit like the last time. :/


All the best

Peter


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

current OpenOffice Flyers

[Peter Kovacs]

Hi all,

the german community has updated our flyers.

Current Version can be found at [1]

If you are french or english native speaker, please have a look.

And give some feedback, thanks.


All the best

Peter

[1] https://drive.google.com/drive/folders/1kpVknzJfZwuV5TOFvezg1V_TZLoSgYaY


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

Re: svn commit: r1843108 - in /openoffice/branches/AOO416: ./ ext_libraries/serf/ main/ main/redland/ main/redland/prj/ main/redland/raptor/ main/redland/rasqal/ main/redland/redland/ main/scp2/source

[Peter Kovacs]

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 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 schrieb pe...@apache.org:

Author: petko
Date: Mon Oct  8 06:09:21 2018
New Revision: 1843108

URL: http://svn.apache.org/viewvc?rev=1843108=rev
Log:
merged in: Issue 127887 - update bundled redland/raptor/rasqal

Added:
 
openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.dmake

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.dmake
 
openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.os2

    - copied unchanged from r1818098,
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.os2
 
openoffice/branches/AOO416/main/redland/raptor/raptor2-2.0.15.patch.win32

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/raptor/raptor2-2.0.15.patch.win32
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.dmake


    - copied unchanged from r1757789,
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.dmake
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.ooo_build

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.ooo_build
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.33.patch.win32


    - copied unchanged from r1757789,
openoffice/trunk/main/redland/rasqal/rasqal-0.9.33.patch.win32
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.autotools

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.autotools
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.dmake

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.dmake
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.ooo_build

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.ooo_build
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.os2


    - copied unchanged from r1818098,
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.os2
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.17.patch.win32

    - copied unchanged from r1757789,
openoffice/trunk/main/redland/redland/redland-1.0.17.patch.win32
Removed:
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.autotools
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.dmake


 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.fixes


 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.ooo_build
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.os2
 
openoffice/branches/AOO416/main/redland/raptor/raptor-1.4.18.patch.win32


 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.autotools
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.dmake


 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.ooo_build
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.os2
 
openoffice/branches/AOO416/main/redland/rasqal/rasqal-0.9.16.patch.win32


 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.autotools
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.dmake
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.ooo_build
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.os2
 
openoffice/branches/AOO416/main/redland/redland/redland-1.0.8.patch.win32

Modified:
  openoffice/branches/AOO416/   (props changed)
  openoffice/branches/AOO416/ext_libraries/serf/makefile.mk
  openoffice/branches/AOO416/main/   (props changed)
  openoffice/branches/AOO416/main/configure.in
  openoffice/branches/AOO416/main/external_deps.lst
  openoffice/branches/AOO416/main/redland/   (props changed)
  openoffice/branches/AOO416/main/redland/prj/d.lst
  openoffice/branches/AOO416/main/redland/raptor/makefile.mk
  openoffice/branches/AOO416/main/redland/rasqal/makefile.mk
  openoffice/branches/AOO416/main/redland/redland/makefile.mk
  openoffice/branches/AOO416/main/redland/redlandversion.mk
 
openoffice/branches/AOO416/main/scp2/source/ooo/file_library_ooo.scp


Propchange: openoffice/branches/AOO416

Re: html code generated from Open Office

[Peter Kovacs]

I took a quick glance at the html filter code in writer. Maybe another 
thing why the code is hard to read is that most comments are in german. 
We do translations on demand. If you are interested in a specific file 
then best practice is to write a comment in 
https://bz.apache.org/ooo/show_bug.cgi?id=39199.


Some examples how to read includes:

#include  Check the vcl module -> main/vcl/inc/vcl/svapp.hxx

#include  check sfx2 module -> 
main/sfx2/inc/sfx2/docfile.hxx


#include  Okay this is special, since it 
refers to Javacode. But I do not know how to find the corresponding Java 
class file.


Sadly we are still restoring OpenGrok, so no help there atm. I am 
searching through Eclipse but that takes ages. Maybe someone has an Idea?


HTH

Peter


On 10/1/18 10:07 PM, Howard Cary Morris wrote:


Looked at code, tried to anyway. Way to many includes, which I don’t 
know how to look up.


I’d be better off with compiled code for modules with all includes 
expanded.


Included read me text of my server code to convert so far.

While I am thinking of it, saw an earlier email about source of help.

For online help, create with Writer and export as .xhtml file headers 
and footers not exported.


Tried dumping .odt file. I could not see text or fonts (must be 
encoded). But other parts were not encoded (like meta data). Seemed to 
waste a lot of space. Saw a lot of other stuff that made it seem like 
our files are being fed into a another language (xml?)


May consider combining .html and .xhtml files for better creation.

Howard

*From: *Howard Cary Morris 
*Sent: *Thursday, September 13, 2018 1:03 AM
*To: *dev@openoffice.apache.org 
*Cc: *Apache OO 
*Subject: *RE: html code generated from Open Office

Only reason I want to see Print and print preview code is that I want 
the HTML5 look identical to printed code. I will have additional 
references to understand the code.




Sent from Mail for 
Windows 10





From: Damjan Jovanovic 
Sent: Wednesday, September 12, 2018 7:59:53 PM
To: Howard Cary Morris
Cc: Apache OO
Subject: Re: html code generated from Open Office

Those modules are in our source code, see this link about getting it:
https://openoffice.apache.org/source.html
Building it is quite involved :-/.

What are you looking for in terms of printing?

ODT files are documented but it's a lot of documentation:
https://www.oasis-open.org/standards#opendocumentv1.2

Damjan


On Wed, Sep 12, 2018 at 10:00 PM Howard Cary Morris <
howard_cary_mor...@hotmail.com> wrote:

> OK, where can I get a copy of that module for Writer?
>
> Would also like a copy of module that does print and one that does view
> preprint.
>
> (Mainly for comparison purposes.)
>
> If there is documentation of the format of the .odt files, I might 
be able

> to write the module from scratch.
>
>
>
> Howard
>
>
>
> *From: *Damjan Jovanovic 
> *Sent: *Monday, September 3, 2018 11:20 PM
> *To: *Apache OO ;
> howard_cary_mor...@hotmail.com
> *Subject: *Re: html code generated from Open Office
>
>
>
> Hi
>
>
>
> If it was me, I said:
>
> The code for the "Save As" -> "HTML document" feature seems to be in:
>
>
>
> main/sc/source/filter/html
>
> for Calc, and
>
> main/sw/source/filter/html
>
> for Writer.
>
> (Not sure if there are more?)
>
>
>
> Thank you for your contribution, and please let us know if you need any
> further help.
>
> Damjan
>
>
>
> On Tue, Sep 4, 2018 at 2:55 AM Howard Cary Morris <
> howard_cary_mor...@hotmail.com> wrote:
>
> Sorry, I seem too have deleted a more recent version of this request.
> Someone sent me name of module that gets invoked for a save as HTML
> request.
> I also like to compare that with the module that does the print request
> and the module that does the print preview. What are all those 
module names.

> Where can I download those modules from?
>
> Thanks Howard
>
> Sent from Mail 
>

> for Windows 10
>
> 
> From: Howard Morris (aka Col Boogie) 
> Sent: Monday, January 5, 2015 10:36:20 PM
> To: dev@openoffice.apache.org
> Subject: html code generated from Open Office
>
> The reason I joined Open Office was to enhance the html code generated
> from writer.
>
> For now, I have constructed html code to upload an html file 
generated by
> Open Office and PHP code to tweak that code and download a better 
version.
> Everything I have doe so far is in the attached zzz.zip file. 
Explanations

> are in Readme.txt
>
> I would have liked to have done this directly, 

Please commit code to 4.1.6

[Peter Kovacs]

Hi all,


Please commit the code patches to the 4.1.6 branch for the accepted 
issues to the branch. Thank you for helping.



All the best

Peter


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

Re: Other build ideas

[Peter Kovacs]

At first glance it looks like it wants what we want, but on second 
glance it describes the removal of UNO from OpenOffice, and divide the 
Monolithic package we have into 3 packages along the layers. I think it 
is what Libre Office has already done. But for sure it will give hints 
on the issues we might face.


The Idea is to reuse old Architecture design for the SCon and MSVC 
migration, but stay in the monolithic package. It is more a move towards 
a stronger and better inner architecture, with the goal to be better 
able to do maintenance. I do really prefer your Idea on creating an UNO 
Project from OpenOffice in the long run when it comes to deviding the 
project into smaller Packages. This is a really strong OpenSource move. 
It creates opportunities for cooperation with other Projects. This is a 
good long term goal.


I only suggest to move along the bottom Layer because i hope for reduced 
refactoring work. Also I hope that the risk in steering up something bad 
is lower. So we can have a good success while migrating.



On 10/6/18 7:18 AM, Damjan Jovanovic wrote:

Those links are in the wrong category then. They refer to OOo not the ODF
Toolkit.

On Sat, Oct 6, 2018 at 3:54 AM Dave Fisher  wrote:



Sent from my iPhone


On Oct 5, 2018, at 6:37 PM, Damjan Jovanovic  wrote:

The links you are looking for are:
https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/OOo_without_URE
https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/Three-Layer_OOo

ODF Toolkit is still in the Incubator. It’s just Svante and it will likely
retire. It might end up with TDF.


Let's leave the split for now. It's not going to help us directly.

Agreed.

Regards,
Dave

On Fri, Oct 5, 2018 at 11:59 PM Peter Kovacs  wrote:

Hi all,

I am a bit skeptical about the 2 Layer approach. OpenOffice has been
designed in a 3 Layer Architecture. This can be seen here.

https://wiki.openoffice.org/wiki/File:ArchOverview.jpg

As this documentation states the Lower Layer does not only consists of
the UNO Group but also of UCB, ConfigManager, GSL.

I do prefer actually to maybe build a containment along these "old"
Layers instead of cutting UNO out. I hope it causes less refactoring

work.


Of course we would not be able do start a UNO - SpinOff Project right
away, but we would get similar advantages, with maybe less work.

We can do a Spinoff maybe later, I like the Idea in general to have some
of the Contrsucts that make OpenOffice so awesome offer to other
Projects in order to get people with different goals to colaborate.

our BASIC Language is also such a topic. But I think this are lower
priorities with the project power we currently have.


Damjan, George do you see any Issues with my plan or would you prefer
the initial Idea?


Thanks guys for the thoughts. They are really good IMHO.


On 10/5/18 8:45 PM, George Karalis wrote:
Hello everyone,

Since am new to the project and working on understanding the build

process this past

week, I agree with Damjan that the build system needs that overhaul. I

also agree that

a MSVC upgrade and a 64-bit windows build, is of high priority.

Changing

the build

system will take months.

As of the MSVC upgrade I have figured out how the whole configure works

and I ‘m

now integrating MSVC++ 14.15 to oowintool script, and trying to

integrate Windows 10

SDK to the configure pipeline as well. After that I 'll try to figure

out the build errors and

fix everything to a successful build. If and when the upgrade

completes,

we should also

investigate implementing targets - if there are none - for the build

tool.

e.g. To compile for windows XP, we need the Windows XP platform

toolset,

which installs

Windows 7.1 SDK, among other things and can build for Windows XP using

MSCV++

2017 and run something like: build —all —target=“winXP”.

Since I am unfamiliar with UNO, I can’t provide any points there, but I

agree with that

separation of concerns, to keep only office functionality at the core

of

the project. Also

another future idea would be to split - I don’t know if it's possible -

each application,

Writer, Calc, Impress etc. in its own separate module, so they can

build

independently

and, maybe?, debug easier, since someone can work on features on only

the app he/she

wants.

As for the build system, after some research, I concluded on three

modern build pipelines,

CMake, SCons and Meson. Personally, I am in favour of CMake, with the

only argument

that it’s backed by many large companies and that provides a safety for

the future. The two

systems are almost identical, SCons is more extensible due to Python,

but all in all

it’s just a weight of each build system's pros and cons. Also, how KDE

switched  <https://lwn.net/Articles/188693/>

to CMake <https://lwn.net/Articles/188693/> was an interesting read.

But, I think Damjan knows better about the project, so

we can have an open discussion about which build system is better for

OpenOffice.

external_debs.lst not found on 4.1.6

[Peter Kovacs]

Hi all,

I try to move patches from trunk to 4.1.6 and found that the file 
external_debs.lst is missing.


What to do with the changes? Did the file change?


all the best

Peter


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

Have SVN access again. :)

[Peter Kovacs]

Well in the end it was a banned IP.

And I have checked out 4.1.6 twice, because I messed my workspace up. 
However the Check in did not work for month. Maybe It is a combination 
and I always did something that did get me on the banned list.


However maybe other people cause the issue since my ISP uses the IP 
Address for multiple of their clients, and will probably force me to 
switch IP address in 40 Minutes.


Lets watch how long it takes until I can not check in.


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

[Review] Community status report

[Peter Kovacs]

Hello all,

I have written this evening a Blogpost draft. Since I think it is hard 
to start with one and we lack communications with the outside world I 
tried to write one that gives a high level technical overview what is 
going on.


I hope this is okay, I fear it is still quite too technical. And I hope 
the basic idea is okay and the tone is good.


I am glad for contributions and critics. :)

 All the Best

Peter

 Blog Post draft 
##


Hello World!

My name is Peter Kovacs and I am the current Chairman of OpenOffice. The 
Chairman is a secretary job that writes the reports to the foundation 
board, in order to inform them on the state of the Project.


I do this in my freetime, next to work and on top of all the other 
things thatt happen in live. Unpaied of course. This is currently true 
for all volunteers active on OpenOffice.


The current situation in development can be devided in 3 main activities.

1.

   Code release and maintenance.

2.

   Upgrade dependencies

3.

   Build environment updates

On the first level we have a gap between Code development and code that 
has been released. We usually refer to this as 4.1.x line and trunk. We 
have the challenge that the quality of trunk line is not in release 
state, and the 4.1.x line is quite behind the trunk line. So from time 
to time we make maintenance releases, of the old 4.1.0 line in order to 
keep OpenOffice functional. While we try to enhance the trunk code to be 
able to be released as 4.2.0. We try to fix bugs on the way and update 
dependencies, or create enhancements as possible.


If we look at the code system dependencies, OpenOffice uses old Windows 
SDK and MacOSx SDK. Current 4.1.x line is build on top of Windows 7 SDK 
which is not publicly available any more. For Mac the Line is on 10.7. 
For 4.2.0 we want to use Windows 10 SDK and for Mac also newer ones. 
However these updates are quite difficult to do in some code regions of 
OpenOffice. We are also working on a 64bit version.


If we take a look at the build process, the situation is quite 
difficult. OpenOffice is very complex software, clustered in a lot of 
modules. The technique used to do this is 20 years old. We try to 
modernize the environment. This process is very difficult in some 
regions of the code. Also we need to migrate to a environment that is 
potential supporting all plattforms the code recieves contributions 
from. That are the community supported Windows, MacOs and Linux 
plattforms, plus FreeBSD and OS/2 plattforms where we recieve upstream 
patches from these plattform communities.


Additional enhancements mainly depend on additional Volunteer 
contributions. We try to support these on the development community 
level the best to our capabilities, but it depends on the additional 
volunteers, who are involved.


I hope this gives you a feeling what is going on. It is like a big 
Gordian knot, and we are forging the sword to cut it. It might be not 
innovative, but we believe with each step we make forward OpenOffice is 
becomming a more sturdy Office suite. It is a long road ahead of course.

Re: Lazy consensus on adoption of corrected Apache OpenOffice logo file

[Peter kovacs]

Hi all,

I agree that the "TM" displacement should be fixed. However I do not see that 
we have to change something to the design.
So is it possible to change the original with something that would enhance the 
situation without changing other attributes?
All the best
Peter

Am 31. August 2018 15:48:46 MESZ schrieb Matthias Seidel 
:
>Hi Pedro,
>
>Am 31.08.2018 um 01:09 schrieb Pedro Lino:
>> Hi Dave, all
>>
>>> On August 30, 2018 at 11:17 PM Dave Fisher 
>wrote:
>>> You can ask for Lazy Consensus on this and give 72 hours for anyone
>to object.
>> Thanks!
>>
>> As suggested, I'm asking for Lazy Consensus on the adoption of file
>http://svn.apache.org/repos/asf/openoffice/branding/AOO4/Apache_OpenOffice_Logo_unofficial_mseidel_fixed_TM.svg
>> as the official vector file for the Apache OpenOffice logo (see
>explanation below).
>> If after 72 hours there are no objections, the file will be renamed
>appropriately and used as the official vector file.
>
>Sorry, if I am late to this discussion...
>
>My graphic was never meant to replace the official one.
>It was more or less a proof of concept and it does not respect the
>"white" space intentionally designed by Chris Rottensteiner.
>
>See:
>https://svn.apache.org/repos/asf/openoffice/branding/AOO4/ChrisR_Notes.txt
>
>My suggestion would rather be to "fix" the existing graphic by only
>converting the TM to paths.
>
>Regards,
>   Matthias
>
>>  
>>> I’m +1 for pure shapes and no text. Maybe comment inline each glyph.
>> I would prefer not to modify the file at this point. In any case this
>email and explanation are public.
>>
>> Regards
>> Pedro
>>
 On Aug 30, 2018, at 2:41 PM, Pedro Lino 
>wrote:

 Hi all

 I don't know what is the appropriate procedure but would like to
>request a vote for the adoption of a corrected Apache OpenOffice logo
>vector file.

 Most of you are aware that the current logo was created by Chris
>Rottensteiner .

 Unfortunately all of the logos in vector format archived in the
>Apache OpenOffice (or at least all that I could find) left by ChrisR
>(http://svn.apache.org/repos/asf/openoffice/branding/AOO4/ ) have the
>same problem: the TM part is a text object.

 This means that editing or viewing the SVG only looks as the author
>expected
>(http://svn.apache.org/repos/asf/openoffice/branding/AOO4/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_with_4.pdf)
>it if the user's computer has font Source Sans Pro Light installed.

 An easy way to see this is to click on the AOO logo at


>https://en.wikipedia.org/wiki/File:Apache_OpenOffice_logo_and_wordmark_(2014).svg

 After clicking on the expected logo as PNG you will open the actual
>SVG which will be showing a wrong TM

 Because of this small defect, there is no perfect SVG that can be
>used as Apache OpenOffice's official logo, and that is the reason why
>the current official logo available to Apache is a PDF

 https://svn.apache.org/repos/asf/comdev/project-logos/originals/

 Luckily user Matthias Seidel has fixed this by converting the TM
>part to paths (as ChrisR did for the rest of the text)

 This does NOT change the artwork in any way. It just guarantees
>that the vector logo looks the same under any OS regardless of the
>fonts installed.


 TL:DR

 Therefore I would like to propose a vote to approve file
>http://svn.apache.org/repos/asf/openoffice/branding/AOO4/Apache_OpenOffice_Logo_unofficial_mseidel_fixed_TM.svg

 as the Apache OpenOffice official vector logo file


 Best regards,

 Pedro
>>>
>>>
>-
>>> 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: Do we have a functional 64 bit version for Windows

[Peter Kovacs]

Maybe this Error Report is the next?

https://bz.apache.org/ooo/show_bug.cgi?id=127774

On 9/21/18 8:43 PM, Damjan Jovanovic wrote:

No. I began working on it, but it's not even remotely finished.

If you wish to help, build on a Win64 setup with --enable-win64 passed to
./configure. The build will break eventually, and the module it breaks in
is the next module you have to port ;).

Damjan

On Fri, Sep 21, 2018 at 7:58 PM Keith N. McKenna 
wrote:


In reviewing Issue 125006
(https://bz.apache.org/ooo/show_bug.cgi?id=125006) I find that one of
the possible causes was suggested to be that these large spreadsheets
may be running close to the memory limits allowable for 32 bit
applications. I would like to test the possibility of that by using a 64
bit version of Calc.

Regards
Keith




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

Re: Subscribe to Questions and Answers

[Peter kovacs]

Hi Tammy Curtis,

You can simply send your questions to the List, there is no need in subscribing 
in order to get some answers. But if you like to read our List or want to 
participate you are welcome to subscribe. This is a public project. It is open 
to anyone.

All the best
Peter

Am 23. September 2018 20:46:04 MESZ schrieb Tammy Curtis :
>May I subscribe to get questions and answers?
>
>Sent from Mail for Windows 10

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

Code signing for Mac

[Peter Kovacs]

Hi all,


I am currently sorting issues.

I came across the code signing issue:

https://bz.apache.org/ooo/show_bug.cgi?id=125360

That refers to a Infra ticket that has been closed in 2016 but we closed 
it in 2014, with a negative solution.



So since code signing is an issue that pops up now and then, I would 
like to know if we would like to do for the mac, general speaking?


If we are at +1, I don't understand why we have this closed.

All the best

Peter


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

Re: [Discussion] Program for Sandro

[Peter Kovacs]

Dear,

Have you asked a user Request? - Use a new thread for that please. - 
Hope you are still with us, it would be sad if you already stop.


All the best

Peter

On 9/11/18 5:15 PM, sandro wrote:

Dear,


It is amazing, a really exciting journey that follows the pumps of heart beat 
is a glad and fantastic way, this certainly guides us through patterns of 
satisfaction.


Well, I have posted here a working schedule, also I will post a work plan of 
the WikiProject that I feel that will bring achievements to the page. I will 
upload it here because it helps and guides me for the work, and I can update it 
every 2-3 weeks.


Glad,

Sandro Suzart





De: Andrea Pescetti 
Enviado: segunda-feira, 10 de setembro de 2018 02:08
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Peter kovacs wrote:

If you see something on our wiki-pages.
You can decide on yourself. There is no real command structure here.
If you need a user for editing the wiki, just write a request here.

Right. Sandro, if we haven't created a MWiki account for you yet, please
ask here. Otherwise, please give us your username so that we can (if
needed) extend permissions for you in order to be able to do some
configuration tasks.

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: ISO image of Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 ?

[Peter kovacs]

Maybe the One with .net 4 dies still Work?

https://www.microsoft.com/en-us/download/details.aspx?id=8442



Am 24. September 2018 20:12:34 MESZ schrieb Matthias Seidel 
:
>Hi all, Pat? Don? Damjan?
>
>Has anyone got an ISO image of "Microsoft Windows SDK for Windows 7 and
>.NET Framework 3.5 SP1" ?
>
>It is needed to build AOO on Windows. Support has ended and MS has
>pulled it from their server.
>
>The links in our Wiki are not working:
>https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10
>
>This is a major problem now for developers who want to set up a new
>building machine.
>
>Unfortunately I have only downloaded the web installer...
>
>Regards,
>
>   Matthias

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

Re: ISO image of Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 ?

[Peter Kovacs]

I see the only alternative to distribute vms. Matthias do you have a Windows 
VM? Alternative would be asking infra. 

Maybe porting to 2010 is not that hard?

All the best
Peter

Am 24. September 2018 20:53:41 MESZ schrieb Matthias Seidel 
:
>Hi Peter,
>
>Am 24.09.2018 um 20:49 schrieb Peter kovacs:
>> Maybe the One with .net 4 dies still Work?
>>
>> https://www.microsoft.com/en-us/download/details.aspx?id=8442
>
>Not according to our Wiki. That one contains MSVC 2010.
>There are also other problems installing it on Win 10 because of .NET
>Framework 4.
>
>If I only had downloaded the ISO... :-(
>
>Matthias
>
>>
>>
>>
>> Am 24. September 2018 20:12:34 MESZ schrieb Matthias Seidel
>:
>>> Hi all, Pat? Don? Damjan?
>>>
>>> Has anyone got an ISO image of "Microsoft Windows SDK for Windows 7
>and
>>> .NET Framework 3.5 SP1" ?
>>>
>>> It is needed to build AOO on Windows. Support has ended and MS has
>>> pulled it from their server.
>>>
>>> The links in our Wiki are not working:
>>>
>https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10
>>>
>>> This is a major problem now for developers who want to set up a new
>>> building machine.
>>>
>>> Unfortunately I have only downloaded the web installer...
>>>
>>> Regards,
>>>
>>>    Matthias
>> -
>> 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

Windows Build Environment futures (was: Open Office Contribution)

[Peter Kovacs]

Welcome George!

This sounds like you made up your mind for a long term volunteer 
project, which is awesome.  A big welcome from me. I hope you stay with 
us. Your mail sounds like you do not need much help. The recruitment has 
the Idea to help people to integrate better, by giving them a dedicated 
space to communicate.


Now lets root the discussion in to Dev Mailinglist. Please subscribe 
there. Damjan is our awesome contributer for Windows. If you 2 align 
that would be awesome. Please use the List, so all can participate.


We currently use MSVC 2008 for all releases, Damjan started to migrate 
to MSVC2015. A bigger jump to 2017 is fine for me, but keep in mind that 
we are standard wise behind 10 years the current standard. Especially on 
Linux we support Distributions, that do not have support for c++11. Also 
current conses is to keep Windows XP Compatibility.


At the same time, the migration from Windows 32bit Version to support 
64bit has been started. The build currently breaks somewhere. A 
continuation would be awesome.


And we are moving the build environment from dmake to gmake. There are 
65 modules left. This activity has a huge impact because all platforms 
are effected. And according to Damjan, the low fruits have been already 
migrated, and the ones left are not easy.


@Damjan, you still would like to migrate then to SCON after gmake, btw? 
I would still like to, even I do not count my voice much, because I did 
not drive this topic much. :(


Hope those answer you some of your questions, and loop you in roughly 
where our status is.


You can try Visual Studio version you like. I do not think MSVS supports 
our code. We have some special features build in historically, that are 
used only in the project. And we strongly use multilanguage 
architecture. So bringing the support to Visual Studio will be also not 
easy.


At Least on Eclipse it is very difficult to get the IDE partial working. 
I am thinking on extending one IDE, and I am undecided if Eclipse is the 
right choice, or maybe netbeans?... Well whatever not your issue. :)


It would be cool if we could establish Windows Visual Studio Suopport or 
any other IDE.


All the best

Peter


The MSVC we use

# 2008: https://www.microsoft.com/en-us/download/details.aspx?id=5023

# 2015: https://www.microsoft.com/de-de/download/details.aspx?id=48145


On 9/22/18 2:27 PM, George K wrote:

Hello,

I would like to contribute to Open Office. My main area of expertise is
computer graphics i.e. ui/ux. I have previous experience with DirectX and
OpenGL. My main focus this couple of years has been mobile development for
iOS and Android. Also i know design and prototyping.

I want to help make Open Office better and dusty off my C++ skills. I am
currently trying to build Open Office on the Windows platform and i 've
faced a problem as Microsoft Windows SDK for Windows 7 and .NET Framework
3.5. SP1 is not available to download. So i 'm stuck at the configure step.
Also is Visual Studio 9 necessary? Can Visual Studio 2017 be used, as i
can't find the former?

That said, i would like to start by making the build process easier(at
least on Windows). After many thoughts i 've come up with the following
build process:

-Install Visual Studio 2017(That means updating the project to work with
MSVC 2017 and provide all the other libraries and tools needed for Windows
through the VS installation. So all things Windows would be installed
through VS).
-Create a Windows script that will install all other prerequisites and
check out the repo(Provide a .bat file that will be run from the command
line which will install Java, Cygwin and it's modules, or install python
and through python scripts set up all the above. Then checkout the repo
from svn and be ready for build).
-Build Open Office as usual.

I know that all this may sound a lot because the whole project must be
updated to modern tools, but i am willing to try. But first things first, i
would be grateful if someone cleared my questions above, for the build
process, and after that get familiar with the code and discuss what would
work and what not, for making the build process better. And if the later
were to happen i believe that new users could be onboarded easier on the
project and start working on features.

Thanks in advance,
George



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

Re: Open Office Build Process

[Peter Kovacs]

Here a pointer to the Archives (search for all mails last year) to the 
MSVC topic:


https://lists.apache.org/list.html?dev@openoffice.apache.org:lte=12M:MSVC

I have found a Wiki resource for the build System (maybe it helps):

https://wiki.openoffice.org/wiki/Build_System_Analysis

https://wiki.openoffice.org/wiki/Build_Environment_Effort/New_Build_System_Requirements


I would use Windows 10. If you use a VM or not is more matter of taste.

All the best to the Migration effort!


On 9/23/18 4:12 PM, Damjan Jovanovic wrote:

Hi George

The build system is particularly difficult to change.

If you look through the mailing list archives, I documented some of my 
experiences with MSVC 14 in a 13 March 2018 email entitled "First 
steps in building with MSVC 14 / Visual Studio 2015". I didn't get 
far. A patch with some of my changes is attached.


Good luck and let us know if (or when ;) you need any help
Damjan

On Sun, Sep 23, 2018 at 2:14 PM George K > wrote:


Hello everyone,

I 'm currently trying to build Open Office on Windows. I 've setup
most of
the environment but I am having trouble finding the Windows 7.0
SDK, witch
contains MSVC 2008, as it is unavailable from Microsoft. Peter kindly
pointed me at an image of Windows Server 2008 Standard
.
Should I
setup a VM with that image, or download Windows 7? I 'm currently
trying to
build on a Windows 10 machine. Any help and directions would be
welcome.

That said, I would like to contribute to Open Office, by making
the build
process easier and migrating the project for Windows on MSVC 2017.
I have
thought of the following build process:

- Install Visual Studio 2017(All libraries and tools needed would be
provided through the installation)
- Install all other prerequisites using a Windows BATCH
file(Provide a .bat
file for automating installation of Java, Cygwin etc. and setting
up the
modules. Or, if complexity demands it, install python and do all
the above
through it. Optimally, checkout the repo from svn and be ready for
build).
- Build Open Office as usual.

That might be complicated, but I 'm willing to try. I 'm currently
trying
to familiarize my self with the code and I would be grateful if
someone
pointed me to the right direction. Let's keep an open discussion
of Open
Office's build process. Feel free to suggest new things or improve
my own.

Thanks in advance,
George


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

Re: [Discussion] Program for Sandro

[Peter Kovacs]

Dear Sandro,

Glad to read about your determination. :) Lets get you doing something.

You can send it directly to my address if you like. I personally would 
appreciate if we could store it somewhere more cloudy.


How about google drive or Dropbox. They offer free cloud space. And you 
can setup the space easy.



Yea it is really cool that we are a cloud Project. I think it is great 
that you are with us. Maybe we can make OpenOffice a bit more Cloudy. ;)


All the best

Peter

On 9/22/18 7:32 PM, sandro wrote:

Dear Peter,

It is always amazing to show my commitment and passion for this project, I feel 
that it is so good to build together that it certainly drives all of us to 
happiness.

I just have been looking for sending a work plan to you, as I told in my last 
message. I will ask an user for the wiki project.

Well, I have the wish and I feel that I am plenty able to go on with long term 
perspective with this volunteering. Because since the time schedule is flexible 
and since I can work from anywhere (school, park, home ...) there is probably 
no interference in the activity and I think that nothing will prevent me from 
collaborate. If a have to move to another city, or if I work more in another 
project, I can always collaborate; the only thing that would stop would be 
internet connection ( if I do not have it at home) but it is easy to find free 
wifi anywhere, there are libraries and other buildings that offer internet 
access for free and also a computer to access.

So I will always be here, I just was doing the work plan while handling other 
tasks (such as a university test to September, 24. It is a calculus test, 
macroeconomics test and a management test in the same week... rs). I plan to 
always collaborate with you, always hold hands.

Glad,
Sandro Suzart



De: Peter Kovacs 
Enviado: sábado, 22 de setembro de 2018 01:04
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Dear,

Have you asked a user Request? - Use a new thread for that please. -
Hope you are still with us, it would be sad if you already stop.

All the best

Peter

On 9/11/18 5:15 PM, sandro wrote:

Dear,


It is amazing, a really exciting journey that follows the pumps of heart beat 
is a glad and fantastic way, this certainly guides us through patterns of 
satisfaction.


Well, I have posted here a working schedule, also I will post a work plan of 
the WikiProject that I feel that will bring achievements to the page. I will 
upload it here because it helps and guides me for the work, and I can update it 
every 2-3 weeks.


Glad,

Sandro Suzart





De: Andrea Pescetti 
Enviado: segunda-feira, 10 de setembro de 2018 02:08
Para: dev@openoffice.apache.org
Assunto: Re: [Discussion] Program for Sandro

Peter kovacs wrote:

If you see something on our wiki-pages.
You can decide on yourself. There is no real command structure here.
If you need a user for editing the wiki, just write a request here.

Right. Sandro, if we haven't created a MWiki account for you yet, please
ask here. Otherwise, please give us your username so that we can (if
needed) extend permissions for you in order to be able to do some
configuration tasks.

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

OpenOffice Status Overview (Kanban like) Board

[Peter Kovacs]

Hi all,

I have a Point on Interest List on Cwiki (Confluence) [1] where I tried 
to collect all stuff that popped up. Goal was always to have some sort 
of Overview, and not forget stuff. I did not maintain it well, and it 
did not made things easier for me.


I have now moved now to trello [2], in hope it changes my view, and 
simplifies the additional management.


Currently I have mostly link to bugs, that popped up. I have some topics 
we discussed added.


I try to add more informations to the cards. I think it could help to 
add discussions, and Wiki Article and other resources in hope they add a 
better access to what is in our focus. My hope is that the board can be 
establish as advertisement board which can be used to give new comers 
some lead where to dive into.


The board is public, can be found by (google) searches. Currently I 
focus with the board on core "business". So only OpenOffice code related 
stuff is entered. I have not mentioned stuff from our Infrastructure 
topics. I am still trying experimenting and trying out. At the moment I 
prefer trello to Jira, due I do not want to copy a bug tracker. I just 
in need of an overview resource.


The list is still quite incomplete, even on actual activities. I just 
moved more or less the Issues that are piling up.


I invite any OpenOffice Volunteer to join the board on request. This 
should not be mandatory tool set. You can also just post something to 
the dev List. I will try to do the sync.


Hope this is a step in the right direction, from a management direction, 
preserving our DNA and be more accessible for everyone.



All the Best

Peter

[1] 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67633711


[2] https://trello.com/b/KxedeWKD/openoffice-program-status-board


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

[discussion] get rid of NOT_AN_OOO_ISSUE

[Peter Kovacs]

Hi all,

I would like to get rid of the Resolution "NOT_AN_OOO_ISSUE". This
leaves people angry and it is annoying to Copy paste or just rewrite
always the same stuff.

So I wonder if we could add a component user support, and allocate the
users list to it. With that we have a broader community looking at those
help requests, and handle them like every other Issue. Also maybe the
barrier between developers/testers and user support gets reduced a bit.

If it is a bug someone can simply change the component and we can check
for reproducibility. Instead of NOT_AN_ISSUE I would like to have FIXED
by workaround or something similar.


can you take some time and write your opinion? -would you like to help?


Thanks

All the Best

Peter









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

Re: [discussion] get rid of NOT_AN_OOO_ISSUE

[Peter Kovacs]

Thanks all for your feedback. I am not so sure the Idea carries. However
I would go in depth because maybe there is something we can think about
in the long run.

Markus wrote:

>
> I cannot belief that all (or the most) users are really angry /
> annoyed / disappointed. Can you proof that?

In a subset of cases we closed we had arguments. We also have improved
the closing comment as a reaction, which controls the outbreak much better.

One example where we had a cry out has been here:

https://bz.apache.org/ooo/show_bug.cgi?id=127855

I do also mention this scottish sceptic guy, who ranted exactly on one
of these cases. While I do not want to look to closely on his method I
believe he or in his surrounding someone has been affected by such a
case and he did berserk in an issue and after that on his blog.

But maybe these cases are not as often as the normal cases.

> The resolution was created to make it visible that the reported issue
> has its source not in OpenOffice. It has nothing to do with user
> support. Maybe it's often used for this but this was/is not intended.
True. I think all the cases where a reset of the Profile does resolve
the Issue may be wrong to close them as NOT_AN_OOO_ISSUE since the Issue
is a corrupted profile. And we do not know the root cause for the
corruption.

And we should consider in finding out if we can not harden openoffice
against this corruption. Most often we do not know if a Issue report has
been fixed with profile reset.

Jörg wrote:

> Bugzilla is not a support ticket system. If we were to start inviting users 
> (through an appropriate category in Bugzilla) to submit support requests 
> here, we would be creating additional work for ourselves.
The support request is there. It costs effort to move people into the
right channel i.e. Forums. And it is effort to move an issue that needed
to be first clarified and ended up on Forums to move it to the Channel
of Bugzilla.

I think we have to discuss ways to reduce this border.

I think we need to lower this to improve the recruitment rate. We are
doing pretty bad on this topic in general. I do think that if more users
are on Bugzilla, maybe they start looking into other stuff. Maybe the
Idea is stupid, and not right. But we need to open ways that people can
naturally extend their work that they are doing. Maybe my impression is
also not right, and we need to take care different steps to activate people.

For QA on 4.1.6 we had 7 Release Testers. That is thin. Maybe if people
handle support request they can be more easily activated to handle new
bugs, and then activated for release testing.






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

Re: Building AOO under Debian9

[Peter Kovacs]

have you tried

rm -r 
/home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS

as a solution?

On 19.01.19 07:24, Mechtilde wrote:
> Hello Jim,
>
> Am 17.01.19 um 15:44 schrieb Jim Jagielski:
>> Well, the error I was hitting is fixed, yeah.
>>
>> You may need to blow away main/instsetoo_native/unxlngx6.pro/* and rebuild
> Yes I did so.
>
> I do a  and then there were no unxlngx6.pro/* in
> main/instsetoo_native. But it doesn't work. I get the messabe:
>
> Error: ERROR: More than one new package in directory
> /home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS
> (
> /home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS/openoffice-de-base-4.2.0-1-linux-4.9-x86_64
> /home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS/openoffice-de-base-4.2.0-1-linux-4.9-x86_64.deb)
> in function: determine_new_packagename (packagepool)stopping
>
> I use r1851632 on my Debian 9.
>
>

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

Re: Version trunk in bugzilla

[Peter Kovacs]

Maybe a version trunk would help?

On 19.01.19 08:13, Mechtilde wrote:
> Hello,
>
> can we get the version "trunk2 in bugzilla to track the issues which
> comms there and are not in the 420-dev branch.
>
> Kind regards
>

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

Re: Forrum help support

[Peter Kovacs]

Hi Barb,

I am sorry you feel hurt.

Please, can you confirm if the link that has been posted is the one you
are upset about.

https://forum.openoffice.org/en/forum/viewtopic.php?f=15=96638

What do you expect now to happen?

All the Best

Peter Kovacs

Project Managment Commitee Member


On 18.01.19 19:05, Barb Gruhl wrote:
> Hi, Is this the kind of treatment you allow from your support members
> on the help forum? This is not be helpful it is being a bully. I have
> included a screen shot of the response I am talking about.
>
> Barb Gruhl
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon>
>   Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Development beginner

[Peter Kovacs]

Hi Dustin,

OpenOffice is an old project. The code has been touched by many people.
OpenOffice is also a multi language project.

Parts of it are written in c, c++ or a mix of both. We got java and
python code. The build  environment is written in perl and bash. We use
in parts dmake, gmake and Ant. We have the Idea to port to SCON.

We have a own COM-Interface written in c,c++ and assembler. It connects
all language pieces.


There is no IDE that can handle this colorful approach. The best IDE
support is offered by eclipse and that is incomplete. Some use Visual
Studio.

Welcome to OpenOffice. :)

Best way to start with OpenOffice is to learn do your own builds and be
persistent. There is no shame in asking questions. Even the experienced
devs here have to ask around.

You find a general guide here:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

specific guide:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step

How to setup eclipse:
https://wiki.openoffice.org/wiki/OpenOffice_and_Eclipse


I try to organize tasks on Jira:
https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=OPENOFFICE=301

you can of course help to maintain Bugzilla. We get frequent reports,
and have to look at old ones if they still are accurate.
https://bz.apache.org/ooo/

Also you can try and write hints on bugs can be solved. Maybe a hint
where to look can already help that a solution can be found.

Or help update the documentation on Programming. We have some stuff
here: https://wiki.openoffice.org/wiki/Category:Development


Hope this gives you enough hints and connects to choose how you
contribute to the project. All actions even learning to build is very
usefull for us.

All the best

Peter


On 14.01.19 02:46, Dustin Alldredge wrote:
> Hi guys, I recently graduated with my bachelor's degree and would like to
> get into development and thought that some experience with open office
> would be a great start. I've never been a part of any development teams
> outside of my educational experience so any tips or pointers would be very
> welcome. I have experience in several languages but am not sure what tools
> everyone uses here. Thank you and I look forward to working with you all!!
>


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

Re: what do i need to do to update our static websides

[Peter Kovacs]

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 wrote:
> 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 need to do it yourself manually.
>
> Long time ago I've explained the instructions here:
> https://openoffice.apache.org/docs/edit-cms.html
>
> HTH
>
> Marcus
>
>
> -
> 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: what do i need to do to update our static websides

[Peter Kovacs]

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
>>
>> 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.
>>
> Peter;
> I the path to check that page is
> http://ooo-site.staging.apache.org/security/bulletin.html
>
> 
>

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

Re: what do i need to do to update our static websides

[Peter Kovacs]

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 [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 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 need to do it yourself manually.
>>
>> Long time ago I've explained the instructions here:
>> https://openoffice.apache.org/docs/edit-cms.html
>
> Here is a detailed tutorial for the CMS that I wrote a year ago for a member 
> of the German community.
> (The tutorial  is ONLY in German.)
>
> http://www.calc-info.de/files/Apache-CMS-Anleitung.pdf
>
>
>
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Re: what do i need to do to update our static websides

[Peter Kovacs]

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 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
>> visible.
>>
>> Are there additional steps needed?
> imho:
> There is a publish link in the Cms, you have to click it.
>
> I see your editing:
> https://ci.apache.org/builders/ooo-site-site-staging/builds/1874
>
> but I don't know how you can access the publish link from there, maybe the 
> one at the top of this page works:
> https://cms.apache.org/ooo-site/wc/browse/joesch-t56vtS/trunk/content/de/
>
> (Ok, not with "joesch", it's my account ;-))
>
>
>
> gretings,
> Jörg
>
>
>
> -
> 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: Latest test builds

[Peter Kovacs]

Hi Rory,

do we have a Bug for this?


All the Best

Peter

On 20.01.19 17:45, Rory O'Farrell wrote:
> On Sun, 20 Jan 2019 10:28:53 -0500
> 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 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 off a Linux 32bit
>> build.
>>
>> Find them here:
>>
>>  http://home.apache.org/~jim/AOO-builds/4.2.0-dev-r1851640/
>>
>> Cheers!
>>
> I have seen a report that 4.1.6 is failing to open .docx files.  4.2.0 
> (r1851640) and Jim's earlier version are also failing with .docx files.  The 
> latest 4.2.0 will crash with a small .docx (~20KB) and offer to recover it; 
> it will then display it.  With a larger .docx (365 KB) it will crash, and be 
> unable to recover or display that file. It also does not identify the file 
> with which it has crashed or is trying to recover. I have not checked these 
> behaviours against 4.1.6
>
> This does not present any immediate problem for me, as I work only in .odt 
> format, but after repairing a corrupt .docx file on forum for a user, I was 
> unable to open it for testing, although the repaired document.xml passed a 
> "Well-formed XML" check.
>
>

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

Re: Building AOO under Debian9

[Peter Kovacs]

Maybe it is a good point to ask infra to switch to git?

On 15.01.19 08:13, Mechtilde wrote:
> the same revision buids under Debian 8 with epm version 3.7 which is
> shipped in the source code.
>
> but this doesn't work with Debian 9 and CentOS 7.
>
> Now I run it with system epm 4.2 on Debian 9. In some hours I will send
> the result.
>
> Mechtilde
>
> Am 15.01.19 um 02:12 schrieb Damjan Jovanovic:
>> I can't see much in that output, and you're not going to like my suggestion.
>>
>> Clone AOO from a Git repository, find an old version that could build debs,
>> and then do a regression test with "git bisect" to find the first commit
>> that broke building debs, so we can see where and how it went wrong and
>> proceed from there.
>>
>> We're probably going to need "git bisect" a lot, for the 4.2.0 release...
>>
>> On Tue, Jan 15, 2019 at 12:04 AM Jim Jagielski  wrote:
>>
>>> 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.
>>
>> Sure, patch the whole 42x branch.
> As I described in the other thread it breaks at building with epm.
>
> It says I had to rebuild instsetoo_native.
 I get the same problem at the 42x branch.

 I did it with a clean build.


 "... removing directory
 /home/mechtilde/aoo42x/main/instsetoo_native/
>>> unxlngx6.pro/Apache_OpenOffice/deb/stripped/en-US
 ...
 Error: ERROR:
 "LD_PRELOAD=/home/mechtilde/aoo42x/main/solver/420/
>>> unxlngx6.pro/bin/getuid.so
 /home/mechtilde/aoo42x/main/solver/420/unxlngx6.pro/bin/epm -f deb
 openoffice-brand-calc
 /home/mechtilde/aoo42x/main/instsetoo_native/
>>> unxlngx6.pro/Apache_OpenOffice/deb/listfile/en-US/epm_gid_Module_Brand_Prg_Calc.lst
 --output-dir DEBS -v2  2>&1 |"!
 in function: call_epm

> Regards
>
 --
 Mechtilde Stehmann
 ## Apache OpenOffice
 ## Freie Office Suite für Linux, MacOSX, Windows
 ## Debian Developer
 ## PGP encryption welcome
 ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

>>>
>>> -
>>> 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

what do i need to do to update our static websides

[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?


Thanks

Peter


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

Re: AOO 4.2.x development branch created

[Peter Kovacs]

The Question is:

Do we want to take action here or not?


On 17.01.19 21:19, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 17.01.19 um 20:42 schrieb Marcus:
>> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>>> Two of my commits were immediately picked by LO. [1] [2]
>>>
>>> Always nice to see, that down streaming still works for the fork... :-D
>> sure, better then to draw this on their own.
>>
>> Again with a note who has tested and reviewed it  - which is totally
>> fine - but no hint where it comes from and who is the author. They
>> still don't want to tell where they get the code from.
> Not exactly, Pilot_Pirx is me... ;-)
>
> But now it looks like I would have committed it directly to LO, while
> they just monitor aoo/trunk and take what they can use. [1]
>
> Regards,
>
>    Matthias
>
> [1]
> https://github.com/LibreOffice/core/commit/1170f10906a9bca78782df6ab1b6a4e20cf0435a
>
>> Is this redicioulous or just sad? I don't know. :-(
>>
>> Marcus
>>
>>
>>
>>> [1]
>>> https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073
>>>
>>> [2]
>>> https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff
>>>
>>>
>>> Am 14.01.19 um 16:46 schrieb Jim Jagielski:
 At this stage, I think just back porting (svn merge) to the AOO42X
 branch is fine.
 As we get close to a release, we'll need to either have an RM
 approve it
 or so something like creating a STATUS file, with a list of proposed
 backports
 and requiring at least 3 +1s to backport (ie: RTC)

> 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
>>> issue I'm thinking...
> How is the process to get commits merged from trunk to AOO42X?
>
> I adjusted some pointers for Windows and Linux:
>
> https://svn.apache.org/viewvc?view=revision=1851110
> https://svn.apache.org/viewvc?view=revision=185
> https://svn.apache.org/viewvc?view=revision=1851214
>
> Additionally I updated some pointers for OS/2. I know that Bitwise is
> already working on a port of 4.2.0, so they would be useful.
>
> Since it took me several attempts it would be easier, if I would
> commit
> them directly. ..
>
> Regards
>
>     Matthias
>
>> Yeppers... for sure it's the udk versioning, which is more a Linux
>> thing than a macOS (or Windows) thing.
>>
>> Will look into either hacking around it or something else. I
>> thought I had fixed it. Obviously not :(
>>
>> -
>> 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: open office writer 4.1.2

[Peter Kovacs]

please update OpenOffice to 4.1.6

Help you get on https://forum.openoffice.org

all the best

Peter

On 19.01.19 16:46, b vonk wrote:
> I can not group two or more items together. Not by selecting the items with 
> the shift button, or by selecting by the slection arrow.
>
> Verzonden vanuit Mail voor Windows 10
>
>

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

Fwd: open office writer 4.1.2

[Peter Kovacs]

sorry, forgot your mail.

All the Best Peter



 Forwarded Message 
Subject:Re: open office writer 4.1.2
Date:   Sat, 19 Jan 2019 23:21:31 +0100
From:   Peter Kovacs 
Reply-To:   dev@openoffice.apache.org
Organization:   Open Office Project
To: dev@openoffice.apache.org



please update OpenOffice to 4.1.6

Help you get on https://forum.openoffice.org

all the best

Peter

On 19.01.19 16:46, b vonk wrote:
> I can not group two or more items together. Not by selecting the items with 
> the shift button, or by selecting by the slection arrow.
>
> Verzonden vanuit Mail voor Windows 10
>
>

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