On Jan 17 18:25, Andrew Schulman wrote:
You're right, this isn't pretty. :-( Any progress since then?
OK, here's what I've worked out.
If SSH_KEY is set (in the environment, or in ~/.cygport.conf), then cygport
will
load that key into an ssh-agent if necessary.
Minor nit: SSH_KEY
If SSH_KEY is set (in the environment, or in ~/.cygport.conf), then cygport
will
load that key into an ssh-agent if necessary.
Minor nit: SSH_KEY as env var is so generic and easily confused with
the variables set by ssh-agent. Wouldn't something with CYGPORT in its
name be better?
On Jan 19 09:23, Andrew Schulman wrote:
If SSH_KEY is set (in the environment, or in ~/.cygport.conf), then
cygport will
load that key into an ssh-agent if necessary.
Minor nit: SSH_KEY as env var is so generic and easily confused with
the variables set by ssh-agent. Wouldn't
You're right, this isn't pretty. :-( Any progress since then?
OK, here's what I've worked out.
If SSH_KEY is set (in the environment, or in ~/.cygport.conf), then cygport will
load that key into an ssh-agent if necessary.
* If no ssh-agent is running, cygport will start one and load the
- Look if ssh-agent is running (SSH_AGENT_PID non-empty?)
- If not, start ssh-agent and ssh-add. This asks for the passphrase,
if any.
- run sftp
- If the script started ssh-agent, run eval $(ssh-agent -k)
I just played with this a bit and it turned out that you must be
It's vexing that it's so hard to find a solution to such a simple problem:
prompt the user for a password if and only if one is needed.
Indeed. Here's another crazy idea.
- Look if ssh-agent is running (SSH_AGENT_PID non-empty?)
- If not, start ssh-agent and ssh-add. This asks for the
On Jan 9 11:44, Corinna Vinschen wrote:
On Jan 9 05:35, Andrew Schulman wrote:
It's vexing that it's so hard to find a solution to such a simple
problem:
prompt the user for a password if and only if one is needed.
Indeed. Here's another crazy idea.
- Look if
On Jan 9 05:35, Andrew Schulman wrote:
It's vexing that it's so hard to find a solution to such a simple problem:
prompt the user for a password if and only if one is needed.
Indeed. Here's another crazy idea.
- Look if ssh-agent is running (SSH_AGENT_PID non-empty?)
- If not,
On Jan 5 05:43, Andrew Schulman wrote:
You're right, this isn't pretty. :-( Any progress since then?
Well, I had a good idea: set up a shared (ControlMaster) ssh connection first,
in order to get the authentication out of the way, then have the sftp batch
step
use the shared connection.
You're right, this isn't pretty. :-( Any progress since then?
Well, I had a good idea: set up a shared (ControlMaster) ssh connection first,
in order to get the authentication out of the way, then have the sftp batch step
use the shared connection.
Unfortunately it seems that that idea isn't
lftp sftp://cygwin:@cygwin.com
Sorry, should be
lftp sftp://cyg...@cygwin.com
On 2014-12-19 09:13, Andrew Schulman wrote:
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
OK, I've looked into this. It can be done, but the only solution I can
On 12/19/2014 7:13 AM, Andrew Schulman wrote:
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
OK, I've looked into this. It can be done, but the only solution I
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
OK, I've looked into this. It can be done, but the only solution I can see
so far is ugly. Here's the deal:
Andrew Schulman writes:
I don't think the !ready files should be created by cygport, at all.
Yaakov will decide, but I disagree.
Well, that's that.
The point of having an upload command
is to relieve packagers of the tedium and likelihood of getting it wrong
when they have to remember
The point of having an upload command
is to relieve packagers of the tedium and likelihood of getting it wrong
when they have to remember where to connect to and which commands to run to
put what files where. How much nicer to just run cygport up and let
cygport handle it.
It then
On Dec 8 20:40, Andrew Schulman wrote:
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
Re password prompts: I see the problem. It's because I echo the
On Dec 8 20:40, Andrew Schulman wrote:
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
Re password prompts: I see the problem. It's because I
Andrew Schulman writes:
upload
Adds the upload command: upload finished packages to cygwin.com.
I don't think the !ready files should be created by cygport, at all.
Also, I would rather want to place these files into a local
staging/mirror area first and then upload after the files have been
Andrew Schulman writes:
upload
Adds the upload command: upload finished packages to cygwin.com.
I don't think the !ready files should be created by cygport, at all.
Yaakov will decide, but I disagree. The point of having an upload command
is to relieve packagers of the tedium and
* The current implementation puts the !ready file into a package-specific
directory, e.g. /x86_64/screen, instead of /x86_64.
Should say: /x86_64/release/screen, instead of /x86_64/release.
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
Re password prompts: I see the problem. It's because I echo the lftp
script to stdout, and pipe it into lftp
BTW I see that you commented out the line:
echo rm -f !ready || echo -n
in the lftp script in __pkg_upload(). That line is there to prevent a race
condition if the maintainer has already made one upload, then later starts
to make another one, at the same time that upset starts to
On Dec 4 06:58, Andrew Schulman wrote:
BTW I see that you commented out the line:
echo rm -f !ready || echo -n
in the lftp script in __pkg_upload(). That line is there to prevent a
race
condition if the maintainer has already made one upload, then later
starts
to
On 2014-10-27 04:10, Andrew Schulman wrote:
On 2014-10-19 09:13, Andrew Schulman wrote:
I've published several improvements to cygport on Github. Each improvement
is in its own branch:
upload
Adds the upload command: upload finished packages to cygwin.com.
I definitely want to add this
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
OK. Looks good.
Re password prompts: I see the problem. It's because I echo the lftp
script to stdout, and pipe
On 2014-12-03 15:40, Andrew Schulman wrote:
Here's what I have at the moment based on your branch as of a few weeks
ago. However, with password-protected SSH keys, the password prompt
isn't handled properly. Any ideas?
OK. Looks good.
Re password prompts: I see the problem. It's because I
On 2014-10-19 09:13, Andrew Schulman wrote:
I've published several improvements to cygport on Github. Each improvement
is in its own branch:
upload
Adds the upload command: upload finished packages to cygwin.com.
I definitely want to add this feature. However, the implementation
On 2014-10-19 09:13, Andrew Schulman wrote:
I've published several improvements to cygport on Github. Each improvement
is in its own branch:
upload
Adds the upload command: upload finished packages to cygwin.com.
I definitely want to add this feature. However, the implementation is
Thanks for taking a look.
On 2014-10-19 09:13, Andrew Schulman wrote:
I've published several improvements to cygport on Github. Each improvement
is in its own branch:
upload
Adds the upload command: upload finished packages to cygwin.com.
I definitely want to add this feature.
OK. Can you please suggest a package with subpackages that I can easily
build to see what's going on in that case?
Nevermind, I'm using arpack.
On Sat, Jun 26, 2010 at 12:11:14PM +0800, JonY wrote:
On 6/26/2010 12:24, Christopher Faylor wrote:
On Sat, Jun 26, 2010 at 12:15:10AM -0400, NightStrike wrote:
On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor wrote:
On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
Hello,
I am
On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
Hello,
I am planning to bring mingw-w64 to cygwin. Here are some nits I found
when working with it.
* It sets CC=gcc
While not a major issue, it does present some issues when cross
compiling the mingw-w64 CRT.
Why would a Cygwin tool worry
On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
Hello,
I am planning to bring mingw-w64 to cygwin. Here are some nits I found
when working with it.
* It sets CC=gcc
While not a major
On Sat, Jun 26, 2010 at 12:15:10AM -0400, NightStrike wrote:
On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
Hello,
I am planning to bring mingw-w64 to cygwin. Here are some nits I found
On 6/26/2010 12:24, Christopher Faylor wrote:
On Sat, Jun 26, 2010 at 12:15:10AM -0400, NightStrike wrote:
On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
Hello,
I am planning to
36 matches
Mail list logo
