Website development questions

Website development questions

[Luis Felipe López Acevedo]

Hi,

I cloned the website to try a fix for bug #22115, and wanted to ask 
first what process do you follow to try out the whole website locally? 
When I build and serve the website with Haunt, I face the following 
problems:

1. Pages don't load static files because they are looking for the 
"static" directory in "/software/guix/static". Do I need to set some 
variable first?
2. The Packages and Packages Issues pages, which are defined in (www 
packages) are commented out. How do you deal with those in development?

I'm using Guix 20161113.19 on Debian 8.6.

Thanks,


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

Hello!

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> I cloned the website to try a fix for bug #22115, and wanted to ask
> first what process do you follow to try out the whole website locally?
> When I build and serve the website with Haunt, I face the following
> problems:
>
> 1. Pages don't load static files because they are looking for the
> "static" directory in "/software/guix/static". Do I need to set some
> variable first?

To test locally, you need to do:

  $ GUIX_WEB_SITE_LOCAL=yes haunt build
  $ haunt serve

There should be no broken links, except for links to the manual or other
parts of gnu.org.

I suppose this should go to README…

> 2. The Packages and Packages Issues pages, which are defined in (www
> packages) are commented out. How do you deal with those in
> development?

That’s on purpose, so that people don’t need to have Guix installed to
hack on the web site.

We build these pages separately using the ‘export-web-page’ procedure.

HTH!

Ludo’.

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-15 04:57, ludo@gnu.org wrote:
> Hello!
> 
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> I cloned the website to try a fix for bug #22115, and wanted to ask
>> first what process do you follow to try out the whole website locally?
>> When I build and serve the website with Haunt, I face the following
>> problems:
>> 
>> 1. Pages don't load static files because they are looking for the
>> "static" directory in "/software/guix/static". Do I need to set some
>> variable first?
> 
> To test locally, you need to do:
> 
>   $ GUIX_WEB_SITE_LOCAL=yes haunt build
>   $ haunt serve
> 
> There should be no broken links, except for links to the manual or 
> other
> parts of gnu.org.
> 
> I suppose this should go to README…
> 
>> 2. The Packages and Packages Issues pages, which are defined in (www
>> packages) are commented out. How do you deal with those in
>> development?
> 
> That’s on purpose, so that people don’t need to have Guix installed to
> hack on the web site.
> 
> We build these pages separately using the ‘export-web-page’ procedure.
> 
> HTH!
> 
> Ludo’.

Yes, thanks. I'll put this information in the README.


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-15 04:57, ludo@gnu.org wrote:
> Hello!
> 
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> I cloned the website to try a fix for bug #22115, and wanted to ask
>> first what process do you follow to try out the whole website locally?
>> When I build and serve the website with Haunt, I face the following
>> problems:
>> 
>> 1. Pages don't load static files because they are looking for the
>> "static" directory in "/software/guix/static". Do I need to set some
>> variable first?
> 
> To test locally, you need to do:
> 
>   $ GUIX_WEB_SITE_LOCAL=yes haunt build
>   $ haunt serve
> 
> There should be no broken links, except for links to the manual or 
> other
> parts of gnu.org.
> 
> I suppose this should go to README…
> 
>> 2. The Packages and Packages Issues pages, which are defined in (www
>> packages) are commented out. How do you deal with those in
>> development?
> 
> That’s on purpose, so that people don’t need to have Guix installed to
> hack on the web site.
> 
> We build these pages separately using the ‘export-web-page’ procedure.

Ludo, I'm not sure how to do this part. Do I just import (www) and (www 
packages) in a REPL, and call `export-web-page` for each page (packages 
index and issues)? You don't have to modify `www.scm` at all (uncomment 
elements in the %web-pages list, for example)?

Also, trying just that, when I try importing (www packages), (guix ui) 
is not found in my system:

     scheme@(guile-user)> (use-modules (www packages))
     ;;; compiling 
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm
     ;;; WARNING: compilation of 
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
     ;;; ERROR: no code for module (guix ui)
     While compiling expression:
     ERROR: no code for module (guix ui)

I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and guix 
is version 20161113.19. Where are Guix modules?

Thanks,


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-20 15:17, Luis Felipe López Acevedo wrote:
> On 2016-11-15 04:57, ludo@gnu.org wrote:
>> Hello!
>> 
>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>> 
>>> I cloned the website to try a fix for bug #22115, and wanted to ask
>>> first what process do you follow to try out the whole website 
>>> locally?
>>> When I build and serve the website with Haunt, I face the following
>>> problems:
>>> 
>>> 1. Pages don't load static files because they are looking for the
>>> "static" directory in "/software/guix/static". Do I need to set some
>>> variable first?
>> 
>> To test locally, you need to do:
>> 
>>   $ GUIX_WEB_SITE_LOCAL=yes haunt build
>>   $ haunt serve
>> 
>> There should be no broken links, except for links to the manual or 
>> other
>> parts of gnu.org.
>> 
>> I suppose this should go to README…
>> 
>>> 2. The Packages and Packages Issues pages, which are defined in (www
>>> packages) are commented out. How do you deal with those in
>>> development?
>> 
>> That’s on purpose, so that people don’t need to have Guix installed to
>> hack on the web site.
>> 
>> We build these pages separately using the ‘export-web-page’ procedure.
> 
> Ludo, I'm not sure how to do this part. Do I just import (www) and
> (www packages) in a REPL, and call `export-web-page` for each page
> (packages index and issues)? You don't have to modify `www.scm` at all
> (uncomment elements in the %web-pages list, for example)?
> 
> Also, trying just that, when I try importing (www packages), (guix ui)
> is not found in my system:
> 
>     scheme@(guile-user)> (use-modules (www packages))
>     ;;; compiling 
> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm
>     ;;; WARNING: compilation of
> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
>     ;;; ERROR: no code for module (guix ui)
>     While compiling expression:
>     ERROR: no code for module (guix ui)
> 
> I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and
> guix is version 20161113.19. Where are Guix modules?
> 
> Thanks,

In the meantime, I cloned guix repo, and added the source directory to 
Guile's load path. The error above is gone, but now I get this one:

     scheme@(guile-user)> (use-modules (www) (www packages))
     ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
     ;;;       or pass the --no-auto-compile argument to disable.
     ;;; compiling 
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm
     ;;; compiling /home/anonimo/Documentos/guix/guix/ui.scm
     ;;; compiling /home/anonimo/Documentos/guix/guix/utils.scm
     ;;; WARNING: compilation of 
/home/anonimo/Documentos/guix/guix/utils.scm failed:
     ;;; ERROR: no code for module (guix config)
     ;;; WARNING: compilation of 
/home/anonimo/Documentos/guix/guix/ui.scm failed:
     ;;; ERROR: no code for module (guix config)
     ;;; compiling /home/anonimo/Documentos/guix/guix/store.scm
     ;;; WARNING: compilation of 
/home/anonimo/Documentos/guix/guix/store.scm failed:
     ;;; ERROR: no code for module (guix config)
     ;;; WARNING: compilation of 
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
     ;;; ERROR: no code for module (guix config)
     While compiling expression:
     ERROR: no binding `guix-warning-port' in module (guix ui)

And still curious about how to import guix modules without using a 
checkout :)


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

¡Hola!

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> On 2016-11-20 15:17, Luis Felipe López Acevedo wrote:
>> On 2016-11-15 04:57, ludo@gnu.org wrote:
>>> Hello!
>>>
>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>>
>>>> I cloned the website to try a fix for bug #22115, and wanted to ask
>>>> first what process do you follow to try out the whole website
>>>> locally?
>>>> When I build and serve the website with Haunt, I face the following
>>>> problems:
>>>>
>>>> 1. Pages don't load static files because they are looking for the
>>>> "static" directory in "/software/guix/static". Do I need to set some
>>>> variable first?
>>>
>>> To test locally, you need to do:
>>>
>>>   $ GUIX_WEB_SITE_LOCAL=yes haunt build
>>>   $ haunt serve
>>>
>>> There should be no broken links, except for links to the manual or
>>> other
>>> parts of gnu.org.
>>>
>>> I suppose this should go to README…
>>>
>>>> 2. The Packages and Packages Issues pages, which are defined in (www
>>>> packages) are commented out. How do you deal with those in
>>>> development?
>>>
>>> That’s on purpose, so that people don’t need to have Guix installed to
>>> hack on the web site.
>>>
>>> We build these pages separately using the ‘export-web-page’ procedure.
>>
>> Ludo, I'm not sure how to do this part. Do I just import (www) and
>> (www packages) in a REPL, and call `export-web-page` for each page
>> (packages index and issues)? You don't have to modify `www.scm` at all
>> (uncomment elements in the %web-pages list, for example)?
>>
>> Also, trying just that, when I try importing (www packages), (guix ui)
>> is not found in my system:
>>
>>     scheme@(guile-user)> (use-modules (www packages))
>>     ;;; compiling
>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm
>>     ;;; WARNING: compilation of
>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
>>     ;;; ERROR: no code for module (guix ui)
>>     While compiling expression:
>>     ERROR: no code for module (guix ui)
>>
>> I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and
>> guix is version 20161113.19. Where are Guix modules?
>>
>> Thanks,
>
> In the meantime, I cloned guix repo, and added the source directory to
> Guile's load path. The error above is gone, but now I get this one:
>
>     scheme@(guile-user)> (use-modules (www) (www packages))
>     ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
>     ;;;       or pass the --no-auto-compile argument to disable.
>     ;;; compiling
> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm
>     ;;; compiling /home/anonimo/Documentos/guix/guix/ui.scm
>     ;;; compiling /home/anonimo/Documentos/guix/guix/utils.scm
>     ;;; WARNING: compilation of
> /home/anonimo/Documentos/guix/guix/utils.scm failed:
>     ;;; ERROR: no code for module (guix config)
>     ;;; WARNING: compilation of
> /home/anonimo/Documentos/guix/guix/ui.scm failed:
>     ;;; ERROR: no code for module (guix config)
>     ;;; compiling /home/anonimo/Documentos/guix/guix/store.scm
>     ;;; WARNING: compilation of
> /home/anonimo/Documentos/guix/guix/store.scm failed:
>     ;;; ERROR: no code for module (guix config)
>     ;;; WARNING: compilation of
> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
>     ;;; ERROR: no code for module (guix config)
>     While compiling expression:
>     ERROR: no binding `guix-warning-port' in module (guix ui)
>
> And still curious about how to import guix modules without using a
> checkout :)

This part requires a Guix installation; a mere checkout won’t do, it has
to be configured (the (guix config) module is created by ./configure).
I think it doesn’t require a running daemon though, so you could do away
by simply making a checkout and running ./configure in there.

HTH!

Ludo’.

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-21 09:01, ludo@gnu.org wrote:
> ¡Hola!
> 
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> On 2016-11-20 15:17, Luis Felipe López Acevedo wrote:
>>> On 2016-11-15 04:57, ludo@gnu.org wrote:
>>>> Hello!
>>>> 
>>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>>> 
>>>>> I cloned the website to try a fix for bug #22115, and wanted to ask
>>>>> first what process do you follow to try out the whole website
>>>>> locally?
>>>>> When I build and serve the website with Haunt, I face the following
>>>>> problems:
>>>>> 
>>>>> 1. Pages don't load static files because they are looking for the
>>>>> "static" directory in "/software/guix/static". Do I need to set 
>>>>> some
>>>>> variable first?
>>>> 
>>>> To test locally, you need to do:
>>>> 
>>>>   $ GUIX_WEB_SITE_LOCAL=yes haunt build
>>>>   $ haunt serve
>>>> 
>>>> There should be no broken links, except for links to the manual or
>>>> other
>>>> parts of gnu.org.
>>>> 
>>>> I suppose this should go to README…
>>>> 
>>>>> 2. The Packages and Packages Issues pages, which are defined in 
>>>>> (www
>>>>> packages) are commented out. How do you deal with those in
>>>>> development?
>>>> 
>>>> That’s on purpose, so that people don’t need to have Guix installed 
>>>> to
>>>> hack on the web site.
>>>> 
>>>> We build these pages separately using the ‘export-web-page’ 
>>>> procedure.
>>> 
>>> Ludo, I'm not sure how to do this part. Do I just import (www) and
>>> (www packages) in a REPL, and call `export-web-page` for each page
>>> (packages index and issues)? You don't have to modify `www.scm` at 
>>> all
>>> (uncomment elements in the %web-pages list, for example)?
>>> 
>>> Also, trying just that, when I try importing (www packages), (guix 
>>> ui)
>>> is not found in my system:
>>> 
>>>     scheme@(guile-user)> (use-modules (www packages))
>>>     ;;; compiling
>>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm
>>>     ;;; WARNING: compilation of
>>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm 
>>> failed:
>>>     ;;; ERROR: no code for module (guix ui)
>>>     While compiling expression:
>>>     ERROR: no code for module (guix ui)
>>> 
>>> I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and
>>> guix is version 20161113.19. Where are Guix modules?
>>> 
>>> Thanks,
>> 
>> In the meantime, I cloned guix repo, and added the source directory to
>> Guile's load path. The error above is gone, but now I get this one:
>> 
>>     scheme@(guile-user)> (use-modules (www) (www packages))
>>     ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
>>     ;;;       or pass the --no-auto-compile argument to disable.
>>     ;;; compiling
>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm
>>     ;;; compiling /home/anonimo/Documentos/guix/guix/ui.scm
>>     ;;; compiling /home/anonimo/Documentos/guix/guix/utils.scm
>>     ;;; WARNING: compilation of
>> /home/anonimo/Documentos/guix/guix/utils.scm failed:
>>     ;;; ERROR: no code for module (guix config)
>>     ;;; WARNING: compilation of
>> /home/anonimo/Documentos/guix/guix/ui.scm failed:
>>     ;;; ERROR: no code for module (guix config)
>>     ;;; compiling /home/anonimo/Documentos/guix/guix/store.scm
>>     ;;; WARNING: compilation of
>> /home/anonimo/Documentos/guix/guix/store.scm failed:
>>     ;;; ERROR: no code for module (guix config)
>>     ;;; WARNING: compilation of
>> /home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
>>     ;;; ERROR: no code for module (guix config)
>>     While compiling expression:
>>     ERROR: no binding `guix-warning-port' in module (guix ui)
>> 
>> And still curious about how to import guix modules without using a
>> checkout :)
> 
> This part requires a Guix installation; a mere checkout won’t do, it 
> has
> to be configured (the (guix config) module is created by ./configure).
> I think it doesn’t require a running daemon though, so you could do 
> away
> by simply making a checkout and running ./configure in there.

Yeah, I just figured that one out :P

However, I have another problem:

     scheme@(guile-user)> (export-web-page packages-page 
"site/packages/index.html")
     gnu/packages/databases.scm:87:21: In procedure #<procedure c375ef0 
at gnu/packages/databases.scm:80:12 ()>:
     gnu/packages/databases.scm:87:21: Throw to key `srfi-34' with args 
`(#<condition &message [message: "4store-fix-buildsystem.patch: patch 
not found"] d5b3220>)'.

     Entering a new prompt.  Type `,bt' for a backtrace or `,q' to 
continue.

I'm clueless about that,


P. S.: Maybe we should find a way to test these kinds of pages with 
dummy objects?


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> However, I have another problem:
>
>     scheme@(guile-user)> (export-web-page packages-page
> "site/packages/index.html")
>     gnu/packages/databases.scm:87:21: In procedure #<procedure c375ef0
> at gnu/packages/databases.scm:80:12 ()>:
>     gnu/packages/databases.scm:87:21: Throw to key `srfi-34' with args
> `(#<condition &message [message: "4store-fix-buildsystem.patch: patch
> not found"] d5b3220>)'.
>
>     Entering a new prompt.  Type `,bt' for a backtrace or `,q' to
> continue.

Somehow ‘search-patch’ from (gnu packages) doesn’t find the patch or is
not looking in the right places.

Could you check the value of (%patch-path)?

  ,use(gnu packages)
  (%patch-path)

HTH,
Ludo’.

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-22 17:52, ludo@gnu.org wrote:
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> However, I have another problem:
>> 
>>     scheme@(guile-user)> (export-web-page packages-page
>> "site/packages/index.html")
>>     gnu/packages/databases.scm:87:21: In procedure #<procedure c375ef0
>> at gnu/packages/databases.scm:80:12 ()>:
>>     gnu/packages/databases.scm:87:21: Throw to key `srfi-34' with args
>> `(#<condition &message [message: "4store-fix-buildsystem.patch: patch
>> not found"] d5b3220>)'.
>> 
>>     Entering a new prompt.  Type `,bt' for a backtrace or `,q' to
>> continue.
> 
> Somehow ‘search-patch’ from (gnu packages) doesn’t find the patch or is
> not looking in the right places.
> 
> Could you check the value of (%patch-path)?
> 
>   ,use(gnu packages)
>   (%patch-path)

Ok, this is what I have:

("/home/anonimo/Documentos/guix-artwork/website"
  "/home/anonimo/.guix-profile/share/guile/site/2.0"
  "/home/anonimo/Documentos/guix/"
  
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/2.0"
  
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site/2.0"
  
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site"
  "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile")

What should be there? I haven't added any patches directory to PATH, nor 
do I know where patches are...

-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> On 2016-11-22 17:52, ludo@gnu.org wrote:
>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>
>>> However, I have another problem:
>>>
>>>     scheme@(guile-user)> (export-web-page packages-page
>>> "site/packages/index.html")
>>>     gnu/packages/databases.scm:87:21: In procedure #<procedure c375ef0
>>> at gnu/packages/databases.scm:80:12 ()>:
>>>     gnu/packages/databases.scm:87:21: Throw to key `srfi-34' with args
>>> `(#<condition &message [message: "4store-fix-buildsystem.patch: patch
>>> not found"] d5b3220>)'.
>>>
>>>     Entering a new prompt.  Type `,bt' for a backtrace or `,q' to
>>> continue.
>>
>> Somehow ‘search-patch’ from (gnu packages) doesn’t find the patch or is
>> not looking in the right places.
>>
>> Could you check the value of (%patch-path)?
>>
>>   ,use(gnu packages)
>>   (%patch-path)
>
> Ok, this is what I have:
>
> ("/home/anonimo/Documentos/guix-artwork/website"
>  "/home/anonimo/.guix-profile/share/guile/site/2.0"
>  "/home/anonimo/Documentos/guix/"
>  "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/2.0"
>  "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site/2.0"
>  "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site"
>  "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile")
>
> What should be there? I haven't added any patches directory to PATH,
> nor do I know where patches are...

‘%patch-path’ is defined like this:

--8<---------------cut here---------------start------------->8---
(define %patch-path
  ;; Define it after '%package-module-path' so that '%load-path' contains user
  ;; directories, allowing patches in $GUIX_PACKAGE_PATH to be found.
  (make-parameter
   (map (lambda (directory)
          (if (string=? directory %distro-root-directory)
              (string-append directory "/gnu/packages/patches")
              directory))
        %load-path)))
--8<---------------cut here---------------end--------------->8---

So patches are looked up in the “gnu/packages/patches” sub-directory
relative to the load path entry that contains “guix.scm”.

Presumably /home/anonimo/Documentos/guix/ contains guix.scm and so
patches are expected to be in
/home/anonimo/Documentos/guix/gnu/packages/patches.

Is it the case?  Or could it be that only “4store-fix-buildsystem.patch”
is missing?

HTH,
Ludo’.

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-23 17:11, ludo@gnu.org wrote:
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> On 2016-11-22 17:52, ludo@gnu.org wrote:
>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>> 
>>>> However, I have another problem:
>>>> 
>>>>     scheme@(guile-user)> (export-web-page packages-page
>>>> "site/packages/index.html")
>>>>     gnu/packages/databases.scm:87:21: In procedure #<procedure 
>>>> c375ef0
>>>> at gnu/packages/databases.scm:80:12 ()>:
>>>>     gnu/packages/databases.scm:87:21: Throw to key `srfi-34' with 
>>>> args
>>>> `(#<condition &message [message: "4store-fix-buildsystem.patch: 
>>>> patch
>>>> not found"] d5b3220>)'.
>>>> 
>>>>     Entering a new prompt.  Type `,bt' for a backtrace or `,q' to
>>>> continue.
>>> 
>>> Somehow ‘search-patch’ from (gnu packages) doesn’t find the patch or 
>>> is
>>> not looking in the right places.
>>> 
>>> Could you check the value of (%patch-path)?
>>> 
>>>   ,use(gnu packages)
>>>   (%patch-path)
>> 
>> Ok, this is what I have:
>> 
>> ("/home/anonimo/Documentos/guix-artwork/website"
>>  "/home/anonimo/.guix-profile/share/guile/site/2.0"
>>  "/home/anonimo/Documentos/guix/"
>>  
>> "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/2.0"
>>  
>> "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site/2.0"
>>  
>> "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site"
>>  
>> "/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile")
>> 
>> What should be there? I haven't added any patches directory to PATH,
>> nor do I know where patches are...
> 
> ‘%patch-path’ is defined like this:
> 
> --8<---------------cut here---------------start------------->8---
> (define %patch-path
>   ;; Define it after '%package-module-path' so that '%load-path' 
> contains user
>   ;; directories, allowing patches in $GUIX_PACKAGE_PATH to be found.
>   (make-parameter
>    (map (lambda (directory)
>           (if (string=? directory %distro-root-directory)
>               (string-append directory "/gnu/packages/patches")
>               directory))
>         %load-path)))
> --8<---------------cut here---------------end--------------->8---
> 
> So patches are looked up in the “gnu/packages/patches” sub-directory
> relative to the load path entry that contains “guix.scm”.
> 
> Presumably /home/anonimo/Documentos/guix/ contains guix.scm and so
> patches are expected to be in
> /home/anonimo/Documentos/guix/gnu/packages/patches.
> 
> Is it the case?  Or could it be that only 
> “4store-fix-buildsystem.patch”
> is missing?

hmm, patches are in that location, and the patch not found is actually 
there as well:

     $ find -name "4store-fix-buildsystem.patch"
     ./gnu/packages/patches/4store-fix-buildsystem.patch

:(


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> On 2016-11-23 17:11, ludo@gnu.org wrote:
>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

[...]

>> ‘%patch-path’ is defined like this:
>>
>> --8<---------------cut here---------------start------------->8---
>> (define %patch-path
>>   ;; Define it after '%package-module-path' so that '%load-path'
>> contains user
>>   ;; directories, allowing patches in $GUIX_PACKAGE_PATH to be found.
>>   (make-parameter
>>    (map (lambda (directory)
>>           (if (string=? directory %distro-root-directory)
>>               (string-append directory "/gnu/packages/patches")
>>               directory))
>>         %load-path)))
>> --8<---------------cut here---------------end--------------->8---
>>
>> So patches are looked up in the “gnu/packages/patches” sub-directory
>> relative to the load path entry that contains “guix.scm”.
>>
>> Presumably /home/anonimo/Documentos/guix/ contains guix.scm and so
>> patches are expected to be in
>> /home/anonimo/Documentos/guix/gnu/packages/patches.
>>
>> Is it the case?  Or could it be that only
>> “4store-fix-buildsystem.patch”
>> is missing?
>
> hmm, patches are in that location, and the patch not found is actually
> there as well:
>
>     $ find -name "4store-fix-buildsystem.patch"
>     ./gnu/packages/patches/4store-fix-buildsystem.patch

Damn it, I’m running out of ideas.  :-)

It’s pretty clear that patches are not searched for under
/home/anonimo/Documentos/guix, which could be because you have another
guix.scm in the search path.

Can you try this:

--8<---------------cut here---------------start------------->8---
$ guile
GNU Guile 2.0.13
Copyright (C) 1995-2016 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> (@@ (gnu packages) %distro-root-directory)
$1 = "/home/ludo/soft/share/guile/site/2.0"
scheme@(guile-user)> (search-path %load-path "guix.scm")
$2 = "/home/ludo/soft/share/guile/site/2.0/guix.scm"
scheme@(guile-user)> ,use(gnu packages)
scheme@(guile-user)> (search-patch "4store-fix-buildsystem.patch")
ERROR: Throw to key `srfi-34' with args `(#<condition &message [message: "4store-fix-buildsystem.patch: patch not found"] 1d40120>)'.

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]> ,q
scheme@(guile-user)> (%patch-path)
$3 = ("/home/ludo/src/manao/ludo/guix" "/home/ludo/.config/guix/personal" "/home/ludo/.local/share/guile/site/2.0" "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches" "/home/ludo/.guix-profile/share/guile/site/2.0" "/run/current-system/profile/share/guile/site/2.0" "/home/ludo/.local/share/guile/site/2.0" "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches" "/home/ludo/.guix-profile/share/guile/site/2.0" "/run/current-system/profile/share/guile/site/2.0" "/home/ludo/.guix-profile/share/guile/site/2.0" "/run/current-system/profile/share/guile/site/2.0" "/home/ludo/soft/share/guile/2.0" "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches" "/home/ludo/soft/share/guile/site" "/home/ludo/soft/share/guile")
--8<---------------cut here---------------end--------------->8---

Most likely your %distro-root-directory points to that older guix.scm,
where the patch in question is unavailable.

HTH!

Ludo’.

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-26 12:37, ludo@gnu.org wrote:
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
>> On 2016-11-23 17:11, ludo@gnu.org wrote:
>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> 
> [...]
> 
>>> ‘%patch-path’ is defined like this:
>>> 
>>> --8<---------------cut here---------------start------------->8---
>>> (define %patch-path
>>>   ;; Define it after '%package-module-path' so that '%load-path'
>>> contains user
>>>   ;; directories, allowing patches in $GUIX_PACKAGE_PATH to be found.
>>>   (make-parameter
>>>    (map (lambda (directory)
>>>           (if (string=? directory %distro-root-directory)
>>>               (string-append directory "/gnu/packages/patches")
>>>               directory))
>>>         %load-path)))
>>> --8<---------------cut here---------------end--------------->8---
>>> 
>>> So patches are looked up in the “gnu/packages/patches” sub-directory
>>> relative to the load path entry that contains “guix.scm”.
>>> 
>>> Presumably /home/anonimo/Documentos/guix/ contains guix.scm and so
>>> patches are expected to be in
>>> /home/anonimo/Documentos/guix/gnu/packages/patches.
>>> 
>>> Is it the case?  Or could it be that only
>>> “4store-fix-buildsystem.patch”
>>> is missing?
>> 
>> hmm, patches are in that location, and the patch not found is actually
>> there as well:
>> 
>>     $ find -name "4store-fix-buildsystem.patch"
>>     ./gnu/packages/patches/4store-fix-buildsystem.patch
> 
> Damn it, I’m running out of ideas.  :-)
> 
> It’s pretty clear that patches are not searched for under
> /home/anonimo/Documentos/guix, which could be because you have another
> guix.scm in the search path.
> 
> Can you try this:
> 
> --8<---------------cut here---------------start------------->8---
> $ guile
> GNU Guile 2.0.13
> Copyright (C) 1995-2016 Free Software Foundation, Inc.
> 
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
> 
> Enter `,help' for help.
> scheme@(guile-user)> (@@ (gnu packages) %distro-root-directory)
> $1 = "/home/ludo/soft/share/guile/site/2.0"
> scheme@(guile-user)> (search-path %load-path "guix.scm")
> $2 = "/home/ludo/soft/share/guile/site/2.0/guix.scm"
> scheme@(guile-user)> ,use(gnu packages)
> scheme@(guile-user)> (search-patch "4store-fix-buildsystem.patch")
> ERROR: Throw to key `srfi-34' with args `(#<condition &message
> [message: "4store-fix-buildsystem.patch: patch not found"] 1d40120>)'.
> 
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> scheme@(guile-user) [1]> ,q
> scheme@(guile-user)> (%patch-path)
> $3 = ("/home/ludo/src/manao/ludo/guix"
> "/home/ludo/.config/guix/personal"
> "/home/ludo/.local/share/guile/site/2.0"
> "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches"
> "/home/ludo/.guix-profile/share/guile/site/2.0"
> "/run/current-system/profile/share/guile/site/2.0"
> "/home/ludo/.local/share/guile/site/2.0"
> "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches"
> "/home/ludo/.guix-profile/share/guile/site/2.0"
> "/run/current-system/profile/share/guile/site/2.0"
> "/home/ludo/.guix-profile/share/guile/site/2.0"
> "/run/current-system/profile/share/guile/site/2.0"
> "/home/ludo/soft/share/guile/2.0"
> "/home/ludo/soft/share/guile/site/2.0/gnu/packages/patches"
> "/home/ludo/soft/share/guile/site" "/home/ludo/soft/share/guile")
> --8<---------------cut here---------------end--------------->8---
> 
> Most likely your %distro-root-directory points to that older guix.scm,
> where the patch in question is unavailable.


I get this:


--8<---------------cut here---------------end--------------->8---
$ guile
GNU Guile 2.0.13
Copyright (C) 1995-2016 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> (@@ (gnu packages) %distro-root-directory)
$1 = "/home/anonimo/Documentos/guix"
scheme@(guile-user)> (search-path %load-path "guix.scm")
$2 = "/home/anonimo/Documentos/guix/guix.scm"
scheme@(guile-user)> ,use(gnu packages)
scheme@(guile-user)> (search-patch "4store-fix-buildsystem.patch")
ERROR: Throw to key `srfi-34' with args `(#<condition &message [message: 
"4store-fix-buildsystem.patch: patch not found"] a835320>)'.

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]> ,q
scheme@(guile-user)> (%patch-path)
$3 = ("/home/anonimo" "/home/anonimo/.guix-profile/share/guile/site/2.0" 
"" "/home/anonimo/Documentos/misitio" "/home/anonimo/Documentos/myglab" 
"/home/anonimo/Documentos/retsi" "/home/anonimo/Documentos/guix/" 
"/home/anonimo/Documentos/guix-artwork/website" 
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/2.0" 
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site/2.0" 
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile/site" 
"/gnu/store/dw907d51axf5xcz6qkngdb8mv1x6ja9m-guile-2.0.13/share/guile")
--8<---------------cut here---------------end--------------->8---


Searching my home directory for "guix.scm" files I get this:


--8<---------------cut here---------------end--------------->8---
$ find -name "guix.scm"
./Documentos/guix/build-aux/hydra/guix.scm
./Documentos/guix/guix.scm
--8<---------------cut here---------------end--------------->8---


So, I don't know :)


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Luis Felipe López Acevedo]

On 2016-11-26 20:02, Luis Felipe López Acevedo wrote:
> On 2016-11-26 12:37, ludo@gnu.org wrote:
>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

[...]

>>> hmm, patches are in that location, and the patch not found is 
>>> actually
>>> there as well:
>>> 
>>>     $ find -name "4store-fix-buildsystem.patch"
>>>     ./gnu/packages/patches/4store-fix-buildsystem.patch
>> 
>> Damn it, I’m running out of ideas.  :-)
>> 
>> It’s pretty clear that patches are not searched for under
>> /home/anonimo/Documentos/guix, which could be because you have another
>> guix.scm in the search path.

Son of a bean, Ludo, the problem was that I had 
"/home/anonimo/Documentos/guix/" instead of 
"/home/anonimo/Documentos/guix" on Guile's load path. I removed the 
trailing slash, and now the patch is found and I can build the Packages 
page.

Sorry for the trouble :P

-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/

Re: Website development questions

[Ludovic Courtès]

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> On 2016-11-26 20:02, Luis Felipe López Acevedo wrote:
>> On 2016-11-26 12:37, ludo@gnu.org wrote:
>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
> [...]
>
>>>> hmm, patches are in that location, and the patch not found is
>>>> actually
>>>> there as well:
>>>>
>>>>     $ find -name "4store-fix-buildsystem.patch"
>>>>     ./gnu/packages/patches/4store-fix-buildsystem.patch
>>>
>>> Damn it, I’m running out of ideas.  :-)
>>>
>>> It’s pretty clear that patches are not searched for under
>>> /home/anonimo/Documentos/guix, which could be because you have another
>>> guix.scm in the search path.
>
> Son of a bean, Ludo, the problem was that I had
> "/home/anonimo/Documentos/guix/" instead of
> "/home/anonimo/Documentos/guix" on Guile's load path. I removed the
> trailing slash, and now the patch is found and I can build the
> Packages page.
>
> Sorry for the trouble :P

No problem!  I fail to see why the trailing slash would matter, but I
leave this as an exercise for the reader.

Ludo’.