all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 46461-done@debbugs.gnu.org
Subject: bug#46461: [core-updates] fldigi missing source tarball
Date: Fri, 12 Feb 2021 14:31:18 +0100	[thread overview]
Message-ID: <87sg61v2e1.fsf@yamatai> (raw)
In-Reply-To: <20210212114316.0a19cf43@scratchpost.org>

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

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> building /gnu/store/h293gw17xn750v7sbhxrjkrq99h4mbn3-fldigi-4.1.17.tar.gz.drv...
>
> Starting download of /gnu/store/7y7xa4ks27s0i77bcllxypakl2fcivlv-fldigi-4.1.17.tar.gz
> From http://www.w1hkj.com/files/fldigi/fldigi-4.1.17.tar.gz...
> download failed "http://www.w1hkj.com/files/fldigi/fldigi-4.1.17.tar.gz" 404 "Not Found"
>
> [...]
>
> I've checked upstream, http://www.w1hkj.com/files/fldigi/ , they have only a fldigi 4.1.18 tarball.
>
> The git repository I could find, https://github.com/w1hkj/fldigi , has only tags
> up to 4.1.14.
>
> So if we used git (and thus swh) instead, we could only carry version 4.1.14.
> As it is now, upstream removing tarballs from their website will randomly break
> the build of the guix derivation--as it did here.

The git repository on Sourceforge has all the tags. I pushed a fix as
65e9f13116edc58836cdbd1da60bfb81a3d58c82 to use it instead of the
tarballs.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2021-02-12 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 10:43 bug#46461: [core-updates] fldigi missing source tarball Danny Milosavljevic
2021-02-12 13:31 ` Guillaume Le Vaillant [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=87sg61v2e1.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=46461-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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.