|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
|
|
setup bug...In setup-1.7, on the "Select Local Package Directory" page, it says:
Select a directory where you want Setup to store the installation files it downloads. The directory will be created if it does not already exist. So, I type in a directory name: C:\TEMP\cygwin17 C:\TEMP exists, but cygwin17 does not. I get the following error popup: Could not change dir to C:\TEMP\cywin17: The system cannot find the file specified. [00000001] Abort Retry Ignore. If I manually create the cygwin17 directory (and click Retry), everything proceeds normally. This seems to be a new error, because this used to work. I won't have much time to track this down myself for a couple of weeks, so I figured I should document it here... -- Chuck |
|
|
Re: setup bug...On Tue, Nov 03, 2009 at 12:16:43PM -0500, Charles Wilson wrote:
>In setup-1.7, on the "Select Local Package Directory" page, it says: > >Select a directory where you want Setup to store the installation files >it downloads. The directory will be created if it does not already >exist. > >So, I type in a directory name: > >C:\TEMP\cygwin17 > >C:\TEMP exists, but cygwin17 does not. I get the following error popup: > >Could not change dir to C:\TEMP\cywin17: The system cannot find the file >specified. [00000001] >Abort Retry Ignore. > > >If I manually create the cygwin17 directory (and click Retry), >everything proceeds normally. > >This seems to be a new error, because this used to work. I won't have >much time to track this down myself for a couple of weeks, so I figured >I should document it here... Yeah, Mark J. Reed noticed this back in September. I've been keeping his message in my inbox as a "todo" item just in case no one else got around to it: http://cygwin.com/ml/cygwin/2009-09/msg00752.html I looked into this briefly back then and I don't think I saw any possibility that this ever worked but maybe I was wrong. cgf |
|
|
Re: setup bug...On Nov 3 12:37, Christopher Faylor wrote:
> On Tue, Nov 03, 2009 at 12:16:43PM -0500, Charles Wilson wrote: > >In setup-1.7, on the "Select Local Package Directory" page, it says: > > > >Select a directory where you want Setup to store the installation files > >it downloads. The directory will be created if it does not already > >exist. > > > >So, I type in a directory name: > > > >C:\TEMP\cygwin17 > > > >C:\TEMP exists, but cygwin17 does not. I get the following error popup: > > > >Could not change dir to C:\TEMP\cywin17: The system cannot find the file > >specified. [00000001] > >Abort Retry Ignore. > > > > > >If I manually create the cygwin17 directory (and click Retry), > >everything proceeds normally. > > > >This seems to be a new error, because this used to work. I won't have > >much time to track this down myself for a couple of weeks, so I figured > >I should document it here... > > Yeah, Mark J. Reed noticed this back in September. I've been keeping > his message in my inbox as a "todo" item just in case no one else got > around to it: > > http://cygwin.com/ml/cygwin/2009-09/msg00752.html > > I looked into this briefly back then and I don't think I saw any > possibility that this ever worked but maybe I was wrong. Shouldn't a simple call to mkdir_p prior to calling SetCurrentDirectoryA be enough to get this working? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat |
|
|
Re: setup bug...On Tue, Nov 03, 2009 at 06:56:33PM +0100, Corinna Vinschen wrote:
>On Nov 3 12:37, Christopher Faylor wrote: >> On Tue, Nov 03, 2009 at 12:16:43PM -0500, Charles Wilson wrote: >> >In setup-1.7, on the "Select Local Package Directory" page, it says: >> > >> >Select a directory where you want Setup to store the installation files >> >it downloads. The directory will be created if it does not already >> >exist. >> > >> >So, I type in a directory name: >> > >> >C:\TEMP\cygwin17 >> > >> >C:\TEMP exists, but cygwin17 does not. I get the following error popup: >> > >> >Could not change dir to C:\TEMP\cywin17: The system cannot find the file >> >specified. [00000001] >> >Abort Retry Ignore. >> > >> > >> >If I manually create the cygwin17 directory (and click Retry), >> >everything proceeds normally. >> > >> >This seems to be a new error, because this used to work. I won't have >> >much time to track this down myself for a couple of weeks, so I figured >> >I should document it here... >> >> Yeah, Mark J. Reed noticed this back in September. I've been keeping >> his message in my inbox as a "todo" item just in case no one else got >> around to it: >> >> http://cygwin.com/ml/cygwin/2009-09/msg00752.html >> >> I looked into this briefly back then and I don't think I saw any >> possibility that this ever worked but maybe I was wrong. > >Shouldn't a simple call to mkdir_p prior to calling SetCurrentDirectoryA >be enough to get this working? Yes, I think so. cgf |
|
|
Re: setup bug...Charles Wilson wrote:
> In setup-1.7, on the "Select Local Package Directory" page, it says: > > Select a directory where you want Setup to store the installation files > it downloads. The directory will be created if it does not already > exist. > > So, I type in a directory name: > > C:\TEMP\cygwin17 > > C:\TEMP exists, but cygwin17 does not. I get the following error popup: > > Could not change dir to C:\TEMP\cywin17: The system cannot find the file > specified. [00000001] > Abort Retry Ignore. > > > If I manually create the cygwin17 directory (and click Retry), > everything proceeds normally. > > This seems to be a new error, because this used to work. I won't have > much time to track this down myself for a couple of weeks, so I figured > I should document it here... I have a patch for this! cheers, DaveK |
|
|
Re: setup bug...On Nov 3 14:10, Christopher Faylor wrote:
> On Tue, Nov 03, 2009 at 06:56:33PM +0100, Corinna Vinschen wrote: > >On Nov 3 12:37, Christopher Faylor wrote: > >> http://cygwin.com/ml/cygwin/2009-09/msg00752.html > >> > >> I looked into this briefly back then and I don't think I saw any > >> possibility that this ever worked but maybe I was wrong. > > > >Shouldn't a simple call to mkdir_p prior to calling SetCurrentDirectoryA > >be enough to get this working? > > Yes, I think so. I've applied a matching patch. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat |
|
|
Re: setup bug...Corinna Vinschen wrote:
> On Nov 3 14:10, Christopher Faylor wrote: >> On Tue, Nov 03, 2009 at 06:56:33PM +0100, Corinna Vinschen wrote: >>> On Nov 3 12:37, Christopher Faylor wrote: >>>> http://cygwin.com/ml/cygwin/2009-09/msg00752.html >>>> >>>> I looked into this briefly back then and I don't think I saw any >>>> possibility that this ever worked but maybe I was wrong. >>> Shouldn't a simple call to mkdir_p prior to calling SetCurrentDirectoryA >>> be enough to get this working? >> Yes, I think so. > > I've applied a matching patch. Please follow the tradition of posting courtesy copies of patches to the mailing list after a commit when exercising maintainorial discretion, so that others can see what's changed without having to manually figure out the list of changed files and their revision numbers and extract it all from CVS. I've got to update my patch to compensate for the changes in this one, but the only one that I'm aware of is a single hunk that caused a conflict. cheers, DaveK |
|
|
Re: setup bug...On Wed, Nov 04, 2009 at 04:05:49PM +0000, Dave Korn wrote:
>Corinna Vinschen wrote: >>On Nov 3 14:10, Christopher Faylor wrote: >>>On Tue, Nov 03, 2009 at 06:56:33PM +0100, Corinna Vinschen wrote: >>>>On Nov 3 12:37, Christopher Faylor wrote: >>>>>http://cygwin.com/ml/cygwin/2009-09/msg00752.html >>>>> >>>>>I looked into this briefly back then and I don't think I saw any >>>>>possibility that this ever worked but maybe I was wrong. >>>>Shouldn't a simple call to mkdir_p prior to calling >>>>SetCurrentDirectoryA be enough to get this working? >>>Yes, I think so. >> >>I've applied a matching patch. > >Please follow the tradition of posting courtesy copies of patches to >the mailing list after a commit when exercising maintainorial >discretion, so that others can see what's changed without having to >manually figure out the list of changed files and their revision >numbers and extract it all from CVS. I've got to update my patch to >compensate for the changes in this one, but the only one that I'm aware >of is a single hunk that caused a conflict. Why not just subscribe to the appropriate cvs list? You'll see relevant changes there. cgf |
|
|
Re: setup bug...Christopher Faylor wrote:
> > Why not just subscribe to the appropriate cvs list? You'll see relevant > changes there. Forgetfulness its existence is really the only reason. We have this tradition over on GCC and binutils, and they have -cvs lists too; I think that it's probably because people don't want to subscribe to machine-generated spew on the whole, but of course I can always go through the archive to find individual patches that I'm interested in. Request withdrawn :) cheers, DaveK |
|
|
Re: setup bug...On Wed, Nov 04, 2009 at 04:11:42PM +0000, Dave Korn wrote:
>Christopher Faylor wrote: > >> >> Why not just subscribe to the appropriate cvs list? You'll see relevant >> changes there. > > Forgetfulness its existence is really the only reason. > > We have this tradition over on GCC and binutils, and they have -cvs lists >too; I think that it's probably because people don't want to subscribe to >machine-generated spew on the whole, but of course I can always go through the >archive to find individual patches that I'm interested in. Request withdrawn :) FWIW, I'll send you a bottle of champagne on the day that we have excessive traffic issues in cygwin-apps-cvs. cgf |
|
|
Re: setup bug...Christopher Faylor wrote:
> On Wed, Nov 04, 2009 at 04:11:42PM +0000, Dave Korn wrote: >> Christopher Faylor wrote: >> >>> Why not just subscribe to the appropriate cvs list? You'll see relevant >>> changes there. >> Forgetfulness its existence is really the only reason. >> >> We have this tradition over on GCC and binutils, and they have -cvs lists >> too; I think that it's probably because people don't want to subscribe to >> machine-generated spew on the whole, but of course I can always go through the >> archive to find individual patches that I'm interested in. Request withdrawn :) > > FWIW, I'll send you a bottle of champagne on the day that we have > excessive traffic issues in cygwin-apps-cvs. Well, let's see if I can't unleash a minor flood sometime in the next day or two anyway ... now posting! cheers, DaveK |
|
|
Re: setup bug...Dave Korn wrote:
> Christopher Faylor wrote: >> FWIW, I'll send you a bottle of champagne on the day that we have >> excessive traffic issues in cygwin-apps-cvs. > > Well, let's see if I can't unleash a minor flood sometime in the next day or > two anyway ... now posting! HOWZAT?!(*) cheers, DaveK -- (*) - Well at the very least it's one short of an over, so one must have gone wide. |
|
|
Re: setup bug...Corinna Vinschen wrote:
> I've applied a matching patch. Thanks! -- Chuck |
| Free embeddable forum powered by Nabble | Forum Help |