From: Jon Turney <jon.turney@dronecode.org.uk>
To: Adam Dinwoodie <adam@dinwoodie.org>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: SFTP release directories missing
Date: Sun, 3 Jul 2022 12:58:20 +0100 [thread overview]
Message-ID: <1dab7a94-2da8-4800-1297-9cfe1a913d4f@dronecode.org.uk> (raw)
In-Reply-To: <CA+kUOanYJAW_vsLyrvni3YaV29XbbkJZ=Xxber+eK8XXGHfKbw@mail.gmail.com>
On 02/07/2022 19:15, Adam Dinwoodie wrote:
> I'm currently seeing attempts to run `cygport <blah> stage` fail with
> an error "cd: Access failed: No such file (/x86_64/release)". And
> logging in manually over sftp, that looks to be accurate; the only
> file I can see is my !mail file.
>
> ```
> $ echo $'ls\npwd\n' | sftp cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org
> Connected to cygwin.com.
> sftp> ls
> !mail
> sftp> pwd
> Remote working directory: /
> sftp>
> ```
>
> Clearly something has gone wrong with the upload space for my
> packages; can someone fix it / tell me what I need to do to fix it?
>
Thanks for reporting this.
A few weeks ago I deployed a change to calm to teach it to remove empty
directories, but it seems I made it too keen.
I've deployed a fix for that, and re-created the directories required by
cygport upload/stage.
This shouldn't happen again, but if needed, you can safely recreate
these directories manually.
We apologize for the inconvenience.
prev parent reply other threads:[~2022-07-03 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 18:15 Adam Dinwoodie
2022-07-02 21:20 ` Christian Franke
2022-07-03 11:31 ` Christian Franke
2022-07-03 11:43 ` Adam Dinwoodie
2022-07-03 11:58 ` Jon Turney [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1dab7a94-2da8-4800-1297-9cfe1a913d4f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=adam@dinwoodie.org \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).