GCL and dependencies on cygwin

[Jon Turney]

On 26/03/2025 11:25, Camm Maguire via Cygwin-apps wrote:
> Greetings, and thanks again so much!
> 
> Alas the autobuild failed.  I tested with a virtualbox running Windows
> 10 and what I believe is up to date stable cygwin and it succeeded.  Two
> questions:
> 
> 1) How can I ensure my test environment is as close as possible to the
> one on the autobuilder?  (In Debian there are unstable chroots....)

In theory, it's just a Windows VM with a fresh cygwin installation in it.

> 2) Can one ssh into the failing job for up to 6 hours to investigate?
> If so how does ssh need to be setup in the cygport file?  (A GCL
> contributor pointed out this possibility on macports, which I think uses
> the same machinery.)
  While this is is a technical possibility, we don't have any mechanism 
for doing this at the moment.


Fortunately, this failure reproduces locally for me, so I could take a 
little look (at first I thought this was broken by some problems in the 
new 3.6.0 Cygwin DLL, but this doesn't seem to be the case). More on 
that in a subsequent email.


I also have a few comments on your cygport file, so maybe you could post 
it here for review.

I am also confused why you didn't start with an empty repo (created by 
'git init'), rather than copying an existing one and removing all the 
files (bringing it's unwanted and potentially confusing history with it).