Thanks Leo, I found another one in 4.2.2: simlpy. Does anyone want to
teach me how to submit a patch?
Leo Famulari:
> On Thu, Sep 01, 2016 at 10:19:00PM +0000, Kete Foy wrote:
>> I found a typo in the info documentation. In the Garbage collection
>> section (chp 3), it says /comput
I found a typo in the info documentation. In the Garbage collection
section (chp 3), it says /computse/.
--
https://emailselfdefense.fsf.org
gpg --recv-key 'D7E9 5431 9C95 097F C314 C2A2 DD8C 15BD 0168 5E3A'
I have some more notes about using parted and disk encryption, so I'm
hoping I can help simplify that when I'm finished installing Guixsd.
Then, I might see if I can help with the savanah page that Ludovic
mentioned.
Taylan Ulrich Bayırlı/Kammer:
> Kete Foy writes:
>
>>
Hello, in the GuixSD documentation, in section 7.1.4.2, under the
*Wireless connection* heading, I needed to put quotes around /my-ssid/
to get the wireless service started.
--
https://emailselfdefense.fsf.org
Key fingerprint = D7E9 5431 9C95 097F C314 C2A2 DD8C 15BD 0168 5E3A
signature.asc
De
On 02/01/2015 11:52 AM, Alex Kost wrote:
And it is in GSD as well. Do you mean you can't switch your console
layout using "loadkeys colemak"? If so, then the problem is that the
upstream names this layout "en-latin9", so as a "workaround" you can try
"loadkeys en-latin9".
This worked.
Thanks
On 02/01/2015 11:52 AM, Alex Kost wrote
And it is in GSD as well. Do you mean you can't switch your console
layout using "loadkeys colemak"? If so, then the problem is that the
upstream names this layout "en-latin9", so as a "workaround" you can try
"loadkeys en-latin9".
I don't know what is t
On 01/31/2015 10:39 PM, Omar Radwan wrote:
Colemak is not very widely used
It has been in every distro for years
In my opinion, the installation media needs 2 features: Colemak and
wireless instructions.
Enhancement request for a notice of processes running old files after
upgrading a package.
In this case, the upgraded package would be a dependency of another process.
This is crucial for running patched software without security
vulnerabilities.
A guix command for listing the processes would be
On Monday, January 06, 2014 01:56:00 PM Ludovic Courtès wrote:
> Where does this build log come from?
> Apparently the log above comes from a build, i.e., something run in the
> build environment (chroot, etc.)
Yes, this comes from './pre-inst-env guix build zsh'.
> What’s installed in the users
starting phase `build'
cd . && autoconf
/nix/store/97vnvqq5daji73b71v4cnmyaa7r3hzk2-bash-4.2/bin/sh: autoconf: command
not found
Makefile:371: recipe for target 'configure' failed
make: *** [configure] Error 127
phase `build' failed after 0 seconds
$ guix package -I
autoconf2.69out
On Saturday, January 04, 2014 12:47:06 PM Ludovic Courtès wrote:
> I’d recommend looking at how that tcsetpgrp check is implemented, to see
> what makes it think it doesn’t work. In particular what does
> ‘config.log’ report about this test?
I didn't find any mention.
> The ‘license’ field shou
On Saturday, January 04, 2014 08:15:40 AM John Darrington wrote:
> The example in bash.scm is over complicated. Look at some of the examples
> in xorg.scm to see how to set configure-flags.
That got me a little further.
Src/../Src/mkmakemod.sh: line 467: /bin/sh: No such file or directory
On Friday, January 03, 2014 04:19:26 PM Ludovic Courtès wrote:
> It is called ‘x11’ (to avoid ambiguity with other licenses originating
> from MIT) in the (guix licenses) module. So you would write
>
>(define-module (gnu packages zsh)
> ...
>(license (x11-style "http://url-of/th
On Friday, January 03, 2014 06:50:40 AM John Darrington wrote:
> This would suggest that you haven't got a guix daemon running.
>
> Install guix and set up the daemon as described in Chapter 2 of the GUIX
> manual.
Thanks, here are the results:
gnu/packages/zsh.scm:12:2: warning: possibl
On Thursday, January 02, 2014 06:44:00 AM Nikita Karetnikov wrote:
> $ git clone git://git.sv.gnu.org/guix.git
> $ cd guix
> $ ./bootstrap && ./configure --localstatedir=/nix/var && make && make check
>
> (See ‘HACKING’ for more information.)
>
> Then you could add a recipe (i.e., the definition
On Thursday, January 02, 2014 06:58:47 PM Nikita Karetnikov wrote:
> Hm, I’m a bit puzzled. How did you change ‘gnu-system.am’, then?
gnu-system.am was at the top level. I didn't have a packages folder in my gnu
dir.
> Did you clone the repository or download the tarball? If not, could you
> p
On Thursday, January 02, 2014 06:50:25 AM Nikita Karetnikov wrote:
> > make[2]: *** No rule to make target `gnu/packages/zsh.scm', needed by
> > `all-
> > am'. Stop.
>
> Sorry, I totally misunderstood the context. Are you trying to add Zsh?
>
> It seems you added a line to ‘gnu-system.am’ but f
make[2]: *** No rule to make target `gnu/packages/zsh.scm', needed by `all-
am'. Stop.
On Wednesday, January 01, 2014 08:55:07 PM John Darrington wrote:
> the
> pre-inst-env file should exist in your build directory (after you have built
> guix of course)
If I finish this process, maybe somebody could use the instructions.
The location of pre-inst-env was one of my earlier questio
On Wednesday, January 01, 2014 05:50:05 PM John Darrington wrote:
> make && ./pre-inst-env guix build
"no such file or directory: ./pre-inst-env"
So I need this: http://git.savannah.gnu.org/cgit/guix.git/tree/pre-inst-env.in?
can't cd to @abs_top_srcdir@
or @abs_top_builddir@
ERROR: no code for
On Wednesday, January 01, 2014 05:09:18 PM John Darrington wrote:
> When it's ready rpPost a patch to the list. Ludovic will commit it to the
> repository (if he likes it).
This is my problem. How do I know if it works if I can't test it by building
the package?
Thanks
On Wednesday, January 01, 2014 01:52:35 PM you wrote:
> The .scm file usually stays in the directory gnu/packages/
If you mean http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/, then
how do I contribute to the project?
> "guix download" is a convenience function for package developers
back public.
On Monday, December 30, 2013 02:23:33 PM you wrote:
> On Mon, Dec 30, 2013 at 05:57:48AM -0500, Kete wrote:
> I'm asking if we're defining packages, how do we build them?
>
>
> What I do is:
>
> make && ./pre-inst-env guix build
Thank
Where does a package definition go to build a local package with Guix:
/nix/store?
Instead of ./configure, make and make install, sbcl uses a command like
this: INSTALL_ROOT=/home/me sh install.sh
How would the build-system and inputs go?
26 matches
Mail list logo
