all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: 62156@debbugs.gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: [bug#62156] [PATCH 0/1] gnu: Add atftp.
Date: Sun, 12 Mar 2023 21:41:38 -0700	[thread overview]
Message-ID: <cover.1678682353.git.felix.lechner@lease-up.com> (raw)

Hi,

I am not sure whether the mirror:// URL is right. It works, but there are two
lint warnings:

gnu/packages/networking.scm:2946:15: atftp@0.8.0: URI https://www.gnu.org/software/atftp/ not reachable: 404 ("Not Found")
gnu/packages/networking.scm:2921:12: atftp@0.8.0: source not archived on Software Heritage and missing from the Disarchive database

Kind regards,
Felix Lechner

* * *

Felix Lechner (1):
  gnu: Add atftp.

 gnu/packages/networking.scm | 41 +++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)


base-commit: 9584b1daa687d1212550841d1c5f62e7ffa44ffc
-- 
2.39.1





             reply	other threads:[~2023-03-13  4:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  4:41 Felix Lechner via Guix-patches via [this message]
2023-03-13  4:42 ` [bug#62156] [PATCH 1/1] gnu: Add atftp Felix Lechner via Guix-patches via
2023-03-19 23:03 ` [bug#62156] [PATCH v2] " Felix Lechner via Guix-patches via
2023-03-20  7:34 ` Sergey Trofimov
2023-03-20 16:57 ` [bug#62156] [PATCH v3 1/2] " Felix Lechner via Guix-patches via
2023-03-20 16:57   ` [bug#62156] [PATCH v3 2/2] lint: Append "/info/refs" to git-reference-url Felix Lechner via Guix-patches via
2023-03-21  4:25 ` [bug#62156] [PATCH v4 1/2] gnu: Add atftp Felix Lechner via Guix-patches via
2023-03-21  4:25   ` [bug#62156] [PATCH v4 2/2] lint: Append "/info/refs" to git-reference-url Felix Lechner via Guix-patches via
2023-03-27 16:49   ` bug#62156: [PATCH 0/1] gnu: Add atftp Ludovic Courtès

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=cover.1678682353.git.felix.lechner@lease-up.com \
    --to=guix-patches@gnu.org \
    --cc=62156@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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.