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

On 2022-04-12 14:35, Thomas Dickey wrote:
> On Tue, Apr 12, 2022 at 03:18:24PM -0400, Thomas Dickey wrote:
>> On Tue, Apr 12, 2022 at 11:48:30AM -0600, Brian Inglis wrote:
>>> 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:
>>> 	<>
>>> or
>>> 	<>
>>> 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

The above repos hold current build files, plus WIP and test versions 
under playground branches.

>> I'm not moving lynx at the moment (it's going to be as much work as
>> the first batch -- best done separately for several reasons on my end).
>> Also, since it's not in
>> but seen here - an old version:
>> I put that off for further investigation.

>>> indent is GNU indent, and tin has been delegated to

>> I didn't list that, either :-)
>> I don't package tin :-)

Your package names matched ours, so I had to check the upstream.

>>> 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

>> maybe - though a recent report (with logs) from your problematic
>> downloads would help as well.

Mine have been overwritten by subsequent downloads and the CI logs 
retention has expired and they have been deleted.
I will see how I can gather evidence without overloading your 
connections or servers.

>> I was looking at these:
>> byacc/byacc.cygport:10:SRC_URI="${VERSION}.tgz"
>> dialog/dialog.cygport:9:SRC_URI="${VERSION}-${RELEASE#*.}.tgz"
>> diffstat/diffstat.cygport:10:SRC_URI="${VERSION}.tgz"
>> luit/luit.cygport:11:SRC_URI="${VERSION}.tgz"
>> ncurses/ncurses.cygport:12:SRC_URI="${VERSION}-${RELEASE#*.}.tgz"
>> tack/tack.cygport:10:SRC_URI="${VERSION}-${RELEASE#*.}.tgz"
>> xterm/xterm.cygport:13:SRC_URI="${VERSION%[a-z]}.tgz"
>> xterm/xterm.cygport:23:	PATCH_URI+="${VERSION}.patch.gz" ;;
>> That PATCH_URI is odd (perhaps a one-off from a while back).

Rather than look at CygwinPorts/-Extra which are at least a couple of 
years old, you can look in the above repos, or Cygwin source package 

>>> 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
> I'm not subscribed to that mailing list.

That's for the Cygwin app maintainers and why I CCed you.

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.]

  parent reply	other threads:[~2022-04-12 21:57 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   ` Change Upstream Source URIs to HTTPS Brian Inglis
2022-04-12 17:58     ` Brian Inglis
     [not found]     ` <>
     [not found]       ` <>
2022-04-12 21:57         ` Brian Inglis [this message]
     [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).