From: ludo@gnu.org (Ludovic Courtès)
To: "Georges Dupéron" <jahvascriptmaniac@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Including sources in guix archive --export
Date: Tue, 02 Oct 2018 14:10:12 +0200 [thread overview]
Message-ID: <87pnwso8gr.fsf@gnu.org> (raw)
In-Reply-To: <1538480972.7259.0@smtp.gmail.com> ("Georges \=\?utf-8\?Q\?Dup\?\= \=\?utf-8\?Q\?\=C3\=A9ron\=22's\?\= message of "Tue, 02 Oct 2018 13:49:32 +0200")
Georges Dupéron <jahvascriptmaniac@gmail.com> skribis:
> On mar., oct. 2, 2018 at 11:57 , Ludovic Courtès <ludo@gnu.org> wrote:
>> Hmm no, ‘--sources=transitive’ is supposed to give you the complete
>> list
>> of source tarballs. Any idea which ones are missing
>
> The ones missing seem to be the sources used to bootstrap GCC and
> Guile (there might be a couple of false positives in that list,
> because: I added these one by one to the list after "hello" by using
> the wildcard /gnu/store/*-$i.drv, until guix build inside the VM
> stopped indicating missing dependencies):
>
> binutils-2.23.2.tar.xz
> bison-3.0.4.tar.xz
> gc-7.6.4.tar.gz
> gcc-4.8.2.tar.xz
> glibc-2.18.tar.xz
> guile-2.0.9.tar.xz
> gcc-4.9.4.tar.xz
> gettext-0.19.8.1.tar.gz
> gmp-6.1.2.tar.xz
> guile-2.2.3.tar.xz
> libatomic_ops-7.6.4.tar.gz
> libffi-3.2.1.tar.gz
> libtool-2.4.6.tar.xz
> libunistring-0.9.9.tar.xz
> m4-1.4.18.tar.xz
> perl-5.26.1.tar.gz
> pkg-config-0.29.2.tar.gz
> static-binaries.tar.xz
> texinfo-6.5.tar.xz
> zlib-1.2.11.tar.gz
Hmm, I see. Perhaps we have a bug here.
Thanks,
Ludo’.
prev parent reply other threads:[~2018-10-02 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:12 Including sources in guix archive --export Georges Dupéron
2018-09-14 10:00 ` Ludovic Courtès
2018-09-20 18:50 ` Dupéron Georges
2018-09-24 15:29 ` Ludovic Courtès
2018-09-24 19:30 ` Dupéron Georges
2018-10-02 9:57 ` Ludovic Courtès
2018-10-02 11:49 ` Georges Dupéron
2018-10-02 12:10 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnwso8gr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=jahvascriptmaniac@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.