From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: mc: broken source link
Date: Tue, 02 Jul 2024 14:28:19 -0700 [thread overview]
Message-ID: <28357.1719955699818752317@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_dpbyeJ1_gq2qziTuf6XuGHA5tBJfs=ukMq28uJdXbcA@mail.gmail.com>
In last weeks source URL was broken for mc. Now, it is forwarded for a new link, only.
http://www.midnight-commander.org/downloads/mc-4.8.31.tar.bz2
forwarded to:
http://ftp.midnight-commander.org/mc-4.8.31.tar.bz2
So it seems to me, mc has a new home for sources.
http://ftp.midnight-commander.org
By the way my experience is that GitHub source links of Releases/Tags are more stable to get them any of time in 24/7. GitHub.com's Bandwidth and accessibility/availability is very well. So why you said they are unstable? There are many recipes which uses GitHub source links for tar.gz files.
next prev parent reply other threads:[~2024-07-02 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 21:45 mc: broken source link Livius
2024-06-27 10:37 ` [OE-core] " Ross Burton
2024-06-27 23:10 ` Livius
2024-06-28 0:21 ` [OE-core] " Fabio Estevam
2024-06-30 11:36 ` Livius
2024-07-01 9:18 ` [OE-core] " Alexander Kanavin
2024-07-02 21:28 ` Livius [this message]
2024-07-03 9:44 ` Alexander Kanavin
[not found] ` <17DEAACE58F9A7B5.14163@lists.openembedded.org>
2024-07-03 9:50 ` Alexander Kanavin
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=28357.1719955699818752317@lists.openembedded.org \
--to=egyszeregy@freemail.hu \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox