Changed timestamp in setup-legacy.ini

2011-11-17 Thread Fergus
Why did the timestamp in setup-legacy.ini change sometime over the last 24H? NEW setup-timestamp: 1321435813 OLD setup-timestamp: 1291702302 Lately this occurs only when setup.exe=setup-legacy.exe alters; but this has not happened (yet, anyway) and nor is there any change in the legacy provision

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Andy Koppe
On 16 November 2011 23:06, Jim Garrison wrote: >> -Original Message- >> On Behalf Of Jeremy Bopp >> Sent: Wednesday, November 16, 2011 9:18 AM >> Subject: Re: Rolling back to 1.6.x Subversion >> >> That whole process is going to be unsupported here though, so is there >> some reason you mus

Re: Changed timestamp in setup-legacy.ini

2011-11-17 Thread Corinna Vinschen
On Nov 17 08:46, Fergus wrote: > Why did the timestamp in setup-legacy.ini change sometime over the last 24H? > NEW setup-timestamp: 1321435813 > OLD setup-timestamp: 1291702302 > Lately this occurs only when setup.exe=setup-legacy.exe alters; but > this has not happened (yet, anyway) and nor is th

Re: filename with HASH

2011-11-17 Thread Dave Korn
On 17/11/2011 00:29, pen wrote: > Few more tests: seems lynx dont like # > > $ mv "test bay#, wwid" "test # abc" > $ lynx -dump "test # abc" > > Can't Access `file://localhost/cygdrive/e/test%20#%20abc' > Alert!: Unable to access document. > > lynx: Can't access startfile > > $ mv "test # abc"

Re: filename with HASH

2011-11-17 Thread Corinna Vinschen
On Nov 17 09:56, Dave Korn wrote: > On 17/11/2011 00:29, pen wrote: > > Few more tests: seems lynx dont like # > > > > $ mv "test bay#, wwid" "test # abc" > > $ lynx -dump "test # abc" > > > > Can't Access `file://localhost/cygdrive/e/test%20#%20abc' > > Alert!: Unable to access document. > > >

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Csaba Raduly
On 11/17/11, Andy Koppe wrote: > Can one use different svn clients on the same working copy, even if > they are the same version? I've always been wary of that due to fear > of subtle differences in working copy format. Character encoding and > line endings are two possible trouble spots that come

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

2011-11-17 Thread viper_88
If only compiling and installing Hydra in real life was so easy, I wouldn't be writing about things that don't work. First things first, though... Let me tell you, from begining to end, what I have got through first to end up with having problems using and/or updating libtool as said in the very t

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

2011-11-17 Thread marco atzeri
On 11/17/2011 1:15 PM, viper_88 wrote: If only compiling and installing Hydra in real life was so easy, I wouldn't be writing about things that don't work. First things first, though... Let me tell you, from begining to end, what I have got through first to end up with having problems using and/

Re: filename with HASH

2011-11-17 Thread pen
Thanks Dave. That was fantastic!!! Now my scripts will become much lighter. =) Dave Korn-9 wrote: > > On 17/11/2011 00:29, pen wrote: >> Few more tests: seems lynx dont like # >> >> $ lynx -dump "index.html # abc" >> >> Can't Access `file://localhost/tmp/lynx/index.html%20#%20abc' >> Alert!:

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Jeremy Bopp
On 11/17/2011 01:39, Andrey Repin wrote: > Greetings, Jeremy Bopp! > >> All I really wanted to know was why it was important to hang back from the >> latest available version when getting the older one was less than trivial. >> Not using anything more than the command line for svn (infrequently at

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Jon Clugston
On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp wrote: > On 11/17/2011 01:39, Andrey Repin wrote: >> Greetings, Jeremy Bopp! >> >>> All I really wanted to know was why it was important to hang back from the >>> latest available version when getting the older one was less than trivial. >>> Not using

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Jeremy Bopp
On 11/17/2011 05:12, Csaba Raduly wrote: > On 11/17/11, Andy Koppe wrote: >> Can one use different svn clients on the same working copy, even if >> they are the same version? I've always been wary of that due to fear >> of subtle differences in working copy format. Character encoding and >> line e

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Jeremy Bopp
On 11/17/2011 10:09, Jon Clugston wrote: > On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp wrote: >> I want to think that they only change the working copy format when the >> minor version changes, but I also think that they have done that with >> every minor version transition since at least 1.4.

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

2011-11-17 Thread Andrey Repin
Greetings, viper_88! > As you can easily see, most of the stuff is missing. It's a bit odd, though, > since when I look for, say, pcre (which I definitely had installed), I get > this: > Searching for installed packages matching pcre: > libpcre-devel > libpcre0 > libpcrecpp-devel > libpcrecpp0 >

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Andrey Repin
Greetings, Andy Koppe! > Can one use different svn clients on the same working copy, even if > they are the same version? You can even use them (literally) simultaneously. Subversion introduced an appropriate locking mechanics to ensure as much as possible that all transactions are atomic. But, a

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Andrey Repin
Greetings, Jeremy Bopp! > Thank you for confirming my memory regarding these format changes. > Still, while it makes sense for the project to make backward > incompatible changes at times, it still seems odd that the new clients > wouldn't support using the working copies from at least 1 minor ver

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Warren Young
On 11/16/2011 3:20 PM, Andrey Repin wrote: it's a release you need to migrate your working copies to 1.17 without checking them out anew. Are you sure? After I got svn 1.7 via setup.exe, svn commands began failing in preexisting checkout directories, telling me I needed to "svn upgrade" the

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

2011-11-17 Thread Dave Korn
On 17/11/2011 13:00, marco atzeri wrote: > the problem is that the configure scripts incorrectly looks for > libpcre.so that on cygwin is called differently: > > /usr/bin/cygpcre-0.dll > > so you need to modify the configure accordingly or > remove the test and leave only the check for "pcre.h"

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

2011-11-17 Thread Dave Korn
On 17/11/2011 20:33, Dave Korn wrote: > On 17/11/2011 13:00, marco atzeri wrote: > >> the problem is that the configure scripts incorrectly looks for >> libpcre.so that on cygwin is called differently: >> >> /usr/bin/cygpcre-0.dll >> >> so you need to modify the configure accordingly or >> remove

[ANNOUNCEMENT] Updated: {gd/libgd2/libgd-devel}-2.0.36RC1-12: An open source code library for the dynamic creation of images.

2011-11-17 Thread Dr. Volker Zell
Hi New versions of 'gd/libgd2/libgd-devel' have been uploaded to a server near you. o Build for cygwin 1.7.9 with gcc-4.5.3 o Linked against libjpeg8 and libpng14 CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing

[ANNOUNCEMENT] Updated: {gnutls/libgnutls26/libgnutls-devel}-2.12.14-1: Library implementing TLS 1.0 and SSL 3.0 protocols

2011-11-17 Thread dr . volker . zell
Hi New versions of 'gnutls/libgnutls26/libgnutls-devel' have been uploaded to a server near you. o Update to latest upstream version gnutls NEWS: === Version 2.12.14 (released 2011-11-08) ** libgnutls: Corrected fix in gnutls_session_get_data() to report the actual session size

[ANNOUNCEMENT] Updated: {liblzo2/liblzo2_2/liblzo2-devel}-2.06-1: A data compression library which is suitable for data de-/compression in real-time

2011-11-17 Thread Dr. Volker Zell
Hi New versions of 'liblzo2/liblzo2_2/liblzo2-devel' have been uploaded to a server near you. o Updated to latest upstream release o Rebuild for cygwin 1.7.9 with gcc-4.5.3 liblzo2 NEWS: === Changes in 2.06 (12 Aug 2011) * Some minor optimizations for big-endian architectures.

[ANNOUNCEMENT] Updated: multitail-5.2.8-1: View one or multiple files like tail but with multiple windows.

2011-11-17 Thread Dr. Volker Zell
Hi A new version of 'multitail' has been uploaded to a server near you. o Updated to latest upstream release o Build for cygwin 1.7.9 with gcc-4.5.3 multitail NEWS: === o No NEWS available CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubs

Perl not completely downloading for cygwin

2011-11-17 Thread matt.pettis
Hi, I am trying to download perl 5.10.1-5 for cygwin through setup.exe, but it usually ends up at around 99% complete and then throws the error "download incomplete.  Try again?"  I've tried a couple of different http repositories, but I get the same error on the ones I tried.  I do have Window

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Andrey Repin
Greetings, Warren Young! > On 11/16/2011 3:20 PM, Andrey Repin wrote: >> >> it's a release you need to migrate your working copies >> to 1.17 without checking them out anew. > Are you sure? As far as I understand the release notes, you need to run "svn cleanup" with earlier version, before runni

Re: [ANNOUNCEMENT] Updated: multitail-5.2.8-1: View one or multiple files like tail but with multiple windows.

2011-11-17 Thread J Boyd
' Please Unsubsribe My Name ' John Boyd On Thu, Nov 17, 2011 at 12:09 PM, Dr. Volker Zell wrote: > Hi > > A new version of 'multitail' has been uploaded to a server near you. > >  o Updated to latest upstream release >  o Build for cygwin 1.7.9 with gcc-4.5.3 > > > multitail NEWS: > ===

Re: Rolling back to 1.6.x Subversion

2011-11-17 Thread Warren Young
On 11/17/2011 3:42 PM, Andrey Repin wrote: On 11/16/2011 3:20 PM, Andrey Repin wrote: it's a release you need to migrate your working copies to 1.17 without checking them out anew. Are you sure? As far as I understand the release notes, you need to run "svn cleanup" with earlier version, b