From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 31108-done@debbugs.gnu.org
Subject: bug#31108: Julia: ‘objconv.zip’ modified in place on www.agner.org
Date: Mon, 12 Oct 2020 11:21:25 +0200 [thread overview]
Message-ID: <86mu0rvlyi.fsf@gmail.com> (raw)
In-Reply-To: <878schrxnu.fsf@inria.fr>
Hi Ludo,
On Thu, 08 Oct 2020 at 09:20, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>> Does it make sense to keep the bug open? If yes, could you please
>> provide a bit more information about the context?
>
> If the current Julia package doesn’t have a similar problem, I think we
> can close this bug.
Maybe I miss the bug at the time “09 Apr 2018”, where it was an upstream
mismatch. It seems fixed by these 2 commits:
--8<---------------cut here---------------start------------->8---
commit 2930a39b165ce9e13e899fe66b82c03932e0e86b
Author: Tobias Geerinckx-Rice <me@tobias.gr>
Date: Wed Oct 31 15:54:38 2018 +0100
gnu: julia: Update objconv input to 2018-10-07.
* gnu/packages/julia.scm (julia)[input]: Update objconf to 2018-10-07.
commit 81bf0fd0d4a7e78febb394576ea849285fc2d329
Author: Marius Bakke <mbakke@fastmail.com>
Date: Tue Sep 4 18:53:13 2018 +0200
gnu: julia: Update objconv input.
* gnu/packages/julia.scm (julia)[inputs]: Update the hash of "objconv", which
does not have a stable URL. Add a file name and use HTTPS while at it.
--8<---------------cut here---------------end--------------->8---
So closing! :-)
BTW, at the time (2018), the inputs were:
--8<---------------cut here---------------start------------->8---
("objconv"
,(origin
(method url-fetch)
;; No versioned URL, see <https://www.agner.org/optimize/> for updates.
(uri "https://www.agner.org/optimize/objconv.zip")
(file-name "objconv-2018-08-15.zip")
(sha256
(base32
"09y4pwxfs6fl47cyingbf95i2rxx74wmycl9fd4ldcgvpx9bzdrx"))))
--8<---------------cut here---------------end--------------->8---
and now, AFAICT, it is not the case. This ’objconv’ had been removed
from the inputs list. See commit (with the not so talkative commit
message :-))
5ef30f2a1f89397bc78af94b6ee95e9fce2f646e updating to 1.4.1.
However, on one hand this dependency seems now bundled with Julia. See
upstream ’deps/objconv.mk’:
--8<---------------cut here---------------start------------->8---
$(SRCCACHE)/objconv.zip: | $(SRCCACHE)
$(JLDOWNLOAD) $@ http://www.agner.org/optimize/objconv.zip
--8<---------------cut here---------------end--------------->8---
On the other hand, maybe ’#:make-flags’ deactivates this; I do not know,
nothing obvious. Julia needs some love and I will not have enough time
to dedicated to them. :-)
Cheers,
simon
prev parent reply other threads:[~2020-10-12 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 8:39 bug#31108: Julia: ‘objconv.zip’ modified in place on www.agner.org Ludovic Courtès
2020-10-05 21:55 ` zimoun
2020-10-08 7:20 ` Ludovic Courtès
2020-10-12 9:21 ` zimoun [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
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=86mu0rvlyi.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=31108-done@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).