From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Fwd: update urls for cygwinports
Date: Mon, 11 Apr 2022 18:13:34 -0400 [thread overview]
Message-ID: <0fbe6b6f9a8275562a783998965e59fb789dde05.camel@cygwin.com> (raw)
In-Reply-To: <20220411212028.GA1534@prl-debianold-64.jexium-island.net>
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Forwarded message — update urls for cygwinports --]
[-- Type: message/rfc822, Size: 8884 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 617 bytes --]
I'm working to phase out the ftp urls on my main website,
and see these files in cygwinports using the ftp urls:
byacc/byacc.cygport
dialog/dialog.cygport
diffstat/diffstat.cygport
luit/luit.cygport
ncurses/ncurses.cygport
tack/tack.cygport
xterm/xterm.cygport
The change is
ftp://ftp.invisible-island.net/XXX
to
https://invisible-island.net/archives/XXX
At the moment I have files in both places, and am working to have
package scripts updated before pulling the plug on ftp.
--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
[-- Attachment #2.1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next parent reply other threads:[~2022-04-11 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411212028.GA1534@prl-debianold-64.jexium-island.net>
2022-04-11 22:13 ` Yaakov Selkowitz [this message]
2022-04-12 12:54 ` Jon Turney
2022-04-12 17:48 ` Change Invisible-Island.net Upstream Source URIs to HTTPS Brian Inglis
2022-04-12 17:58 ` Brian Inglis
[not found] ` <20220412191824.GA3685@prl-debianold-64.jexium-island.net>
[not found] ` <20220412203557.GA5938@prl-debianold-64.jexium-island.net>
2022-04-12 21:57 ` Brian Inglis
[not found] ` <20220413004158.GA4268@prl-debianold-64.jexium-island.net>
2022-04-13 2:44 ` Brian Inglis
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=0fbe6b6f9a8275562a783998965e59fb789dde05.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).