Hi Jon,

On 8/21/2025 11:32 AM, Jon Turney via Cygwin-apps wrote:
On 21/08/2025 10:26, Mark Geisert via Cygwin-apps wrote:
Replying to myself...

On 8/11/2025 1:22 AM, Mark Geisert via Cygwin-apps wrote:
Hi Vadim,

[...]
OK, I follow and agree with your reasoning.  I've applied your patches locally and built a cygutils-1.4.17-5 test release.  My usual upload workflow doesn't work anymore, likely due to the already- announced (on the cygwin-apps list) deprecation of same.  I need to work out how to accomplish the upload using current best practices. Give me a bit of time please.

I've resolved the upload workflow but am having trouble building the -5 test release package properly.  Just letting the OP know work has not stopped on this.

Uh, confused here.

If this is referring to the recent "stop sftp uploads" discussion, nothing has changed yet (indeed, it is unclear what it could change to).

So you should be able to continue to work in the way you've been used to. If that's not the case, please let us know what the problem is so we can help you.

I was talking about two different things here, sorry. The -5 package I built (that later proved to be defective) I was unable to 'cygport upload'. I don't have the session log anymore but the problem seemed to be a 'cd' command failing right after the sftp session was established.

I assumed the transition away from sftp had already commenced, so I worked out how to access the cgit-hosted cygutils repository directly.

Then I discovered the new -5 package was broken and I've been working on recovering from that using time slots too small to finish the job. I see what's going on here.. it's the kooky way patches have been handled in this project since I took it over. I finally shot myself in the foot with it and am now setting it up better and/or rejiggering it to work for this -5 release and fixing it for real when I get back from vacation. Appreciate the offer of help but this is my thing to fix. I'll ask for help if I get stuck on something.
Thanks & Regards,

..mark

Reply via email to