From: Maxime Devos <maximedevos@telenet.be>
To: Michael Rohleder <mike@rohleder.de>, 53966@debbugs.gnu.org
Subject: [bug#53966] [PATCH] gnu: udpcast: Update to 20211207.
Date: Sun, 13 Feb 2022 10:32:09 +0100 [thread overview]
Message-ID: <68d97cac57ef847b158f60ad5953a1cd635bbd8e.camel@telenet.be> (raw)
In-Reply-To: <20220213050928.22409-1-mike@rohleder.de>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Michael Rohleder schreef op zo 13-02-2022 om 06:09 [+0100]:
> ;; XXX: Original server is at https://www.udpcast.linux.lu is
> not
> ;; reliable.
Do you know in what sense it is unreliable?
> (uri (list (string-append
> - "http://sources.buildroot.net/udpcast/udpcast-"
> - version ".tar.gz")
> - (string-append
> "https://fossies.org/linux/privat/udpcast-"
> version ".tar.gz")
> (string-append
> "https://www.udpcast.linux.lu/download/udpcast-"
> version ".tar.gz")))
>
I noticed the old URI
<https://fossies.org/linux/privat/udpcast-20200328.tar.gz/>
now is a 404. It seems like old versions are automatically removed,
so the fossies URL would be unreliable (from a reproducibility POV).
The only remaining URL is the www.udpcast.linux.lu URL. It would be
nice to have more fallbacks, so personally I would keep the
sources.buildroot.net URL, even though it currently 404s, with a
comment like
;; At time of writing, sources.buildroot.net only has old versions
;; of udpcast, but presumably it will be updated eventually.
YMMV.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-13 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 5:09 [bug#53966] [PATCH] gnu: udpcast: Update to 20211207 Michael Rohleder
2022-02-13 9:32 ` Maxime Devos [this message]
2022-02-13 16:45 ` Michael Rohleder
2022-02-14 9:57 ` bug#53966: " Nicolas Goaziou
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=68d97cac57ef847b158f60ad5953a1cd635bbd8e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53966@debbugs.gnu.org \
--cc=mike@rohleder.de \
/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.