unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 57118@debbugs.gnu.org, raingloom <raingloom@riseup.net>
Subject: [bug#57118] [PATCH] gnu: Add linode-cli.
Date: Thu, 01 Sep 2022 03:10:32 +0200	[thread overview]
Message-ID: <87v8q728un.fsf@riseup.net> (raw)
In-Reply-To: <87pmgg85ep.fsf_-_@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> raingloom <raingloom@riseup.net> skribis:
>
>> From: Csepp <raingloom@riseup.net>
>>
>> * gnu/packages/python-xyz.scm (linode-cli) (linode-openapi-spec): New variables.
>
> [...]
>
>> +;; linode-cli would normally fetch this at build time
>> +;; TODO: is there a way to refer to previous versions? is there even a point
>> +;; in trying to?
>> +(define linode-openapi-spec
>> +  (origin
>> +    (method url-fetch)
>> +    (uri "https://www.linode.com/docs/api/openapi.yaml")
>> +    (sha256
>> +     (base32
>> +      "1jcjfnagjihcy03fcmn5sghdf7a80798xjgj1x7z3ncqwd5aggwg"))))
>
> Unfortunately, as you probably guess, this file was updated in place and
> the hash is now different.
>
> Is there a stable URL for the specific version we’d want to use here?
> Otherwise it’s just too shaky: the thing will fail to build a week or
> month later, when linode.com decides to update that file.
>
> With this fixed, the patch is ready to go.
>
> Thanks in advance,
> Ludo’.

I skimmed the OpenAPI spec and couldn't find any mention of how to
access previous versions.
IMHO if there is a build failure, guix refresh -u should take care of
updating the hash.  It's better than trying to use an outdated API
description without notifying the user.




  reply	other threads:[~2022-09-01  1:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:18 [bug#57118] [PATCH] gnu: Add linode-cli raingloom
2022-08-15  8:32 ` Mathieu Othacehe
2022-08-15 11:42 ` [bug#57118] [PATCH v2] " raingloom
2022-08-31 21:33   ` [bug#57118] [PATCH] " Ludovic Courtès
2022-09-01  1:10     ` Csepp [this message]
2022-09-01  8:52       ` Ludovic Courtès
2022-09-01 20:06         ` Csepp
2022-09-02  9:13           ` Ludovic Courtès
2022-09-17 20:13             ` Csepp
2022-09-17 20:24           ` Maxime Devos
2024-04-01  7:53 ` [bug#57118] Linode-cli license Steve George

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=87v8q728un.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=57118@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 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).