public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Cc: Thomas Dickey <>,
	Yaakov Selkowitz <>
Subject: Re: Change Upstream Source URIs to HTTPS
Date: Tue, 12 Apr 2022 11:48:30 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On 2022-04-11 16:13, Yaakov Selkowitz wrote:
> On 2022-04-11, 15:20, Thomas Dickey wrote:
> 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
>> to
>> At the moment I have files in both places, and am working to have
>> package scripts updated before pulling the plug on ftp.

I co-/maintain a couple of your packages, and as CygwinPorts is no 
longer used, mostly having been migrated to Cygwin packages, I had a 
look at the current packages you provide, those available in Cygwin, 
Cygwin GIT cygport source packages, maintainers, and build repos for 
some packages:


and where those had not been committed, downloaded and scanned the 
package sources, to produce the attached package info.

You missed mentioning your lynx and vttest packages Cygwin provides; 
Cygwin indent is GNU indent, and tin has been delegated to

All the packages from your site still refer to your FTP URIs:

byacc, dialog, diffstat, luit, lynx, ncurses, tack, vttest, xterm.

We can certainly update the maintained package URIs so future releases 
use your web archive rather than FTP.

I have tried using your web archives in the past and found that your 
access to your are consistently 
unreliable, and to your are 
sometimes unreliable, resulting in download failures when accessed from 
my desktop or our Scallywag CIs from Appveyor or Github, so reverted to 
using your FTP archives to which access is consistently reliable.
Perhaps you could check your web site download logs

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

[-- Attachment #2: invisible-island-net-package-cygport-sources.log --]
[-- Type: text/plain, Size: 1247 bytes --]

Package		Version		Maintainer	Git/Cygwin-Packages	Repo/Source Cygport
byacc		20170430	ORPHANED (YS)${VERSION}.tgz
dialog		1.3-3.20170131	ORPHANED (YS)${VERSION}-${RELEASE#*.}.tgz
diffstat	1.64		Eric Blake/Brian Inglis$PN/$P.tgz
indent		2.2.12		Jari Aalto		no repo	original
luit		20220111	Jon Turney${VERSION}.tgz
lynx		2.8.9-13	Corinna Vinschen	no repo$SRC_DIR.tar.bz2
ncurses		6.1-1.20190727	ORPHANED (YS)${VERSION}-${RELEASE#*.}.tgz
tack		1.08-2.20190721	ORPHANED		no repo${VERSION}-${RELEASE#*.}.tgz"
tin		2.4.3		Corinna Vinschen	no repo${P}.tar.xz
vttest		20220215	Brian Inglis$NAME/$NAME-$VERSION.tgz
xterm		370		Thomas Wolff${VERSION%[a-z]}.tgz

  parent reply	other threads:[~2022-04-12 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-04-11 22:13 ` Fwd: update urls for cygwinports Yaakov Selkowitz
2022-04-12 12:54   ` Jon Turney
2022-04-12 17:48   ` Brian Inglis [this message]
2022-04-12 17:58     ` Change Upstream Source URIs to HTTPS Brian Inglis
     [not found]     ` <>
     [not found]       ` <>
2022-04-12 21:57         ` Brian Inglis
     [not found]           ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).