wip-libreoffice

wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

I've pushed a branch wip-libreoffice which has the start of a package for 
libreoffice and dependencies.

I am running out of resources to complete it on my own.  It takes 10 hours to 
(fail to) build on my machine, before I run out of disk space (it needs at least
 12GB).

It is at the stage however where it "builds" but some internal tests fail for reasons
I've not yet determined.    Any help would be greatly received.


Can this be scheduled to build on hydra?


J'


-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

On Thu, Nov 13, 2014 at 07:01:41PM +0100, John Darrington wrote:
> I've pushed a branch wip-libreoffice which has the start of a package for 
> libreoffice and dependencies.

Amazing! I thought you needed java for this?

Actually, you could already propose patches for the dependencies that we
could add to master.

> I am running out of resources to complete it on my own.  It takes 10 hours to 
> (fail to) build on my machine, before I run out of disk space (it needs at least
>  12GB).
> It is at the stage however where it "builds" but some internal tests fail for reasons
> I've not yet determined.    Any help would be greatly received.
> Can this be scheduled to build on hydra?

Yes; but I would suggest to disable mips and i686 and keep only the x86_64
architecture for the test.

Andreas

Re: wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]

On Fri, Nov 14, 2014 at 07:44:31PM +0100, Andreas Enge wrote:
     On Thu, Nov 13, 2014 at 07:01:41PM +0100, John Darrington wrote:
     > I've pushed a branch wip-libreoffice which has the start of a package for 
     > libreoffice and dependencies.
     
     Amazing! I thought you needed java for this?

I think it is optional.  Note the --without-java flag.
     
     Actually, you could already propose patches for the dependencies that we
     could add to master.

It might be safe to put some of them in master, but libreoffice being libreoffice
requires some of its dependencies to be configured in a very specific way.  I'm
not yet sure that all of them are correctly configured.
     
     > I am running out of resources to complete it on my own.  It takes 10 hours to 
     > (fail to) build on my machine, before I run out of disk space (it needs at least
     >  12GB).
     > It is at the stage however where it "builds" but some internal tests fail for reasons
     > I've not yet determined.    Any help would be greatly received.
     > Can this be scheduled to build on hydra?
     
     Yes; but I would suggest to disable mips and i686 and keep only the x86_64
     architecture for the test.

That would probably be a sensible approach, at least to begin with.
     

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

Hi John,

I enabled only x86_64 for libreoffice (and all systems for its added
dependencies) and created a jobset on hydra:
   http://hydra.gnu.org/jobset/gnu/wip-libreoffice
It should start building soon.

Notice that graphite2 is already available in the distribution, so there is
no need to add silgraphite.

On Fri, Nov 14, 2014 at 08:17:38PM +0100, John Darrington wrote:
> It might be safe to put some of them in master, but libreoffice being libreoffice
> requires some of its dependencies to be configured in a very specific way.  I'm
> not yet sure that all of them are correctly configured.

Well, you can already add a patch for a dependency that builds, and modify it
later if it needs tweaking.

Andreas

Re: wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

Thanks Andraes,

Note that LO has some *very* specific dependencies.  In some cases, they have
even gone so far as to fork projects.  So it may be that we'll need to maintain
several versions of a package to satisfy everthing.

Anyway, I will keep an eye on the build and see if we can make it build to a succesfull
conclusion.  Anyone else interested can also chip in.

J'

On Tue, Nov 18, 2014 at 11:44:27PM +0100, Andreas Enge wrote:
     Hi John,
     
     I enabled only x86_64 for libreoffice (and all systems for its added
     dependencies) and created a jobset on hydra:
        http://hydra.gnu.org/jobset/gnu/wip-libreoffice
     It should start building soon.
     
     Notice that graphite2 is already available in the distribution, so there is
     no need to add silgraphite.
     
     On Fri, Nov 14, 2014 at 08:17:38PM +0100, John Darrington wrote:
     > It might be safe to put some of them in master, but libreoffice being libreoffice
     > requires some of its dependencies to be configured in a very specific way.  I'm
     > not yet sure that all of them are correctly configured.
     
     Well, you can already add a patch for a dependency that builds, and modify it
     later if it needs tweaking.
     
     Andreas

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

There is an evaluation error:

In gnu/packages/libreoffice.scm:
 645: 1 [arguments]
In unknown file:
   ?: 0 [scm-error misc-error #f "~A" ("Unknown architecture for nss") #f]

ERROR: In procedure scm-error:
ERROR: Unknown architecture for nss

Probably one needs to enable only s86_64-linux as a supported architecture
for nss?

Andreas

Re: wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Thu, Nov 20, 2014 at 11:56:08PM +0100, Andreas Enge wrote:
     There is an evaluation error:
     
     In gnu/packages/libreoffice.scm:
      645: 1 [arguments]
     In unknown file:
        ?: 0 [scm-error misc-error #f "~A" ("Unknown architecture for nss") #f]
     
     ERROR: In procedure scm-error:
     ERROR: Unknown architecture for nss
     
     Probably one needs to enable only s86_64-linux as a supported architecture
     for nss?

s86_64-linux ??  "s" ?  Did you mean to type "x" ?


I thought you said a few days back that the evaluations would only run on x86_64
at least to start with.  

Perhaps we should expand that error message to show what achitecture it thinks
it is trying to build.

BTW, where do you see these results?  According to hydra.gnu.org, the wip-libreoffice
branch has never been evaluated.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

On Fri, Nov 21, 2014 at 09:43:56AM +0100, John Darrington wrote:
> s86_64-linux ??  "s" ?  Did you mean to type "x" ?

Yes.

> I thought you said a few days back that the evaluations would only run on x86_64
> at least to start with.  

Well, I added a line to libreoffice to make it build only on x86_64, at the
package level, not at the hydra level.

> BTW, where do you see these results?  According to hydra.gnu.org, the wip-libreoffice
> branch has never been evaluated.

You need to click on the branch and then on "Evaluation errors". This shows
an error message from your nss package; I do not quite understand why this
already happens on hydra, and not when offloading the build of the nss package.
You could try to replace this test by a supported-systems stance already.

Andreas

Re: wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]

On Fri, Nov 21, 2014 at 10:54:28AM +0100, Andreas Enge wrote:
     On Fri, Nov 21, 2014 at 09:43:56AM +0100, John Darrington wrote:
     
     > I thought you said a few days back that the evaluations would only run on x86_64
     > at least to start with.  
     
     Well, I added a line to libreoffice to make it build only on x86_64, at the
     package level, not at the hydra level.
     
     > BTW, where do you see these results?  According to hydra.gnu.org, the wip-libreoffice
     > branch has never been evaluated.
     
     You need to click on the branch and then on "Evaluation errors". This shows
     an error message from your nss package; 

BUG!!  This only works if Javascript is enabled.  Please fix it so that it works without Javascript.

     I do not quite understand why this
     already happens on hydra, and not when offloading the build of the nss package.

Does Ludo know?

     You could try to replace this test by a supported-systems stance already.
     
I don't know what this sentance means.


J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

On Fri, Nov 21, 2014 at 12:31:02PM +0100, John Darrington wrote:
> I don't know what this sentance means.

Do something similar as my last patch on wip-libreoffice:
Add a line
   (supported-systems `("x86_64-linux"))
to the nss package.

No idea if this would be enough.

Personally, I still prefer to work bottom-up by adding dependencies first
(actually, I usually do a depth-first traversal of the dependency graph).

Andreas

Re: wip-libreoffice

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Fri, Nov 21, 2014 at 01:05:58PM +0100, Andreas Enge wrote:
     On Fri, Nov 21, 2014 at 12:31:02PM +0100, John Darrington wrote:
     > I don't know what this sentance means.
     
     Do something similar as my last patch on wip-libreoffice:
     Add a line
        (supported-systems `("x86_64-linux"))
     to the nss package.
     
     No idea if this would be enough.
     
     Personally, I still prefer to work bottom-up by adding dependencies first
     (actually, I usually do a depth-first traversal of the dependency graph).
     

I will do what you suggested.  But like you say, it would seem sensible to me, if this entire branch is built
only for x86_64, at least for the time being.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-libreoffice

[Andreas Enge]

On Fri, Nov 21, 2014 at 06:22:23PM +0100, John Darrington wrote:
> I will do what you suggested.  But like you say, it would seem sensible to me, if this entire branch is built
> only for x86_64, at least for the time being.

I do not see how to do this at the gui level of our hydra install; maybe
it is not possible. Ludovic?

What you could do maybe is create a dummy package that has supported-system
set to x86_64-linux only, and have all your other packages inherit from it.

Andreas

Re: wip-libreoffice

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> On Fri, Nov 21, 2014 at 06:22:23PM +0100, John Darrington wrote:
>> I will do what you suggested.  But like you say, it would seem sensible to me, if this entire branch is built
>> only for x86_64, at least for the time being.
>
> I do not see how to do this at the gui level of our hydra install; maybe
> it is not possible. Ludovic?

Right, it’s not possible.  build-aux/hydra/gnu-system.scm would need to
be updated to allow that (similar to the ‘subset’ parameter.)

> What you could do maybe is create a dummy package that has supported-system
> set to x86_64-linux only, and have all your other packages inherit from it.

Yeah; actually just put ‘supported-systems’ on LibreOffice itself, since
the other packages may not be that resource hungry.

Thanks,
Ludo’.