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