Re: recv() timeout problem

2013-07-05 Thread Corinna Vinschen
On Jul  4 19:34, David Stacey wrote:
> Please find attached a short programme that demonstrates a problem
> I'm having with recv() timeouts. Under Fedora 19 x64, the test
> programme times out after three seconds (which is the desired
> behaviour). However, when run from Cygwin, the call to recv() never
> exits.
> 
> I am using the latest snapshot (2013-07-03) in 32-bit Cygwin. OS is
> Windows 7 Ultimate x64 SP1.
> 
> Many thanks in advance for your help,

Unfortunately that won't work at the moment.

The underlying implementation of recv is nonblocking.  A blocking
Windows recv call is noninterruptible, unfortunately (at least up to
Windows 2003), so this was necessary to handle signals or
thread-cancellation.

Due to its nonblocking nature under the hood, this doesn't support
SO_RCVTIMEO and SO_SNDTIMEO and, surprisingly, we never had a complaint
about that, despite its age.

I can't promise a quick solution, but I put implementing handling of
SO_RCVTIMEO and SO_SNDTIMEO in recv/send on my TODO list.  Of course,
patches are welcome, too.

For the time being, I suggest to use select or poll with timeout
instead.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



base-files-4.1-2

2013-07-05 Thread Ken Brown
base-files-4.1-2 was released as a test version in March 2012.  Is there 
a plan to promote it to current?  I'm not aware of any problems with it.


Ken


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: base-files-4.1-2

2013-07-05 Thread Corinna Vinschen
On Jul  5 07:33, Ken Brown wrote:
> base-files-4.1-2 was released as a test version in March 2012.  Is
> there a plan to promote it to current?  I'm not aware of any
> problems with it.

I just tried it on 64 bit, and I see some problems.

- /etc/postinstall/base-files-mketc.sh

Only cosmetically:  The dos file warning when creating the service
files is annoying.  Setting CYGWIN=nodosfilewarning might be a good
idea.

- /etc/profile.d/1777fix.sh

Calls getfacl without path.  Assuming tcsh is your login shell, at
the time this is run under tcsh, there's no default PATH set, so the
script doesn't find the tools:

  /etc/profile.d/1777fix.sh: line 36: getfacl: command not found
  /etc/profile.d/1777fix.sh: line 36: getfacl: command not found
  /etc/profile.d/1777fix.sh: line 36: getfacl: command not found
  /etc/profile.d/1777fix.sh: line 36: getfacl: command not found
  /etc/profile.d/1777fix.sh: line 36: getfacl: command not found
  /etc/profile.d/1777fix.sh: line 46: touch: command not found

Using the full path for all tools would fix that.

Other than that it's ok I think.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: recv() timeout problem

2013-07-05 Thread David Stacey

On 05/07/13 10:00, Corinna Vinschen wrote:

On Jul  4 19:34, David Stacey wrote:

>Please find attached a short programme that demonstrates a problem
>I'm having with recv() timeouts. Under Fedora 19 x64, the test
>programme times out after three seconds (which is the desired
>behaviour). However, when run from Cygwin, the call to recv() never
>exits.
>
>I am using the latest snapshot (2013-07-03) in 32-bit Cygwin. OS is
>Windows 7 Ultimate x64 SP1.
>
>Many thanks in advance for your help,

Unfortunately that won't work at the moment.

The underlying implementation of recv is nonblocking.  A blocking
Windows recv call is noninterruptible, unfortunately (at least up to
Windows 2003), so this was necessary to handle signals or
thread-cancellation.

Due to its nonblocking nature under the hood, this doesn't support
SO_RCVTIMEO and SO_SNDTIMEO and, surprisingly, we never had a complaint
about that, despite its age.

I can't promise a quick solution, but I put implementing handling of
SO_RCVTIMEO and SO_SNDTIMEO in recv/send on my TODO list.  Of course,
patches are welcome, too.

For the time being, I suggest to use select or poll with timeout
instead.


Thank you for your e-mail, and for replying so quickly. Regarding the 
recv() timeouts: no problem, it's easy enough to work around. On your 
TODO list, file this one under things to do when you've finally got that 
cat.


I think that's the last of my Poco problems out of the way. I'll give it 
a clean build and test, and send an ITP either this evening or tomorrow.


Thanks once again for your help,

Dave.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: recv() timeout problem

2013-07-05 Thread Corinna Vinschen
On Jul  5 13:41, David Stacey wrote:
> On 05/07/13 10:00, Corinna Vinschen wrote:
> >On Jul  4 19:34, David Stacey wrote:
> >>>Please find attached a short programme that demonstrates a problem
> >>>I'm having with recv() timeouts. Under Fedora 19 x64, the test
> >>>programme times out after three seconds (which is the desired
> >>>behaviour). However, when run from Cygwin, the call to recv() never
> >>>exits.
> >>>
> >>>I am using the latest snapshot (2013-07-03) in 32-bit Cygwin. OS is
> >>>Windows 7 Ultimate x64 SP1.
> >>>
> >>>Many thanks in advance for your help,
> >Unfortunately that won't work at the moment.
> >
> >The underlying implementation of recv is nonblocking.  A blocking
> >Windows recv call is noninterruptible, unfortunately (at least up to
> >Windows 2003), so this was necessary to handle signals or
> >thread-cancellation.
> >
> >Due to its nonblocking nature under the hood, this doesn't support
> >SO_RCVTIMEO and SO_SNDTIMEO and, surprisingly, we never had a complaint
> >about that, despite its age.
> >
> >I can't promise a quick solution, but I put implementing handling of
> >SO_RCVTIMEO and SO_SNDTIMEO in recv/send on my TODO list.  Of course,
> >patches are welcome, too.
> >
> >For the time being, I suggest to use select or poll with timeout
> >instead.
> 
> Thank you for your e-mail, and for replying so quickly. Regarding
> the recv() timeouts: no problem, it's easy enough to work around. On
> your TODO list, file this one under things to do when you've finally
> got that cat.

LOL.  Nah, it's an interesting little problem, I'm pretty sure I'll
have a look later this month.

> I think that's the last of my Poco problems out of the way. I'll
> give it a clean build and test, and send an ITP either this evening
> or tomorrow.
> 
> Thanks once again for your help,

No worries.  And thanks for the testcase, I'm sure I'll use it to test
the SO_RCVTIMEO implementation when I get to it.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: clang++ broken by recent GCC update

2013-07-05 Thread jojelino

On 2013-07-04 PM 9:47, Václav Zeman wrote:> Hi.
>
> The C++ part of Clang package (I have not tested the C part) is broken
> after update of GCC to 4.7.3. It cannot find standard C++ headers:
>
>
Clang does use hard-coded include path for using gcc header files.
Please build your own or you can file bug report to clang.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



lftp error SSL_connect: sslv3 alert unexpected message

2013-07-05 Thread Rafael Enrique Martinez Delgado
Hello everyone,

I have been trying to use lftp to connect sftp.am.gxsics.com but just
get the error SSL_connect: sslv3 alert unexpected message
when using cygwin built of lftp (which uses OpenSSL). I then found a
build that was done with GNUTLS with 4.3 version of lftp and this can
connect with no issues using the same script and so it seems to be
down to OpenSSL and the specific setup used by GXS which is kind of
old school with implicit ftps on port 6366. Below are the log and lftp
script.

I have tried it on Windows 7 32 bits as well as Windows 8 32 bits.
I ran cygcheck on windows 8 and got a blank file, but was able to run uname -a

CYGWIN_NT-6.2 RM-LAPTOP 1.7.20(0.266/5/3) 2013-06-07 11:11 i686 Cygwin

Thanks in advance.

set cmd:default-protocol ftps
set cmd:verify-host false
set cmd:verify-path false
set ftps:initial-prot P
set ftp:list-empty-ok true
set ftp:ssl-allow true
set ftp:ssl-auth SSL
set ftp:use-allo false
set ftp:use-fxp false
set net:idle 1
set net:max-retries 
set net:reconnect-interval-base 2
set net:reconnect-interval-max 4
set net:timeout 120
set ssl:check-hostname true
set ssl:verify-certificate false
open -d ftps://user:passw...@sftp.am.gxsics.com:6366
lcd /cygdrive/c/lftp
ls
cls
bye

 Resolving host address...
 1 address found: 204.90.130.188
 Connecting to sftp.am.gxsics.com (204.90.130.188) port 6366
 SSL_connect: sslv3 alert unexpected message
 Closing control socket
ls: Fatal error: SSL_connect: sslv3 alert unexpected message
 Connecting to sftp.am.gxsics.com (204.90.130.188) port 6366
 SSL_connect: sslv3 alert unexpected message
 Closing control socket
Fatal error: SSL_connect: sslv3 alert unexpected message

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Failure with fork() (Cygwin on Wine install now sort of works)

2013-07-05 Thread Alan W. Irwin

On 2013-07-04 13:39-0700 Alan W. Irwin wrote:


So if the consensus here after looking at the setup_install.out
results is that cygwin on Wine is more or less installed properly from
these results (except for the rename issue above which I can fix by
doing that rename manually as suggested by the error message), then
the next order of business [...]


I have now looked more carefully at the setup_install.out results that
are wrapped inside a tarball I attached to a previous post in this
thread.  At the same time I have also looked at the resulting files in
my cygwin install tree.  It turns out that because of errors the first
install script created an empty /etc/fstab rather than the desired
result and also was unable to create the /dev directory. These issues
very likely had follow-on effects for several of the other postinstall
scripts that were run (for example, all the read-only filesystem error
messages when any attempt was made to write to /dev.) Anyhow, it now
seems likely there are at least a couple of Wine bugs that are still
preventing a clean postinstall phase for setup.exe on Wine, and the
rest of this story will continue for now at
http://bugs.winehq.org/show_bug.cgi?id=24018.  Meanwhile, I thank the
people here that (a) helped to fix the Cygwin fork bug, and (b) gave
me good directions for trying out that fix before it becomes part of
an official Cygwin release.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Setup.exe crashes before opening the servers window on Windows XP

2013-07-05 Thread gialloporpora

Dear all,
I have the same problem reported in this topic:
http://cygwin.com/ml/cygwin/2008-03/msg00259.html

any time I start setup.exe (I need to update some packages)  I have this 
error message:


>
> Microsoft Visual C++ Runtime Library
> Runtime Error!
> Program: C:\cygwin\setup.exe
> This application has requested the Runtime to terminate it in an 
unusual way.

> Please contact the application's support team for more information.

unfortunatelly the modified setup.exe linked in the topic is not 
available and I don't have understand how to fix it.
I have Windows XP SP3 and it has worked fine  until my last restart. I 
have uninstalled  git  in the previous session. The cygwin environment 
seems to work fine, only setup.exe has problems.


Sandro




--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Setup.exe crashes before opening the servers window on Windows XP

2013-07-05 Thread marco atzeri

Il 7/5/2013 9:25 PM, gialloporpora ha scritto:

Dear all,
I have the same problem reported in this topic:
http://cygwin.com/ml/cygwin/2008-03/msg00259.html

any time I start setup.exe (I need to update some packages)  I have this
error message:

 >
 > Microsoft Visual C++ Runtime Library
 > Runtime Error!
 > Program: C:\cygwin\setup.exe
 > This application has requested the Runtime to terminate it in an
unusual way.
 > Please contact the application's support team for more information.

unfortunatelly the modified setup.exe linked in the topic is not
available and I don't have understand how to fix it.
I have Windows XP SP3 and it has worked fine  until my last restart. I
have uninstalled  git  in the previous session. The cygwin environment
seems to work fine, only setup.exe has problems.

Sandro



have you downloaded the latest setup or you are using an old copy ?

Marco


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: mintty not responding to ctrl-c

2013-07-05 Thread Andrey Repin
Greetings, Balaji Venkataraman!

> For some strange reason, I'm not able to get mintty to accept/respond
> to any ctrl-c input. I'm doing something as basic as this:

> $ ls [hit ctrl-c here]

> No response in mintty. Works fine in the default Cygwin terminal
> (windows terminal via cygwin.bat) and xterm. Please find attached
> cygheck -s -r -v output. TIA for any input.

If it's something like what we've faced recently, and native NT console does
not exhibit such behavior, try the snapshot cygwin1.dll.


--
WBR,
Andrey Repin (anrdae...@freemail.ru) 06.07.2013, <00:14>

Sorry for my terrible english...


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Setup.exe crashes before opening the servers window on Windows XP

2013-07-05 Thread gialloporpora

Risposta al messaggio di marco atzeri :


have you downloaded the latest setup or you are using an old copy ?


I have the latest version, I have downloaded it yesterday:

C:\cygwin>Starting cygwin install, version 2.774


and it worked fine until  I have uninstalled some packages and rebooted 
my computer.

Sandro





--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Failure with fork() (Cygwin on Wine install now sort of works)

2013-07-05 Thread Christopher Faylor
On Fri, Jul 05, 2013 at 12:11:10PM -0700, Alan W. Irwin wrote:
>On 2013-07-04 13:39-0700 Alan W. Irwin wrote:
>
>> So if the consensus here after looking at the setup_install.out
>> results is that cygwin on Wine is more or less installed properly from
>> these results (except for the rename issue above which I can fix by
>> doing that rename manually as suggested by the error message), then
>> the next order of business [...]
>
>I have now looked more carefully at the setup_install.out results that
>are wrapped inside a tarball I attached to a previous post in this
>thread.  At the same time I have also looked at the resulting files in
>my cygwin install tree.  It turns out that because of errors the first
>install script created an empty /etc/fstab rather than the desired
>result and also was unable to create the /dev directory.

The /dev directory is a pseudo-directory created on-the-fly by the
Cygwin DLL.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Setup.exe crashes before opening the servers window on Windows XP

2013-07-05 Thread gialloporpora

RiOk, thanks Marco (grazie :-))
Now I have solved. I have removed (renamed) the file setup.rc in 
/etc/setup and it works again.


Sandro




--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: lftp error SSL_connect: sslv3 alert unexpected message

2013-07-05 Thread Andrew Schulman
> Hello everyone,
> 
> I have been trying to use lftp to connect sftp.am.gxsics.com but just
> get the error SSL_connect: sslv3 alert unexpected message
> when using cygwin built of lftp (which uses OpenSSL). I then found a
> build that was done with GNUTLS with 4.3 version of lftp and this can
> connect with no issues using the same script and so it seems to be
> down to OpenSSL and the specific setup used by GXS which is kind of
> old school with implicit ftps on port 6366. Below are the log and lftp
> script.

Thanks for reporting this.  Since others have also reported recent trouble
with this build of lftp, I'll see if I can build it with GnuTLS and let you
see if that fixes your problem.

Also, I'm about to release version 4.4.8 for Cygwin, which supposedly fixes
some sftp bugs.  Please try that when it comes out, and see if that fixes
your problem.

Andrew


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: mintty not responding to ctrl-c

2013-07-05 Thread Balaji Venkataraman
On Fri, Jul 5, 2013 at 1:15 PM, Andrey Repin  wrote:

> If it's something like what we've faced recently, and native NT console does
> not exhibit such behavior, try the snapshot cygwin1.dll.

I did see that thread and thought it was perhaps related to that. And
yes, I was using a fairly recent snapshot (Snapshot date:
20130627-19:17:14) - see the cygcheck output in the original email.
Would appreciate any leads.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Failure with fork() (Cygwin on Wine install now sort of works)

2013-07-05 Thread Alan W. Irwin

On 2013-07-05 16:48-0400 Christopher Faylor wrote:


On Fri, Jul 05, 2013 at 12:11:10PM -0700, Alan W. Irwin wrote:

On 2013-07-04 13:39-0700 Alan W. Irwin wrote:


So if the consensus here after looking at the setup_install.out
results is that cygwin on Wine is more or less installed properly from
these results (except for the rename issue above which I can fix by
doing that rename manually as suggested by the error message), then
the next order of business [...]


I have now looked more carefully at the setup_install.out results that
are wrapped inside a tarball I attached to a previous post in this
thread.  At the same time I have also looked at the resulting files in
my cygwin install tree.  It turns out that because of errors the first
install script created an empty /etc/fstab rather than the desired
result and also was unable to create the /dev directory.


The /dev directory is a pseudo-directory created on-the-fly by the
Cygwin DLL.


I was really curious about the implications of that so had some further
questions, but I am going to drop those questions because they are a
distraction from the principal point I want to make.

In sum, if any Cygwin developer here feels moved to help debug Wine so
that the Cygwin install works properly on it, the best thing you could
do would be to follow the steps I detailed at at
) with Wine-1.6-rc4
patched with Andrey Turkin's patch, and with Cygwin updated with the
recent snapshot cygwin1.dll that contains the fork fix.  Then run that
exact same setup.exe procedure (with the fork fix applied in the same
way) on Microsoft Windows.  Such direct comparisons between Wine and
Microsoft Windows results would be a great help in figuring out which
of the many error messages that show up in a fresh install of Cygwin
on Wine should actually be of concern to Wine developers.  (I cannot
do such comparisons myself because I don't have ready access to
Microsoft Windows, i.e., I have been running Linux since 1996 and my
only Windows experience is running MinGW/MSYS on Wine off and on as a
build and test platform for software for the last couple of years).

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Failure with fork() (Cygwin on Wine install now sort of works)

2013-07-05 Thread Christopher Faylor
On Fri, Jul 05, 2013 at 07:27:04PM -0700, Alan W. Irwin wrote:
>On 2013-07-05 16:48-0400 Christopher Faylor wrote:
>>On Fri, Jul 05, 2013 at 12:11:10PM -0700, Alan W.  Irwin wrote:
>>>On 2013-07-04 13:39-0700 Alan W.  Irwin wrote:
So if the consensus here after looking at the setup_install.out results
is that cygwin on Wine is more or less installed properly from these
results (except for the rename issue above which I can fix by doing
that rename manually as suggested by the error message), then the next
order of business [...]
>>>
>>>I have now looked more carefully at the setup_install.out results that
>>>are wrapped inside a tarball I attached to a previous post in this
>>>thread.  At the same time I have also looked at the resulting files in
>>>my cygwin install tree.  It turns out that because of errors the first
>>>install script created an empty /etc/fstab rather than the desired
>>>result and also was unable to create the /dev directory.
>>
>>The /dev directory is a pseudo-directory created on-the-fly by the
>>Cygwin DLL.
>
>I was really curious about the implications of that so had some further
>questions, but I am going to drop those questions because they are a
>distraction from the principal point I want to make.
>
>In sum, if any Cygwin developer here feels moved to help debug Wine so
>that the Cygwin install works properly on it, the best thing you could

I can only speak for this Cygwin developer but I have a long track
record of not wanting to involve myself in Cygwin and Wine interactions.
We stand on our head and do backflips in Cygwin code to get it to
emulate Linux behavior.  Having to do the same in another direction,
figuring out why something which works on multiple Windows platforms
does not work on a Windows emulator, is not something that I'm keen on
doing.

I'm just mentioning this in case you thought that since I have
sporadically been responding to this thread I might be interested in
joining in the discovery.  Unfortunately, I'm really not.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



SVN - Newest Version

2013-07-05 Thread Chloe

How do I install the latest SVN? I have version
$ svn --version
svn, version 1.7.8 (r1419691)
   compiled Jan 26 2013, 10:45:51
$ which svn
/usr/bin/svn

but my working copy is a newer format:

$ svn info
svn: E155021: This client is too old to work with the working copy at

I tried setup.exe and searched in
http://cygwin.mirrors.hoobly.com
http://box-soft.com
ftp://ftp.cygwinports.org/pub/cygwinports

but there were no SVN clients, just SVN utilities and converters.
http://i.imgur.com/eqF9ftM.png?1



--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: SVN - Newest Version

2013-07-05 Thread Denis Excoffier

On 2013-07-06 07:27, Chloe wrote:
> How do I install the latest SVN? I have version
> $ svn --version
> svn, version 1.7.8 (r1419691)
>   compiled Jan 26 2013, 10:45:51
> $ which svn
> /usr/bin/svn
> 
> but my working copy is a newer format:
> 
> $ svn info
> svn: E155021: This client is too old to work with the working copy at
> 
> I tried setup.exe and searched in
> http://cygwin.mirrors.hoobly.com
> http://box-soft.com
> ftp://ftp.cygwinports.org/pub/cygwinports
> 
> but there were no SVN clients, just SVN utilities and converters.
> http://i.imgur.com/eqF9ftM.png?1
> 
Did you try with the "subversion" keyword?
You should obtain subversion-1.8.0 which is what you seem to need.

Regards,

Denis Excoffier.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: SVN - Newest Version

2013-07-05 Thread David Rothenberger
On 7/5/2013 10:27 PM, Chloe wrote:
> How do I install the latest SVN? I have version
> $ svn --version
> svn, version 1.7.8 (r1419691)
>compiled Jan 26 2013, 10:45:51
> $ which svn
> /usr/bin/svn

> I tried setup.exe and searched in
> http://cygwin.mirrors.hoobly.com
> http://box-soft.com
> ftp://ftp.cygwinports.org/pub/cygwinports
> 
> but there were no SVN clients, just SVN utilities and converters.
> http://i.imgur.com/eqF9ftM.png?1

The latest version is 1.8.0 and the package name is subversion. It's
available on the hoobly.com mirror.

If you had Subversion installed through setup before, you should be able
to simply start setup and keep clicking Next to update all your
packages, including Subversion. You might want to click on the "View"
button at the top-right until it says Pending, though, to see exactly
what it will install.

-- 
David Rothenberger    daver...@acm.org

Peers's Law:
The solution to a problem changes the nature of the problem.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple