unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Sree Harsha Totakura <sreeharsha@totakura.in>
To: 16463@debbugs.gnu.org
Subject: bug#16463: Guile derivation fails to build
Date: Fri, 17 Jan 2014 11:13:18 +0100	[thread overview]
Message-ID: <52D9023E.40704@totakura.in> (raw)
In-Reply-To: <874n52zzy0.fsf@gnu.org>

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/standalone$
> sha1sum ./test-command-line-encoding2 
> 81f83b7f877a4970add5d891bf2112e028032e1d
> ./test-command-line-encoding2 
> totakura@nautophone:~/build/guile-2.0.9/test-suite/standalone$ stat
> ./test-command-line-encoding2 File:
> `./test-command-line-encoding2' Size: 455       	Blocks: 8
> IO Block: 4096   regular file Device: fe07h/65031d	Inode: 6818828
> Links: 1 Access: (0750/-rwxr-x---)  Uid: ( 1000/totakura)   Gid: (
> 1000/totakura) Access: 2014-01-17 10:08:46.471166827 +0100 Modify:
> 2012-12-17 00:27:40.000000000 +0100 Change: 2014-01-17
> 09:53:35.842651260 +0100 Birth: -

But, these change in the guix guile build directory, perhaps due to
the path overwrite from /bin/sh to
/home/nix/store/v7vpnjlrgs4w3zsgbkqplksnsncl0lv6-bash-4.2/bin/sh

> totakura@nautophone:/tmp/nix-build-guile-2.0.9.drv-0/guile-2.0.9/test-suite/standalone$
> sha1sum ./test-command-line-encoding2 
> f155f1137b326f9c16efc2c2f57fbd51e2ee24c2
> ./test-command-line-encoding2 
> totakura@nautophone:/tmp/nix-build-guile-2.0.9.drv-0/guile-2.0.9/test-suite/standalone$
> stat ./test-command-line-encoding2 File:
> `./test-command-line-encoding2' Size: 512             Blocks: 8
> IO Block: 4096   regular file Device: fe04h/65028d    Inode: 261292
> Links: 1 Access: (0755/-rwxr-xr-x)  Uid: ( 1000/totakura)   Gid: (
> 1000/totakura) Access: 2014-01-17 09:47:23.884806822 +0100 Modify:
> 2012-12-17 00:27:40.000000000 +0100 Change: 2014-01-17
> 09:44:56.468075823 +0100 Birth: - 
> totakura@nautophone:/tmp/nix-build-guile-2.0.9.drv-0/guile-2.0.9/test-suite/standalone$
> diff ./test-command-line-encoding2
> ~/build/guile-2.0.9/test-suite/standalone/test-command-line-encoding2
>  1c1 <
> #!/home/nix/store/v7vpnjlrgs4w3zsgbkqplksnsncl0lv6-bash-4.2/bin/sh 
> ---
>> #!/bin/sh

Can you check it in your guix guile directory.

Sree

  reply	other threads:[~2014-01-17 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 12:07 bug#16463: Guile derivation fails to build Sree Harsha Totakura
2014-01-16 23:32 ` Ludovic Courtès
2014-01-17  9:16   ` Sree Harsha Totakura
2014-01-17  9:42     ` Sree Harsha Totakura
2014-01-17 10:04       ` Ludovic Courtès
2014-01-17 10:13         ` Sree Harsha Totakura [this message]
2014-01-17 10:35           ` Ludovic Courtès
2014-01-17 10:44       ` Ludovic Courtès
2014-01-17 10:46         ` Sree Harsha Totakura
2014-01-17 11:08           ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D9023E.40704@totakura.in \
    --to=sreeharsha@totakura.in \
    --cc=16463@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).