Re: buildbots -- Linux and MacOSX

[Jürgen Schmidt]

On 11/15/13 6:54 PM, Andrew Rist wrote:
> I wanted to give an update on the buildbots, as this is a question that
> keeps coming up.

first of all thanks for the summarized update

> 
>  * We've received assurances that the Mac buildbot is coming. Long
>story short, the current mac hardware is a bit long in the tooth and
>we would kill everything on it if we added our builds to the current
>machine.  We are waiting for real hardware in the form of a Mac Pro
>which will enable us to have multiple virtualized mac bots, giving
>us our own environment that can be set up for AOO.  The machine
>should be ordered by the end of the year - bot should come up early
>next year - ish...

perfect and with the ongoing 64 bit work it will be much easier to setup
a working env on a modern system (kudos for Herbert).

>  * We are also waiting on a CentOS bot to create our standard Linux
>build.  This has been requested and is in the works, and Jan has
>agreed to bring this up in discussions with infra.  I am hoping we
>can have this for the 4.1 release timeframe.

sounds good and I hope we can get it. I believe we can focus on a 64 bit
system first.

>  * FreeBSD bot - we have a new freebsd bot and it is slowly moving
>toward building without errors.  If anyone has suggestions for
>fixing issues on there, please post to dev and we'll move that
>forward.  We are currently stuck on Hunspell -

FreeBSD is a port but we don't release binaries. It's fine to me to have
a FreeBSD port but for me it don't have a high priority. If we have
hardware or other physical limitation we should first drop such
unreleased platforms. And please don't get me wrong we do everything to
support this platform but I personally don't see the demand for a build
bot at the moment

>   
> http://ci.apache.org/builders/openoffice-fbsd-nightly/builds/91/steps/configure/logs/stdio
> 
>and
>   
> http://ci.apache.org/projects/openoffice/buildlogs/fbsdn/log/unxfbsdx.pro.build.html
> 
>  * The hung process issue with the windows buildbots seems to solved
>now, and has not been a problem lately.
>  * Currently the Windows bots are failing - but this seems to an issue
>of svn getting out of sync, I'm cleaning up the bot and restarting
>the machine after some updates - I expect this to clean up the
>current issues.  (
>  * Snapshots - both linux and windoze are currently having issues in
>terms of the size of files that the build creates.  The standard
>buildbot directory upload routine zips the directory, uploads it,
>and unzips at the destination.  Our directory of install bits has
>gotten too large and we are running into an exception on this
>step.   (On long term fix is to create our own custom directory
>upload code for build bot - but that is another discussion...)  The
>short term solution is to split the snapshot build into two builds   
> (possible in a single flow) and build half the languages in each
>build - this should get us around the space issue.

mmh, I always wondering a little bit about this physical limitations but
that is a different story.

Can you tell us a little bit more about the requirements for the custom
directory and upload code.


For a short term solution I would suggest to prepare a package lst file
and pack only en-US + the 5 most often downloaded languages and for all
other languages we build language packs only. What do you think?

Juergen

> 
> That's all for now
> A.
> 
> 
> 
> On 11/13/2013 10:01 AM, Kay Schenk wrote:
>> On Tue, Nov 12, 2013 at 6:33 PM, Glenn Harvey Liwanag <
>> glennharveyliwa...@gmail.com> wrote:
>>
>>> I can try building the thing on my Mac OS X if that's what you're
>>> looking
>>> for. It's my only computer right now and I use it for school so I
>>> have to
>>> know first the average build time and the instructions to get the whole
>>> thing done without academics interfering with the work.
>>>
>> Thanks for this offer! Resources used for building are dependent on your
>> system, but typically it would take about 2 hours for a full build.
>>
>> Information on how to obtain the source and a link to the Building Guide
>> can be found on the project source page:
>>
>>   http://openoffice.apache.org/source.html
>>
>> Please let us know how this goes for you.
>>
>>
>>> On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk 
>>> wrote:
>>>
 Regarding Jürgen's comments  on a recent thread --

 http://markmail.org/message/v5zli2np67qv5ryz

 Since  CentOS 5 is our reference distribution for delivered Linux
>>> binaries
 (I did not know this!) -- and I am assuming this distro might remain as
>>> the
 reference going forward, does it make sense to try to move forward
 to set
 this up as a buildbot. I know wokr had already started on this. Can
>>> someone
 give us an update?

 https://issues.apache.org/jira/browse/INFRA-6217

 I don't know CentOS, but having about 1

Re: OSBA Office Interoperability Workshop last week

[Pedro Giffuni]

Hi Juergen;

I am just catching up with some old mail but thank you for the 
interesting report.


Just as an external observer and reminding that IANAL, the LO/TDF 
doesn't seem to be complying with the Apache License section 4 
subsection (d) and is misinterpreting on purpose subsection (b).


The so-called "rebasing" was obfuscated on purpose, probably with some 
level of paranoia, to avoid making clear which code is under an Apache 
License and which is not. It was not surprising to find that at least 
one CWS, not included in AOO, was "relicensed" and mixed with other 
arbitrary license swapping.


Using public funding for opensource projects is great but it involves 
all the parties working responsibly. I just think that given the 
situation of uncertainty of the results and the general lack of 
collaboration from one group it just doesn't make sense for both 
projects to work together.


It's not all bad though: While LibreOffice seems to be a place to run 
experiments, AOO is setting the new standards that get widely adopted.


Just my opinion though ... I am always glad to be proved wrong.

Pedro.

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

Re: [WWW]Website not building?

[Ricardo Berlasso]

2013/11/17 Ricardo Berlasso 

> Yesterday I did some changes on a page on the ES website (Revision
> 1542617). The commit was "successful" but the changes never arrived to the
> staging site. Clicking on [Follow Staging Build] gave me an "error 503
> (Service Temporarily Unavailable)".
>
> On the service status page(1) I can see that "vmbuild.apache.org" is on
> critical state. Is that the reason?
>
> (1) http://monitoring.apache.org/status/
>
> Regards,
> Ricardo
>


It seems that everything is working now. In fact, it seems that someone
published the site: the changes on the page are now "live".

Regards,
Ricardo

[WWW]Website not building?

[Ricardo Berlasso]

Yesterday I did some changes on a page on the ES website (Revision
1542617). The commit was "successful" but the changes never arrived to the
staging site. Clicking on [Follow Staging Build] gave me an "error 503
(Service Temporarily Unavailable)".

On the service status page(1) I can see that "vmbuild.apache.org" is on
critical state. Is that the reason?

(1) http://monitoring.apache.org/status/

Regards,
Ricardo

Business partnership - Openoffice and SafeRev

[Aviva]

 

 

 

Hello,

 

I represent SafeRev, a non-search monetization component which helps
maximize revenues for leading Download applications Worldwide (e.g.:
Babylon, Softonic, Iminent, InstallCore and others).

 

I'm sure we can help you monetize your free downloads on this website, and
increase your revenues.

Can we have a call this week to discuss this in more details?

 

Looking forward to hearing from you.

 

Best regards,

 

Aviva Shapira

Senior Business Development 

 


 


T: +972-3-6390013  

  www.saferev.com   

 

 



 

 

 

Nepali or Hindi or Sanskrit using Devanagari Script

[taruntapasi]

Sir those languages must be more developed for it.



Sent from Windows Mail