On 2025-12-13 09:02, Jon Turney wrote:
On 27/11/2025 17:05, Brian Inglis via Cygwin-apps wrote:
On 2025-11-27 07:03, Jon Turney wrote:
On 26/11/2025 12:47, Brian Inglis via Cygwin-apps wrote:
Do not remember anything about changes to calm stashing source packages
under $MIRROR/src/release/$PKG/... which appears to have changed starting
about 2025-11-09 with a couple (xhost, ninja) in 07/ July, then libargp,
ruby-cairo, curl (source package previous release on curl site!), and
everything newer up until now?
Yeah, this is a long-overdue change as part of the groundwork for eventually
supporting arm64 packages (since I don't want to go back to the bad old days
of potentially different source packages for the same version of an x86 and
x86_64 package...)
I didn't make an announcement, as the form of the paths (relative to the
package repository root) which appear in setup.ini is considered an
implementation detail, nobody should be relying on that. We might change it
to a hash or something, one day...
At the moment this only happens for packages deployed via scallywag, since
there's still some work needed to make 'cygport upload' do the same thing.
The issue came up with the Curl website posting the previous Cygwin source
package release version:
https://curl.se/download.html#Win64cygwin
from the kernel.org mirror x86_64 release tree:
https://mirrors.kernel.org/sources.redhat.com/cygwin/x86_64/release/ curl/
curl-8.16.0-1-src.tar.xz
so what advice should we give Curl as to a canonical location where they can
find the latest Cygwin curl release source package?
Look in:
https://cygwin.com/packages/packages.json.xz # .asc/.sig/.sum?
or:
https://cygwin.com/pub/cygwin/x86_64/setup.ini{.xz,.zst,.bz2,}{.sig,}
or elsewhere, or give them the alternatives and let them decide?
I'm not sure what advice to give, as I'm not sure what the purpose is here.
If it's to show the cygwin packaging, then linking to the packaging repo might
be useful.
Thanks Jon,
It's to show the Cygwin source package version.
If it's to show how to build it on cygwin, then that kind of assumes a cygwin
installation is available, in which case, using the cygwin tools to fetch the
source package might be the best example.
Or, I mean, they've already taken on the work of checking that the mirrors is
still there and hasn't changed it's internal organization (sources.redhat.com is
long gone), so they can just link to it at the new path, which will continue to
work until the next time something changes...
So I will suggest they check:
{ftp,http{,s}}://cygwin.com/pub/cygwin/src/release/curl/
{ftp,http{,s}}://ftp.acc.umu.se/mirror/cygwin/src/release/curl/
{ftp,http{,s}}://mirror.accum.se/mirror/cygwin/src/release/curl/
using say:
$ lynx -dump -listonly -nonumbers
https://cygwin.com/pub/cygwin/src/release/curl/ | grep
'curl-[-.0-9]\+-src\.tar\.' | sort -V | tail -1
https://cygwin.com/pub/cygwin/src/release/curl/curl-8.17.0-1-src.hint
https://cygwin.com/pub/cygwin/src/release/curl/curl-8.17.0-1-src.tar.xz
or they could scan:
https://cygwin.com/packages/packages.json.xz
$ curl https://cygwin.com/packages/packages.json.xz | unxz -cd | \
jq '.packages | .[] | select(.name=="curl") | .versions.stable | last'
"8.17.0-1"
or look for the first '^source:\s' line after '^@\scurl' in:
https://cygwin.com/pub/cygwin/x86_64/setup.ini{.xz,.zst,.bz2,}
https://ftp.acc.umu.se/mirror/cygwin/x86_64/setup.ini{.xz,.zst,.bz2,}
https://mirror.accum.se/mirror/cygwin/x86_64/setup.ini{.xz,.zst,.bz2,}
using say:
$ awk -vRS='\n\n@ ' -vFS='\n' '$1 == "curl" {print $12}' setup.ini
source: src/release/curl/curl-8.17.0-1-src.tar.xz 9732016
0528eba69f488c92427274bbc28a251ed717cfef6300c5043994a2c9720af25b4e683a79ca469ec1c75cd52a1f415972ef6de5f474e8a84cffafeb6e7564ec7a
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
