unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Frederickson <jonathan@terracrypt.net>
To: 37735@debbugs.gnu.org
Subject: bug#37735: Ansible package build/installation failing
Date: Sun, 13 Oct 2019 09:45:20 -0400	[thread overview]
Message-ID: <c1c66f2c-775d-039f-8eb8-86d70e840ce9@terracrypt.net> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1884 bytes --]

I recently tried to upgrade the packages on my desktop that are
installed through Guix, and Ansible is failing to build. (I've attached
the build log to this report.) I went looking for the cause, and it
looks like... the 'wrap' phase is failing because there's no 'sbin' path
in the store dir. I tried to fix that by accounting for that case in the
Python build system: https://issues.guix.gnu.org/issue/37722

However, even after that, the 'fix-symlinks' phase (defined in the
ansible package itself) is failing:

starting phase `fix-symlinks'
Backtrace:
           8 (primitive-load "/gnu/store/x87ddva1qdjfa68sh0a74s3i6gn…")
In ice-9/eval.scm:
   191:35  7 (_ _)
In ice-9/boot-9.scm:
    829:9  6 (catch _ _ #<procedure 7ffff5bac518 at /gnu/store/qxai…> …)
In srfi/srfi-1.scm:
   863:16  5 (every1 #<procedure 7ffff4d1b120 at /gnu/store/qxai6lh…> …)
In
/gnu/store/qxai6lhbg2c4q37s5qf3cddwl0q61ng2-module-import/guix/build/gnu-build-system.scm:
   839:30  4 (_ _)
In ice-9/eval.scm:
    619:8  3 (_ #(#(#<directory (guile-user) 7ffff5c70140>) ((. #))))
In ice-9/boot-9.scm:
   260:13  2 (for-each #<procedure 7ffff4d23540 at ice-9/eval.scm:3…> …)
In ice-9/eval.scm:
    619:8  1 (_ #(#(#<directory (guile-user) 7ffff5c70140> "/gn…") #))
In unknown file:
           0 (delete-file "/gnu/store/8w285skr915h0i5yg0ky1klj1lzy7j…")

ERROR: In procedure delete-file:
In procedure delete-file: No such file or directory

This leads me to believe that the problem may have been introduced
somewhere else and that there *should* be an 'sbin' dir in that store
dir. (Although I can't see the full path in that backtrace as the string
is truncated.)

I'll keep digging, but I figured I'd post here in case anyone with
deeper knowledge of the build flow has a better idea of what's wrong.


[-- Attachment #1.1.2: xa0h9238fsx0ar16i8fx2h8nyki7v0-ansible-2.8.1.drv.bz2 --]
[-- Type: application/x-bzip, Size: 178426 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-10-13 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 13:45 Jonathan Frederickson [this message]
     [not found] ` <handler.37735.B.157097473030768.ack@debbugs.gnu.org>
2019-10-13 14:07   ` bug#37735: Acknowledgement (Ansible package build/installation failing) Jonathan Frederickson
2019-10-14 20:47 ` bug#37735: Ansible package build/installation failing Arun Isaac
2019-10-15 20:36   ` Arun Isaac

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=c1c66f2c-775d-039f-8eb8-86d70e840ce9@terracrypt.net \
    --to=jonathan@terracrypt.net \
    --cc=37735@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).