all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 38630-done@debbugs.gnu.org
Subject: bug#38630: Software Heritage (swh): Fix API change, causing repeatedly submitting archives
Date: Tue, 17 Dec 2019 23:32:40 +0100	[thread overview]
Message-ID: <20191217233240.09d4166a@alma-ubu> (raw)
In-Reply-To: <87h81yrjkv.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

On Tue, 17 Dec 2019 17:41:04 +0100
Ludovic Courtès <ludo@gnu.org> wrote:

> > I have not communicated with SWH about that, especially I have not
> > asked SWH why they broke the API without updating the version
> > number.  
> 
> Yeah, that’s weird, I’ve pinged them on IRC.
> 
> It seems that the removal was intentional as part of
> <https://forge.softwareheritage.org/D2167>, but it wasn’t clear
> whether the API breakage should have happened.  This led them to open
> a new task: <https://forge.softwareheritage.org/T2158>.  We should
> keep an eye on it.

I will be frequently linting and see what's happening :-)

[..]

> In the meantime, your patch looks like the right move, so you can
> push it.

Thanks for your review and further information, pushed as

356a79becc4061d158c68718ad169abac1ab672f

Closing this ticket.

Björn

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

  reply	other threads:[~2019-12-17 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15 21:34 [bug#38630] Software Heritage (swh): Fix API change, causing repeatedly submitting archives Björn Höfling
2019-12-17 16:41 ` Ludovic Courtès
2019-12-17 22:32   ` Björn Höfling [this message]
2019-12-18  9:22     ` Jonathan Brielmaier
2019-12-18 21:44       ` Björn Höfling
2019-12-20  0:48         ` Jonathan Brielmaier

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=20191217233240.09d4166a@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=38630-done@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.