From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31346@debbugs.gnu.org
Subject: [bug#31346] [PATCH] gnu: gnuzilla: Add mozjs-52.
Date: Fri, 25 May 2018 11:06:31 +0200 [thread overview]
Message-ID: <87zi0oyui0.fsf@gnu.org> (raw)
In-Reply-To: <87wowfannx.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Roel Janssen <roel@gnu.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>>>> + (source (origin
>>>> + (method url-fetch)
>>>> + (uri (string-append
>>>> + "https://queue.taskcluster.net/v1/task/"
>>>> + "YqG2fjJJSTGzGX090FjDYg/runs/0/artifacts/"
>>>> + "public/build/mozjs-" version ".tar.bz2"))
>>>
>>> Could we use ftp.mozilla.org instead?
>>
>> So I thought, but it doesn't seem to be available there:
>> http://ftp.mozilla.org/pub/spidermonkey/releases/
>>
>> The latest release there is version 45. In the pre-releases there's
>> version 59.
>>
>> Maybe I can add comment in the form:
>>
>> ;; The release notes at https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Releases/52
>> ;; states: “You can download full source code from treeherder, by going
>> ;; to the mozilla-esr52 repository and clicking on the first SM(pkg)
>> ;; link you see. The download link below is the result of that.
>>
>> Would that be sufficient?
>
> Yes, sure. Kinda weird they don’t use their own infrastructure.
So I added the comment and tried to build it again, but the build fails
now. I need to further investigate this.
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2018-05-25 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 21:19 [bug#31346] [PATCH] gnu: gnuzilla: Add mozjs-52 Roel Janssen
2018-05-05 20:26 ` Ludovic Courtès
2018-05-06 20:21 ` Roel Janssen
2018-05-07 8:13 ` Ludovic Courtès
2018-05-25 9:06 ` Roel Janssen [this message]
2018-08-29 20:57 ` bug#31346: " Leo Famulari
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=87zi0oyui0.fsf@gnu.org \
--to=roel@gnu.org \
--cc=31346@debbugs.gnu.org \
--cc=ludo@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 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.