Re: [outreach] Help trying to create R package
On Fri, Oct 19, 2018 at 6:25 PM Gábor Boskovits wrote:
>
> Hello Laura,
>
> Laura Lazzati ezt írta (időpont: 2018.
> okt. 19., P, 22:35):
> >
> > On Fri, Oct 19, 2018 at 3:45 PM Gábor Boskovits wrote:
> > >
> > > Hello Laura,
> > >
> > > Laura Lazzati ezt írta (időpont: 2018.
> > > okt. 19., P, 20:37):
> > > >
> > > > On Fri, Oct 19, 2018 at 4:29 AM Gábor Boskovits
> > > > wrote:
> > > > >
> > > > > Hello Ricardo,
> > > > >
> > > > > Ricardo Wurmus ezt írta (időpont: 2018. okt.
> > > > > 19., P 9:10):
> > > > >>
> > > > >>
> > > > >> Hi Laura,
> > > > >>
> > > > >> > with guix environment --pure guix --ad-hoc coreutils findutils
> > > > >> > which (or -C)
> > > > >> > I get, the output:
> > > > >> > Command 'lesspipe' is available in the following places
> > > > >> > * /bin/lesspipe
> > > > >> > * /usr/bin/lesspipe
> > > > >> > The command could not be located because '/bin:/usr/bin' is not
> > > > >> > included in the PATH environment variable.
> > > > >> > lesspipe: command not found
> > > > >>
> > > > >> This is because your shell initialization code (e.g. to set up the
> > > > >> prompt) refers to lesspipe. You can ignore this or remove the fancy
> > > > >> initialization.
> > > > >>
> > > > >> > There, I run which guix and get:
> > > > >> > which: no guix in
> > > > >> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > > > >>
> > > > >> That’s because “--pure” resets the PATH; that’s by design. The only
> > > > >> problem you have is that your Guix is located elsewhere. But why do
> > > > >> you
> > > > >> need Guix itself inside of an environment to build Guix?
> > > > >>
> > > > >> The point of using “guix environment --pure guix” is only to enter a
> > > > >> clean environment containing everything you need to build Guix from
> > > > >> source. So once you’re inside of this environment you can run the
> > > > >> bootstrap and configure scripts, and run make to compile the sources.
> > > > >>
> > > > >> To *use* that Guix you just built you need to use “./pre-inst-env
> > > > >> guix”
> > > > >> from the source directory.
> > > > >>
> > > > >> > The closest I got was by setting:
> > > > >> > PATH=$PATH:/usr/bin/:/bin
> > > > >> > PATH=$PATH:/usr/local/bin
> > > > >>
> > > > >> This defeats the purpose of using “--pure” as these directories
> > > > >> contain
> > > > >> all sorts of things on a foreign distro, so you lose control over the
> > > > >> environment.
> > > >
> > > > I am glad to tell you that I have followed all the commands, I will
> > > > copy some of them here just in case, and saved the output in my daily
> > > > journal of everything :)
> > > >
> > > > guix environment --pure guix --ad-hoc coreutils findutils which
> > > > ./bootstrap
> > > > ./configure --localstatedir=/var
> > > > make
> > > > echo $? ->got 0
> > > > which guix -> got
> > > > no guix in
> > > > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > > > ./pre-inst-env guix package --help -> worked fine!
> > > > ./pre-inst-env guix package -i hello -> the same
> > > > ./pre-inst-env guix package -i emacs
> > > > export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> > > > export
> > > > INFOPATH="/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
> > > > (with this two exports, I could run hello and emacs without problems)
> > > > ./pre-inst-env guix package -i nss-certs
> > > > Played a lot with
> > > > ./pre-inst-env guix build r-aspi
> > > > and
> > > > emacs gnu/packages/cran.scm
> > > > until I found out that there were syntax errors, mismatches in
> > > > parenthesis and so on, and in the last
> > > > ./pre-inst-env guix build r-aspi got:
> > > > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > > > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > > > (still that) but:
> > >
> > > This is not a problem, it just indicates that you modified cran.scm, and
> > > it will
> > > use the .scm file instead, as the .go file was compiled from an older
> > > source.
> > >
> > > > successfully built
> > > > /gnu/store/bmapswnk9li1nscfpirgzsy3npw9hyql-r-aspi-0.2.0.drv
> > > > /gnu/store/a3apqwf4hy67ms462hn802gk89x99mzh-r-aspi-0.2.0
> > > >
> > >
> > > That's great!
> > >
> > > > I am following the contribution guide now, to send the patch, I ran
> > > > ./pre-inst-env guix lint r-aspi
> > > > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > > > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > > > fetching CVE database for 2018...
> > > > fetching CVE database for 2017...
> > > > fetching CVE database for 2016...
> > > > fetching CVE database for 2015...
> > > >
> > > > Is this output OK?
> > > >
> > >
> > > Yes, this output is just fine.
> > I have already run all the commands suggested in
> >
Re: 25/65: gnu: Add sbcl-slime-swank.
Hi Pierre, m...@ambrevar.xyz (Pierre Neidhardt) skribis: > commit c4d4ae1e16254a96caaeb5ccb4486f301ae4f1b7 > Author: Pierre Neidhardt > Date: Tue Sep 11 22:59:35 2018 +0200 > > gnu: Add sbcl-slime-swank. > > * gnu/packages/lisp.scm (sbcl-slime-swank): New variable. [...] > + (method git-fetch) > + (uri (git-reference > + ;; (url "https://github.com/slime/slime/;) > + ;; (commit "841f61467c03dea9f38ff9d5af0e21a8aa29e8f7") > + ;; REVIEW: Do we need sionescu's patch to package SWANK? > + (url "https://github.com/sionescu/slime/;) > + ;; (commit "swank-asdf") > + (commit "2f7c3fcb3ac7d50d844d5c6ca0e89b52a45e1d3a"))) Leftovers? :-) > +(license (license (list license:gpl2+ license:public-domain) For the record this typo made it impossible to build Guix (“license: unbound variable”). This was easily fixed in 0ee6692a63538e874ba0b4d85584a4a73b75367c so no big deal, though make sure to run “make” before “git push” next time. Thank you for all the Common Lisp packages! Ludo’.
Re: [outreach] Help trying to create R package
Hello Laura,
Laura Lazzati ezt írta (időpont: 2018.
okt. 19., P, 22:35):
>
> On Fri, Oct 19, 2018 at 3:45 PM Gábor Boskovits wrote:
> >
> > Hello Laura,
> >
> > Laura Lazzati ezt írta (időpont: 2018.
> > okt. 19., P, 20:37):
> > >
> > > On Fri, Oct 19, 2018 at 4:29 AM Gábor Boskovits
> > > wrote:
> > > >
> > > > Hello Ricardo,
> > > >
> > > > Ricardo Wurmus ezt írta (időpont: 2018. okt. 19.,
> > > > P 9:10):
> > > >>
> > > >>
> > > >> Hi Laura,
> > > >>
> > > >> > with guix environment --pure guix --ad-hoc coreutils findutils which
> > > >> > (or -C)
> > > >> > I get, the output:
> > > >> > Command 'lesspipe' is available in the following places
> > > >> > * /bin/lesspipe
> > > >> > * /usr/bin/lesspipe
> > > >> > The command could not be located because '/bin:/usr/bin' is not
> > > >> > included in the PATH environment variable.
> > > >> > lesspipe: command not found
> > > >>
> > > >> This is because your shell initialization code (e.g. to set up the
> > > >> prompt) refers to lesspipe. You can ignore this or remove the fancy
> > > >> initialization.
> > > >>
> > > >> > There, I run which guix and get:
> > > >> > which: no guix in
> > > >> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > > >>
> > > >> That’s because “--pure” resets the PATH; that’s by design. The only
> > > >> problem you have is that your Guix is located elsewhere. But why do
> > > >> you
> > > >> need Guix itself inside of an environment to build Guix?
> > > >>
> > > >> The point of using “guix environment --pure guix” is only to enter a
> > > >> clean environment containing everything you need to build Guix from
> > > >> source. So once you’re inside of this environment you can run the
> > > >> bootstrap and configure scripts, and run make to compile the sources.
> > > >>
> > > >> To *use* that Guix you just built you need to use “./pre-inst-env guix”
> > > >> from the source directory.
> > > >>
> > > >> > The closest I got was by setting:
> > > >> > PATH=$PATH:/usr/bin/:/bin
> > > >> > PATH=$PATH:/usr/local/bin
> > > >>
> > > >> This defeats the purpose of using “--pure” as these directories contain
> > > >> all sorts of things on a foreign distro, so you lose control over the
> > > >> environment.
> > >
> > > I am glad to tell you that I have followed all the commands, I will
> > > copy some of them here just in case, and saved the output in my daily
> > > journal of everything :)
> > >
> > > guix environment --pure guix --ad-hoc coreutils findutils which
> > > ./bootstrap
> > > ./configure --localstatedir=/var
> > > make
> > > echo $? ->got 0
> > > which guix -> got
> > > no guix in
> > > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > > ./pre-inst-env guix package --help -> worked fine!
> > > ./pre-inst-env guix package -i hello -> the same
> > > ./pre-inst-env guix package -i emacs
> > > export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> > > export
> > > INFOPATH="/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
> > > (with this two exports, I could run hello and emacs without problems)
> > > ./pre-inst-env guix package -i nss-certs
> > > Played a lot with
> > > ./pre-inst-env guix build r-aspi
> > > and
> > > emacs gnu/packages/cran.scm
> > > until I found out that there were syntax errors, mismatches in
> > > parenthesis and so on, and in the last
> > > ./pre-inst-env guix build r-aspi got:
> > > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > > (still that) but:
> >
> > This is not a problem, it just indicates that you modified cran.scm, and it
> > will
> > use the .scm file instead, as the .go file was compiled from an older
> > source.
> >
> > > successfully built
> > > /gnu/store/bmapswnk9li1nscfpirgzsy3npw9hyql-r-aspi-0.2.0.drv
> > > /gnu/store/a3apqwf4hy67ms462hn802gk89x99mzh-r-aspi-0.2.0
> > >
> >
> > That's great!
> >
> > > I am following the contribution guide now, to send the patch, I ran
> > > ./pre-inst-env guix lint r-aspi
> > > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > > fetching CVE database for 2018...
> > > fetching CVE database for 2017...
> > > fetching CVE database for 2016...
> > > fetching CVE database for 2015...
> > >
> > > Is this output OK?
> > >
> >
> > Yes, this output is just fine.
> I have already run all the commands suggested in
> https://www.gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html#Submitting-Patches
> I have never used git format-patch before, I am reading documentation
> about it but I am not very sure about how to apply it to my package,
> could you help me in clarifying this last step?
Once you made a commit, and you are statisfied with it, then you can run:
git format-patch -1
to create a patch form
Re: [outreach] Help trying to create R package
On Fri, Oct 19, 2018 at 3:45 PM Gábor Boskovits wrote:
>
> Hello Laura,
>
> Laura Lazzati ezt írta (időpont: 2018.
> okt. 19., P, 20:37):
> >
> > On Fri, Oct 19, 2018 at 4:29 AM Gábor Boskovits wrote:
> > >
> > > Hello Ricardo,
> > >
> > > Ricardo Wurmus ezt írta (időpont: 2018. okt. 19., P
> > > 9:10):
> > >>
> > >>
> > >> Hi Laura,
> > >>
> > >> > with guix environment --pure guix --ad-hoc coreutils findutils which
> > >> > (or -C)
> > >> > I get, the output:
> > >> > Command 'lesspipe' is available in the following places
> > >> > * /bin/lesspipe
> > >> > * /usr/bin/lesspipe
> > >> > The command could not be located because '/bin:/usr/bin' is not
> > >> > included in the PATH environment variable.
> > >> > lesspipe: command not found
> > >>
> > >> This is because your shell initialization code (e.g. to set up the
> > >> prompt) refers to lesspipe. You can ignore this or remove the fancy
> > >> initialization.
> > >>
> > >> > There, I run which guix and get:
> > >> > which: no guix in
> > >> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > >>
> > >> That’s because “--pure” resets the PATH; that’s by design. The only
> > >> problem you have is that your Guix is located elsewhere. But why do you
> > >> need Guix itself inside of an environment to build Guix?
> > >>
> > >> The point of using “guix environment --pure guix” is only to enter a
> > >> clean environment containing everything you need to build Guix from
> > >> source. So once you’re inside of this environment you can run the
> > >> bootstrap and configure scripts, and run make to compile the sources.
> > >>
> > >> To *use* that Guix you just built you need to use “./pre-inst-env guix”
> > >> from the source directory.
> > >>
> > >> > The closest I got was by setting:
> > >> > PATH=$PATH:/usr/bin/:/bin
> > >> > PATH=$PATH:/usr/local/bin
> > >>
> > >> This defeats the purpose of using “--pure” as these directories contain
> > >> all sorts of things on a foreign distro, so you lose control over the
> > >> environment.
> >
> > I am glad to tell you that I have followed all the commands, I will
> > copy some of them here just in case, and saved the output in my daily
> > journal of everything :)
> >
> > guix environment --pure guix --ad-hoc coreutils findutils which
> > ./bootstrap
> > ./configure --localstatedir=/var
> > make
> > echo $? ->got 0
> > which guix -> got
> > no guix in
> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> > ./pre-inst-env guix package --help -> worked fine!
> > ./pre-inst-env guix package -i hello -> the same
> > ./pre-inst-env guix package -i emacs
> > export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> > export
> > INFOPATH="/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
> > (with this two exports, I could run hello and emacs without problems)
> > ./pre-inst-env guix package -i nss-certs
> > Played a lot with
> > ./pre-inst-env guix build r-aspi
> > and
> > emacs gnu/packages/cran.scm
> > until I found out that there were syntax errors, mismatches in
> > parenthesis and so on, and in the last
> > ./pre-inst-env guix build r-aspi got:
> > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > (still that) but:
>
> This is not a problem, it just indicates that you modified cran.scm, and it
> will
> use the .scm file instead, as the .go file was compiled from an older source.
>
> > successfully built
> > /gnu/store/bmapswnk9li1nscfpirgzsy3npw9hyql-r-aspi-0.2.0.drv
> > /gnu/store/a3apqwf4hy67ms462hn802gk89x99mzh-r-aspi-0.2.0
> >
>
> That's great!
>
> > I am following the contribution guide now, to send the patch, I ran
> > ./pre-inst-env guix lint r-aspi
> > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > fetching CVE database for 2018...
> > fetching CVE database for 2017...
> > fetching CVE database for 2016...
> > fetching CVE database for 2015...
> >
> > Is this output OK?
> >
>
> Yes, this output is just fine.
I have already run all the commands suggested in
https://www.gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html#Submitting-Patches
I have never used git format-patch before, I am reading documentation
about it but I am not very sure about how to apply it to my package,
could you help me in clarifying this last step?
>
> > >
> > >
> > > Sorry, my bad, I missed that.
> > >
> > >>
> > >> --
> > >> Ricardo
> > >
> > > g_bor
> >
> > Regards!
> > Laura
> Best regards,
> g_bor
Regards :)
Laura
Re: [outreach] Help trying to create R package
Hello Laura,
Laura Lazzati ezt írta (időpont: 2018.
okt. 19., P, 20:37):
>
> On Fri, Oct 19, 2018 at 4:29 AM Gábor Boskovits wrote:
> >
> > Hello Ricardo,
> >
> > Ricardo Wurmus ezt írta (időpont: 2018. okt. 19., P
> > 9:10):
> >>
> >>
> >> Hi Laura,
> >>
> >> > with guix environment --pure guix --ad-hoc coreutils findutils which (or
> >> > -C)
> >> > I get, the output:
> >> > Command 'lesspipe' is available in the following places
> >> > * /bin/lesspipe
> >> > * /usr/bin/lesspipe
> >> > The command could not be located because '/bin:/usr/bin' is not
> >> > included in the PATH environment variable.
> >> > lesspipe: command not found
> >>
> >> This is because your shell initialization code (e.g. to set up the
> >> prompt) refers to lesspipe. You can ignore this or remove the fancy
> >> initialization.
> >>
> >> > There, I run which guix and get:
> >> > which: no guix in
> >> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> >>
> >> That’s because “--pure” resets the PATH; that’s by design. The only
> >> problem you have is that your Guix is located elsewhere. But why do you
> >> need Guix itself inside of an environment to build Guix?
> >>
> >> The point of using “guix environment --pure guix” is only to enter a
> >> clean environment containing everything you need to build Guix from
> >> source. So once you’re inside of this environment you can run the
> >> bootstrap and configure scripts, and run make to compile the sources.
> >>
> >> To *use* that Guix you just built you need to use “./pre-inst-env guix”
> >> from the source directory.
> >>
> >> > The closest I got was by setting:
> >> > PATH=$PATH:/usr/bin/:/bin
> >> > PATH=$PATH:/usr/local/bin
> >>
> >> This defeats the purpose of using “--pure” as these directories contain
> >> all sorts of things on a foreign distro, so you lose control over the
> >> environment.
>
> I am glad to tell you that I have followed all the commands, I will
> copy some of them here just in case, and saved the output in my daily
> journal of everything :)
>
> guix environment --pure guix --ad-hoc coreutils findutils which
> ./bootstrap
> ./configure --localstatedir=/var
> make
> echo $? ->got 0
> which guix -> got
> no guix in
> (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> ./pre-inst-env guix package --help -> worked fine!
> ./pre-inst-env guix package -i hello -> the same
> ./pre-inst-env guix package -i emacs
> export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> export INFOPATH="/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
> (with this two exports, I could run hello and emacs without problems)
> ./pre-inst-env guix package -i nss-certs
> Played a lot with
> ./pre-inst-env guix build r-aspi
> and
> emacs gnu/packages/cran.scm
> until I found out that there were syntax errors, mismatches in
> parenthesis and so on, and in the last
> ./pre-inst-env guix build r-aspi got:
> ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> (still that) but:
This is not a problem, it just indicates that you modified cran.scm, and it will
use the .scm file instead, as the .go file was compiled from an older source.
> successfully built
> /gnu/store/bmapswnk9li1nscfpirgzsy3npw9hyql-r-aspi-0.2.0.drv
> /gnu/store/a3apqwf4hy67ms462hn802gk89x99mzh-r-aspi-0.2.0
>
That's great!
> I am following the contribution guide now, to send the patch, I ran
> ./pre-inst-env guix lint r-aspi
> ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> fetching CVE database for 2018...
> fetching CVE database for 2017...
> fetching CVE database for 2016...
> fetching CVE database for 2015...
>
> Is this output OK?
>
Yes, this output is just fine.
> >
> >
> > Sorry, my bad, I missed that.
> >
> >>
> >> --
> >> Ricardo
> >
> > g_bor
>
> Regards!
> Laura
Best regards,
g_bor
Re: [outreach] Help trying to create R package
On Fri, Oct 19, 2018 at 4:29 AM Gábor Boskovits wrote:
>
> Hello Ricardo,
>
> Ricardo Wurmus ezt írta (időpont: 2018. okt. 19., P
> 9:10):
>>
>>
>> Hi Laura,
>>
>> > with guix environment --pure guix --ad-hoc coreutils findutils which (or
>> > -C)
>> > I get, the output:
>> > Command 'lesspipe' is available in the following places
>> > * /bin/lesspipe
>> > * /usr/bin/lesspipe
>> > The command could not be located because '/bin:/usr/bin' is not
>> > included in the PATH environment variable.
>> > lesspipe: command not found
>>
>> This is because your shell initialization code (e.g. to set up the
>> prompt) refers to lesspipe. You can ignore this or remove the fancy
>> initialization.
>>
>> > There, I run which guix and get:
>> > which: no guix in
>> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
>>
>> That’s because “--pure” resets the PATH; that’s by design. The only
>> problem you have is that your Guix is located elsewhere. But why do you
>> need Guix itself inside of an environment to build Guix?
>>
>> The point of using “guix environment --pure guix” is only to enter a
>> clean environment containing everything you need to build Guix from
>> source. So once you’re inside of this environment you can run the
>> bootstrap and configure scripts, and run make to compile the sources.
>>
>> To *use* that Guix you just built you need to use “./pre-inst-env guix”
>> from the source directory.
>>
>> > The closest I got was by setting:
>> > PATH=$PATH:/usr/bin/:/bin
>> > PATH=$PATH:/usr/local/bin
>>
>> This defeats the purpose of using “--pure” as these directories contain
>> all sorts of things on a foreign distro, so you lose control over the
>> environment.
I am glad to tell you that I have followed all the commands, I will
copy some of them here just in case, and saved the output in my daily
journal of everything :)
guix environment --pure guix --ad-hoc coreutils findutils which
./bootstrap
./configure --localstatedir=/var
make
echo $? ->got 0
which guix -> got
no guix in
(/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
./pre-inst-env guix package --help -> worked fine!
./pre-inst-env guix package -i hello -> the same
./pre-inst-env guix package -i emacs
export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
export INFOPATH="/home/laura/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
(with this two exports, I could run hello and emacs without problems)
./pre-inst-env guix package -i nss-certs
Played a lot with
./pre-inst-env guix build r-aspi
and
emacs gnu/packages/cran.scm
until I found out that there were syntax errors, mismatches in
parenthesis and so on, and in the last
./pre-inst-env guix build r-aspi got:
;;; note: source file /home/laura/guix/gnu/packages/cran.scm
;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
(still that) but:
successfully built /gnu/store/bmapswnk9li1nscfpirgzsy3npw9hyql-r-aspi-0.2.0.drv
/gnu/store/a3apqwf4hy67ms462hn802gk89x99mzh-r-aspi-0.2.0
I am following the contribution guide now, to send the patch, I ran
./pre-inst-env guix lint r-aspi
;;; note: source file /home/laura/guix/gnu/packages/cran.scm
;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
fetching CVE database for 2018...
fetching CVE database for 2017...
fetching CVE database for 2016...
fetching CVE database for 2015...
Is this output OK?
>
>
> Sorry, my bad, I missed that.
>
>>
>> --
>> Ricardo
>
> g_bor
Regards!
Laura
Re: 'package-name-version' and 'strip-store-file-name' does the same thing with different ways
l...@gnu.org (Ludovic Courtès) writes: > Hello Alex, > > Alex Vong skribis: > >> Btw, I also noticed that the procedure 'flatten' are defined in >> (gnu services telephony), (gnu services web) and (guix import utils). >> [I was about to define my own version of it...] >> I like the version using 'fold-right' together with 'match-lambda*' the >> most. Should we move it (guix build utils) and remove the rest? > > About ‘flatten’ specifically, I feel like it’s not a good sign in terms > of programming style when we end up using it (though we’d need to study > these specific use cases), so I’m reluctant to “standardizing” it. :-) > Your comment lead me to find out that 'append-map' is actually what I want. I am curious why it is an indication of bad style. >> Similarly, 'file-sans-extension' are defined in both (guix utils) and >> (guix build guile-build-system). They are both the same. Should we move >> them to (guix build utils) as well? > > Yes, sounds like a good idea! > OK! > Thanks, > Ludo’. signature.asc Description: PGP signature
Re: Should 'build-expression->derivation' be used for new build systems?
l...@gnu.org (Ludovic Courtès) writes: > Hello Alex, > > Alex Vong skribis: > >> I noticed that in the (guix derivations) module, >> 'build-expression->derivation' is marked as deprecated. However, I see >> that all build systems currently living in the (guix build-system ...) >> namespaces are still using it. Is this intended or will this be changed >> eventually? If this is going to change, is there an example to follow? > > For now, you have to use it. > > The story of ‘build-expression->derivation’ is that of an unfinished > transition to G-expressions. :-) > > There’s a branch called ‘wip-build-systems-gexp’ that aims to complete > that transition, but I haven’t yet gotten around to actually finishing > the work. This is one of the things I want us to complete for 1.0 > though, so sooner rather than later. May I ask why the transition? Just curious. > > Thanks, > Ludo’.
Re: New Guix reference card
On Fri, Oct 19, 2018 at 10:45 AM Ludovic Courtès wrote: > > Hello Guix! > > I’ve written a reference card for Guix, which you can find here: > > https://gnu.org/s/guix/guix-refcard.pdf Thanks! I find it really useful. I did not know you call them reference card, I generally call them cheatsheets > > The source is at: > > https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/refcard > > It’s written using the Lout document formatting system, so I provided a > simple build file such that you just have to run: > > guix build -f build.scm > > I initially tried to do this in plain TeX based on the Org-mode and GDB > refcards, on the grounds that people were more likely to be familiar > with TeX, but that turned out to be too tricky for me and I’m just more > fluent in Lout than in TeX. > > Enjoy, share, and improve! :-) > > Ludo’. >
Re: [bug#32871] Ruby 2.5, pushing to staging?
Ludovic Courtès writes: > Hi Chris, > > Christopher Baines skribis: > >> Christopher Baines writes: ... >>> Anyway, looking at the contributing guide this is possibly too big of a >>> change to push directly to master, so should I push this to the staging >>> branch? >> >> I've now gone ahead and pushed to staging. Not really sure what happens >> now will berlin and hydra pick this up automatically, and start >> building packages? > > Not yet! Primarily because we’re focusing (or trying to…) on building > core-updates so we can get it merged soonish, after which we can > hopefully merge staging. So, berlin seemed to do something [1], but most of the builds are scheduled. But yeah, waiting for core-updates is fine. 1: http://berlin.guixsd.org/eval/1072 signature.asc Description: PGP signature
Re: Should 'build-expression->derivation' be used for new build systems?
Hello Alex, Alex Vong skribis: > I noticed that in the (guix derivations) module, > 'build-expression->derivation' is marked as deprecated. However, I see > that all build systems currently living in the (guix build-system ...) > namespaces are still using it. Is this intended or will this be changed > eventually? If this is going to change, is there an example to follow? For now, you have to use it. The story of ‘build-expression->derivation’ is that of an unfinished transition to G-expressions. :-) There’s a branch called ‘wip-build-systems-gexp’ that aims to complete that transition, but I haven’t yet gotten around to actually finishing the work. This is one of the things I want us to complete for 1.0 though, so sooner rather than later. Thanks, Ludo’.
Re: FOSDEM 2019 - stand
Björn Höfling skribis: > On Sun, 9 Sep 2018 01:03:25 +0200 > Björn Höfling wrote: > > [..] > >> The stands are usually very demanded. We have better chances if we >> share the table with some other project. Should we do that? And if, >> with which project? > > I asked on the r-b mailing list. They are unsure and want to discuss it > in their next meeting: > > I'm not sure we want to commit to operating a booth a FOSDEM and I would > suggest we'll discuss this on our next IRC meeting next Tuesday, the > 23rd of October at 16 UTC on #reproducible-builds. > > I saved the date and think I can participate. Cool, let’s see what comes out of it! Thank you, Ludo’.
Re: Guix & IPFS
> As discussed before (I think?), builds are performed in an isolated > environment without network access—this is one of the measures taken to > guarantee build reproducibility and statelessness. > > So what you’re doing here (running “gx” in a derivation) cannot work. No, the above error comes from the "gx-fetch" code I've just pushed to the wip-ipfs branch. Downloaders obviously have network access, but maybe I've set it up wrong. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
Re: Trying to crosscompile for POWER9
Hello Tobias, Good to see you here. :-) Tobias Platen skribis: > When I try to compile GUIX for POWER9 an old version of GCC is used. > How do I use the gcc version used for cross compiling. > > ./pre-inst-env guix build --target=powerpc64le-linux hello Note that --target expects a GNU triplet. So it should be: --target=powerpc64le-linux-gnu That said, it may not fix the issue you encountered, as others explained. Thanks, Ludo’.
Re: Guix & IPFS
Hi,
Pierre Neidhardt skribis:
> ERROR: from shell.Get(): Post
> https://ipfs.io/api/v0/get?arg=QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky=true:
> x509: failed to load system roots and no roots provided
> retrying fetch QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky after a
> second...
> ERROR: from shell.Get(): Post
> https://ipfs.io/api/v0/get?arg=QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky=true:
> x509: failed to load system roots and no roots provided
> retrying fetch QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky after a
> second...
> ERROR: from shell.Get(): Post
> https://ipfs.io/api/v0/get?arg=QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky=true:
> x509: failed to load system roots and no roots provided
> ERROR: (install): failed to fetch package:
> QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky: Post
> https://ipfs.io/api/v0/get?arg=QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky=true:
> x509: failed to load system roots and no roots provided
> Backtrace:
>2 (primitive-load "/gnu/store/gpnysp8v5nv1l3yklbv0y5fvb0r?")
> In guix/build/gx.scm:
> 52:10 1 (gx-fetch _ _ #:gx-command _)
> In unknown file:
>0 (scm-error misc-error #f "~A" ("Cannot import gx pack?") ?)
>
> ERROR: In procedure scm-error:
> Cannot import gx package
> note: keeping build directory
> `/tmp/guix-build-ipfs-go-ipfs-cmdkit-1.1.3-1.QmSP88r-checkout.drv-1'
> builder for
> `/gnu/store/pwjnh2sp30plxbw12zmwg4p5w0wfh5fy-ipfs-go-ipfs-cmdkit-1.1.3-1.QmSP88r-checkout.drv'
> failed wi
As discussed before (I think?), builds are performed in an isolated
environment without network access—this is one of the measures taken to
guarantee build reproducibility and statelessness.
So what you’re doing here (running “gx” in a derivation) cannot work.
HTH,
Ludo’.
Re: 'package-name-version' and 'strip-store-file-name' does the same thing with different ways
Hello Alex, Alex Vong skribis: > Btw, I also noticed that the procedure 'flatten' are defined in > (gnu services telephony), (gnu services web) and (guix import utils). > [I was about to define my own version of it...] > I like the version using 'fold-right' together with 'match-lambda*' the > most. Should we move it (guix build utils) and remove the rest? About ‘flatten’ specifically, I feel like it’s not a good sign in terms of programming style when we end up using it (though we’d need to study these specific use cases), so I’m reluctant to “standardizing” it. :-) > Similarly, 'file-sans-extension' are defined in both (guix utils) and > (guix build guile-build-system). They are both the same. Should we move > them to (guix build utils) as well? Yes, sounds like a good idea! Thanks, Ludo’.
Re: Guix & IPFS
Hello, Pjotr Prins skribis: > Nix, these days, has a two phase build. In the second phase you get network > access where you can run network tests. That is kinda interesting. Interesting, do you have links to documentation or code? Thanks, Ludo.
New Guix reference card
Hello Guix! I’ve written a reference card for Guix, which you can find here: https://gnu.org/s/guix/guix-refcard.pdf The source is at: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/refcard It’s written using the Lout document formatting system, so I provided a simple build file such that you just have to run: guix build -f build.scm I initially tried to do this in plain TeX based on the Org-mode and GDB refcards, on the grounds that people were more likely to be familiar with TeX, but that turned out to be too tricky for me and I’m just more fluent in Lout than in TeX. Enjoy, share, and improve! :-) Ludo’.
Tensorflow package
Hi Guix, I was wondering if anyone is currently working on packaging Tensorflow, and if so what the progress is looking like. It looked like back in April Ricardo was least looking at it[1]. I just found out I need to use it for a collaboration, and if I can move some other work around I /might/ be able to help with the package, depending on how technical the roadblocks are. Just want to make sure I'm not repeating any work. Thanks a lot for the help! Best, Adam [1] https://lists.gnu.org/archive/html/guix-devel/2018-04/msg00276.html
Re: move "source /etc/profile" from .zlogin to .zprofile
l...@gnu.org (Ludovic Courtès) writes: > Alright, so Chris you can probably go ahead and push the patch! Sounds good! I've committed this to master as 2f4d43584cb26315c028dfbd2197da0d175933a2. -- Chris signature.asc Description: PGP signature
Re: [outreach] Help trying to create R package
Hello Ricardo, Ricardo Wurmus ezt írta (időpont: 2018. okt. 19., P 9:10): > > Hi Laura, > > > with guix environment --pure guix --ad-hoc coreutils findutils which (or > -C) > > I get, the output: > > Command 'lesspipe' is available in the following places > > * /bin/lesspipe > > * /usr/bin/lesspipe > > The command could not be located because '/bin:/usr/bin' is not > > included in the PATH environment variable. > > lesspipe: command not found > > This is because your shell initialization code (e.g. to set up the > prompt) refers to lesspipe. You can ignore this or remove the fancy > initialization. > > > There, I run which guix and get: > > which: no guix in > > > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin) > > That’s because “--pure” resets the PATH; that’s by design. The only > problem you have is that your Guix is located elsewhere. But why do you > need Guix itself inside of an environment to build Guix? > > The point of using “guix environment --pure guix” is only to enter a > clean environment containing everything you need to build Guix from > source. So once you’re inside of this environment you can run the > bootstrap and configure scripts, and run make to compile the sources. > > To *use* that Guix you just built you need to use “./pre-inst-env guix” > from the source directory. > > > The closest I got was by setting: > > PATH=$PATH:/usr/bin/:/bin > > PATH=$PATH:/usr/local/bin > > This defeats the purpose of using “--pure” as these directories contain > all sorts of things on a foreign distro, so you lose control over the > environment. > Sorry, my bad, I missed that. > -- > Ricardo > g_bor >
Re: [outreach] Help trying to create R package
Hi Laura, > with guix environment --pure guix --ad-hoc coreutils findutils which (or -C) > I get, the output: > Command 'lesspipe' is available in the following places > * /bin/lesspipe > * /usr/bin/lesspipe > The command could not be located because '/bin:/usr/bin' is not > included in the PATH environment variable. > lesspipe: command not found This is because your shell initialization code (e.g. to set up the prompt) refers to lesspipe. You can ignore this or remove the fancy initialization. > There, I run which guix and get: > which: no guix in > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin) That’s because “--pure” resets the PATH; that’s by design. The only problem you have is that your Guix is located elsewhere. But why do you need Guix itself inside of an environment to build Guix? The point of using “guix environment --pure guix” is only to enter a clean environment containing everything you need to build Guix from source. So once you’re inside of this environment you can run the bootstrap and configure scripts, and run make to compile the sources. To *use* that Guix you just built you need to use “./pre-inst-env guix” from the source directory. > The closest I got was by setting: > PATH=$PATH:/usr/bin/:/bin > PATH=$PATH:/usr/local/bin This defeats the purpose of using “--pure” as these directories contain all sorts of things on a foreign distro, so you lose control over the environment. -- Ricardo
Re: [outreach] Help trying to create R package
Helllo Laura,
Laura Lazzati ezt írta (időpont: 2018.
okt. 19., P, 5:48):
>
> On Thu, Oct 18, 2018 at 10:05 PM Laura Lazzati
> wrote:
> >
> > On Thu, Oct 18, 2018 at 3:17 PM Laura Lazzati
> > wrote:
> > >
> > > On Thu, Oct 18, 2018 at 3:15 PM Ricardo Wurmus wrote:
> > > >
> > > >
> > > > Hi Laura,
> > > >
> > > > > configure: checking for guile 2.2
> > > > > configure: found guile 2.2
> > > > > checking for guile-2.2... /usr/bin/guile-2.2
> > > > > checking for Guile version >= 2.2... 2.2.3
> > > > > checking for guild-2.2... no
> > > > > checking for guile-config-2.2... no
> > > > > checking for guile-tools-2.2... no
> > > > > configure: error: 'guild' binary not found; please check your
> > > > > guile-2.x installation.
> > > >
> > > > I recommend using “guix environment --pure guix” when on a foreign
> > > > distribution.
> > > Yes, I am trying that right now :) I'll let you know after reading
> > > Invoking guix environment and trying that. Hope this works
> > > >
> > I have tried lots of things today, not successfully.
> >
> > with guix environment guix, I get the same output that I get without
> > using guix environment (I mean, it uses the installed guix that I tend
> > to use generally)
> > the output of which guix in both cases is:
> > /home/laura/.config/guix/current/bin/guix
> >
> > with guix environment --pure guix --ad-hoc coreutils findutils which (or -C)
> > I get, the output:
> > Command 'lesspipe' is available in the following places
> > * /bin/lesspipe
> > * /usr/bin/lesspipe
> > The command could not be located because '/bin:/usr/bin' is not
> > included in the PATH environment variable.
> > lesspipe: command not found
> > There, I run which guix and get:
> > which: no guix in
> > (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
> >
> > The closest I got was by setting:
> > PATH=$PATH:/usr/bin/:/bin
> > PATH=$PATH:/usr/local/bin
> > And since I still got the issue with guile, I went to
> > /usr/bin/
> > and created a symlink
> > sudo ln -s /gnu/store/p9wm67w3rfw3hlb9iljgvsfn84mz4w9d-guile-2.2.4
> > guile-2.2.4
> > (setting guile-2.2 that whas already there to a hidden file)
> > Then the ./configure --localstatedir=/var
> > Worked fine, as well as the make (echo $? of both 0)
> > There, the result of which guix is:
> > /usr/local/bin/guix
> > ( a symlink to -> /var/guix/profiles/per-user/root/guix-profile/bin/guix)
> > I could run the ./pre-inst-env guix package -i hello, took a while but
> > worked.
> > Complained about having to do:
> > export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> > Did so.
This seems to be ok so far.
> > And finally I appended my r-aspi definition to cran.scm
> > However, everything went wrong when trying to run: (sorry, the output
> > is long and I also get the same output with ./pre-inst-env lint
> > r-aspi)
> > ./pre-inst-env guix build r-aspi
> > ;;; note: source file /home/laura/guix/gnu/packages/cran.scm
> > ;;; newer than compiled /home/laura/guix/gnu/packages/cran.go
> > guix build: warning: failed to load '(gnu packages abiword)':
> > exception thrown: # > #\t string: "a7izhueiqsdjs2eo7dfyb63cqje7mbqz6ennlyoynxxucbhpdnta"]
If I get you right, then the problem is introduced when you add the
package definition to cran.scm, since
./pre-inst-env guix package -i hello worked.
Since essentially everything is broken by the change, it is most
probable that you have some forms that
is not closed properly.
I would at first check for mismatching parenthesis.
If you can see nothing suspicious, then could you send a diff, so that
I can have a look?
> I have an update here, sorry, I can't help trying to figure out what's
> wrong. In the definition of my r-aspi, I found that the base32 was not
> well calculated, and I have already corrected that. Now this line does
> not appear anymore when throwing the same commands. the other warnings
> do. and the In procedure module-lookup: Unbound variable: continue
> too. I also tried generating the new cran.go with guild compile
> cran.scm but the output was really awful. If you need it, when you
> answer back I paste it.
> > 262f6c0>
> > guix build: warning: failed to load '(gnu packages android)':
> > In procedure module-lookup: Unbound variable: googletest
> > guix build: warning: failed to load '(gnu packages avr)':
> > In procedure module-lookup: Unbound variable: binutils
> > guix build: warning: failed to load '(gnu packages axoloti)':
> > In procedure module-lookup: Unbound variable: gcc-4.9
> > guix build: warning: failed to load '(gnu packages bioconductor)':
> > In procedure module-lookup: Unbound variable: perl-module-build
> > guix build: warning: failed to load '(gnu packages bootloaders)':
> > no binding `bc' in module (gnu packages algebra)
> > guix build: warning: failed to load '(gnu packages chemistry)':
> > In procedure module-lookup: Unbound variable: python2-numpy
> > guix build: warning: failed to load '(gnu
