-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2014 05:12 PM, Mark H Weaver wrote:
> Until we get this straightened out, what's the most reliable way for me to
> hack the code to ensure that substitutes cannot work, ever?
As a hack, you can try removing the code after the first line from
Hi!
This patch solved this bug. Thanks!
Sree
On 02/01/2014 01:46 AM, Cyril Roelandt wrote:
> * gnu/packages/python.scm (python-2): add libffi to the inputs and use it to
> build the ctypes module.
On 01/27/2014 07:06 PM, Ludovic Courtès wrote:
> Is this fixed with the libffi change you proposed (commit
> d43547f12d4eae19845f3bf13a53a050af965063)?
I haven't tested it, but I don't think the libffi change I proposed
would fix this, because python source comes with libffi.
What I could not con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Python (both versions 2.7.6 and 3.3) installed through Guix do not
contain/install ctypes module.
> $ guix package --list-installed ;;; note: source file
> /usr/local/share/guile/site/2.0/srfi/srfi-37.scm ;;; newer
> than compiled /usr/local
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
One testcase for gstreamer-1.0.10 fails on my computer. The following
output is seen when this happens:
> Running suite(s): GstBus
>
>
> Unexpected critical/warning: Source ID 1 was not found when
> attempting to remove it 90%: Checks: 10, Fail
On 01/17/2014 11:44 AM, Ludovic Courtès wrote:
> What does this report:
>
> ./meta/guile -c '(pk (file-encoding (open-input-file
> "test-suite/standalone/test-command-line-encoding2")))'
It reports:
> bash-4.2$ meta/guile -c '(pk (file-encoding (open-input-file
> "test-suite/standalone/test-comm
On 01/17/2014 11:04 AM, Ludovic Courtès wrote:
> This is weird. In my checkout that file is 455 byte long, not 512.
> Its SHA1 is 81f83b7f877a4970add5d891bf2112e028032e1d.
>
> Can you check yours?
I have the same values from my local build:
> totakura@nautophone:~/build/guile-2.0.9/test-suite/st
On 01/17/2014 12:32 AM, Ludovic Courtès wrote:
> This is very weird. Is it reproducible? Does ‘guix-daemon’ use
> the chroot, separate name spaces, and separate build users?
Yes, it is reproducible.
>
> Does this fail in the same way?
>
> guix build -e '(@ (gnu packages base) guile-final)' -n
Hi!
Guile derivation seems to fail during `make check`. I am not sure why
Guile is even being built; all I did was to execute `guix package
install=hello`. Perhaps guile is one of the (indirect) dependencies for
hello? and hydra.gnu.org was unresponsive for some reason..
Attached is a excerpt f
Hi,
I observed the following crash when I tried to install the 'hello'
package with guix-0.5.
> $ guix package --install=hello accepted connection from pid 29177,
> uid 1000 The following package will be installed: hello-2.9 out
> /nix/store/jgvkvznlsvwax0hc29f5br508ivphks1-hello-2.9
>
> The f
On 03/23/2013 09:51 PM, Sree Harsha Totakura wrote:
>> So how do we proceed? On the GNU side, the submission as to be mailed
>> > by Monday [0].
>> >
>> > Since you’re already working on gnunet-update, perhaps it would make
>> > more sens
On 03/22/2013 03:52 PM, Ludovic Courtès wrote:
>> > No, I don't think it would interfere. Matthias and Bart will generally
>> > be happy to mentor GSoC hacking this year, and I suspect Sree Harsha
>> > wouldn't mind giving advice either, so mentoring should not be an issue.
> Great.
>
> So how do
On 03/21/2013 07:01 PM, Christian Grothoff wrote:
> On 03/21/2013 02:02 PM, Ludovic Courtès wrote:
>> Hello GNUnet!
>>
>> GNU Guix provides a transparent binary/source deployment model. A
>> server can claim: “hey, I have the binary for
>> /nix/store/v9zic07iar8w90zcy398r745w78a7lqs-emacs-24.2!”,
13 matches
Mail list logo
