From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Re: SFTP release directories missing
Date: Sun, 3 Jul 2022 12:43:59 +0100 [thread overview]
Message-ID: <20220703114359.wlgmwwr3op2qf4ta@lucy.dinwoodie.org> (raw)
In-Reply-To: <924fcdc4-f9a6-abdf-39d9-23903c92486f@t-online.de>
On Sun, Jul 03, 2022 at 01:31:02PM +0200, Christian Franke wrote:
> Christian Franke wrote:
> > 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@cygwin.com
> > > 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?
> >
> > I got the same problem 2x today during upload of pass and etckeeper.
> > Could be fixed by creating the directories manually with mkdir.
> >
>
> Seems to be fixed now. Empty directories {noarch,x86,x86_64}/release
> reappeared in my lftp account.
Confirmed everything looks good for me now too, thank you for checking!
next prev parent reply other threads:[~2022-07-03 11:44 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 [this message]
2022-07-03 11:58 ` Jon Turney
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=20220703114359.wlgmwwr3op2qf4ta@lucy.dinwoodie.org \
--to=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).