Setup and Mintty
Hi Andy, Hi others, the latest setup sources implement the mintty desktop and start menu shortcuts. So, afaics, if you would just change the mintty package so that it doesn't install its own shortcuts, we could update setup on sourceware to the new version. Is there anything else missing? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
[RFU] autossh-1.4c-1
Please upload, including setup.hint which has changed. Please remove version 1.4a-1, leaving 1.4b-1 as previous. Thanks, Andrew. wget \ http://home.comcast.net/~andrex2/cygwin/autossh/setup.hint \ http://home.comcast.net/~andrex2/cygwin/autossh/autossh-1.4c-1.tar.bz2 \ http://home.comcast.net/~andrex2/cygwin/autossh/autossh-1.4c-1-src.tar.bz2
Re: [RFU] autossh-1.4c-1
On Nov 17 12:22, Andrew Schulman wrote: Please upload, including setup.hint which has changed. Please remove version 1.4a-1, leaving 1.4b-1 as previous. Thanks, Andrew. wget \ http://home.comcast.net/~andrex2/cygwin/autossh/setup.hint \ http://home.comcast.net/~andrex2/cygwin/autossh/autossh-1.4c-1.tar.bz2 \ http://home.comcast.net/~andrex2/cygwin/autossh/autossh-1.4c-1-src.tar.bz2 Done. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
[ITP] GNOME 3.2 dependencies
In order to update the GNOME libraries currently in the distro, I need to add the following packages: dconf (for gtk3) font-cantarell-otf (for gnome-themes-standard) glib2.0-networking (for libsoup2.4) gnome-doc-utils (for gnome-common) gnome-themes-standard (replaces gnome-themes) gsettings-desktop-schemas (for glib2.0) gtk3 (parallel to gtk2.0) itstool (for yelp-tools, below) libcanberra (for libgnome2) libdatrie (for libthai) libthai (for pango1.0) p11-kit (for gnome-keyring) vala (build-time dependency of dconf) yelp-tools (for gnome-common) yelp-xsl (for yelp-tools) All of these are in the latest releases of both Fedora and Ubuntu. Therefore, I am treating these as pre-approved per this message[1] and will proceed with the upload early next week. Yaakov Cygwin/X [1] http://cygwin.com/ml/cygwin-apps/2011-11/msg00025.html
Re: Setup and Mintty
On 17 November 2011 17:17, Corinna Vinschen wrote: the latest setup sources implement the mintty desktop and start menu shortcuts. So, afaics, if you would just change the mintty package so that it doesn't install its own shortcuts, we could update setup on sourceware to the new version. A shortcut-less mintty package is here: http://mintty.googlecode.com/files/mintty-1.0.1-2.tar.bz2 http://mintty.googlecode.com/files/mintty-1.0.1-2-src.tar.bz2 http://mintty.googlecode.com/svn/tags/1.0.1-2/cygport/setup.hint As I'd mentioned before, I think the changeover needs to go like this: 1. Add Base category to mintty's setup.hint. 2. Wait a day for mirrors to catch up. 3. Upload new setup.exe. 4. Upload shortcut-less mintty package. Without step 2, setup.exe might end up creating shortcuts to a non-existent mintty.exe. Is there anything else missing? I suspect the manual and FAQ need a few tweaks. Andy
src/winsup/cygwin ChangeLog shared.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-11-17 22:08:14 Modified files: winsup/cygwin : ChangeLog shared.cc Log message: * shared.cc (shared_info::create): Open global shared data section non-inheritable to avoid accumulating stray handles in child processes. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5559r2=1.5560 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/shared.cc.diff?cvsroot=srcr1=1.149r2=1.150
Changed timestamp in setup-legacy.ini
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. (Oh no - hate odd-numbered timestamps.) Fergus ~ -- 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: Rolling back to 1.6.x Subversion
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 must remain on such an old release of subversion? Consider users who depend on clients (SVNKit) that don't yet have 1.7 native support (i.e. Subclipse). We have to stay on 1.6 until ALL our clients support 1.7 due to the working copy restructuring. 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 to mind. I've certainly seen problems with CVS: Windows CVS clients often convert to Windows line endings on checkout, whereas Cygwin CVS doesn't, so if you check out with one and then do a 'cvs diff' with the other, it says that every line has changed. Andy -- 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: Changed timestamp in setup-legacy.ini
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 there any change in the legacy provision. My fault. Instead of copying a file I moved it. When I realized the mistake, I copied it back. That's why the timestamp changed. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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: filename with HASH
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 test# a $ lynx -dump test# a Looking up test Making HTTP connection to test Alert!: Unable to connect to remote host. lynx: Can't access startfile http://test/#%20a A # marks a separator in a URL between the URI part and the anchor within the page to load up the display at. I think lynx is applying the same syntax to local file URLs; for example, if you have a local file index.html, you can append any arbitrary # anchor to it: $ wget 'http://www.bbc.co.uk/' --2011-11-17 09:47:02-- http://www.bbc.co.uk/ Resolving www.bbc.co.uk (www.bbc.co.uk)... 212.58.246.94 Connecting to www.bbc.co.uk (www.bbc.co.uk)|212.58.246.94|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 135886 (133K) [text/html] Saving to: `index.html' 100%[==] 135,886 446K/s in 0.3s 2011-11-17 09:47:03 (446 KB/s) - `index.html' saved [135886/135886] $ ls index* index.html $ lynx -dump index.html#foobar #[1]A to Z [2]BBC Help [3]Terms of Use [4]British Broadcasting Corporation BBC Home [ ... snip ... ] So I think it's a limitation of the URL format that it's ambiguous between a filename with an actual # in it and a filename followed by # and an anchor, and there's probably not much lynx can do about it. Your best bet, if you absolutely have to use lynx on files with hash signs in their names, would be to use lynx's -stdin option and redirect the input from the file, so that lynx doesn't ever see the filename at all: $ lynx -dump index.html # abc Can't Access `file://localhost/tmp/lynx/index.html%20#%20abc' Alert!: Unable to access document. lynx: Can't access startfile $ lynx -stdin -dump index.html # abc #[1]A to Z [2]BBC Help [3]Terms of Use [4]British Broadcasting Corporation BBC Home [ ... snip ... ] cheers, DaveK -- 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: filename with HASH
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. lynx: Can't access startfile $ mv test # abc test# a $ lynx -dump test# a Looking up test Making HTTP connection to test Alert!: Unable to connect to remote host. lynx: Can't access startfile http://test/#%20a A # marks a separator in a URL between the URI part and the anchor within the page to load up the display at. I think lynx is applying the same syntax to local file URLs; for example, if you have a local file index.html, you can append any arbitrary # anchor to it: Apart from that, all non-graphical characters in an URL are converted to the %xx syntax. Therefore, the URL test # abc is converted to file://[$PWD]/test%20#%20abc *before* trying to find the file. So lynx tries to access the file test%20#%20abc in the current directory, which obviously doesn't exist. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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: Rolling back to 1.6.x Subversion
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 to mind. I regularly use Cygwin's SVN and Subclipse in a Windows version of Eclipse and never had any problems. I had to postpone upgrading to the Subversion 1.7 Cygwin package until Subclipse 1.8 came out, which supports the 1.7 working copy format. -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- 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: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
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 title. When I want to compile Hydra, I get this: Hubert@Hubert-PC ~ $ cd Hydra Hubert@Hubert-PC ~/Hydra $ ./configure Starting hydra auto configuration ... Checking for openssl (libssl, libcrypto, ssl.h, sha.h) ... ... found Checking for idn (libidn.so) ... ... NOT found, unicode logins and passwords will no t be supported Checking for pcre (libpcre.so, pcre.h) ... ... NOT found, server response checks wil l be less reliable Checking for Postgres (libpq.so, libpq-fe.h) ... ... NOT found, module postgres disa bled Checking for SVN (libsvn_client-1 libapr-1.so libaprutil-1.so) ... ... NOT found, mo dule svn disabled Checking for firebird (libfbclient.so) ... ... NOT found, module firebird disabled Checking for MYSQL client (libmysqlclient.so, math.h) ... ... NOT found, module Mysq l will not support version 4.x Checking for AFP (libafpclient.so) ... ... NOT found, module Apple Filing Protocol d isabled - Apple sucks anyway Checking for NCP (libncp.so / nwcalls.h) ... ... NOT found, module NCP disabled Checking for SAP/R3 (librfc/saprfc.h) ... ... NOT found, module sapr3 disabled Get it from http://www.sap.com/solutions/netweaver/linux/eval/index.asp Checking for libssh (libssh/libssh.h) ... ... NOT found, module ssh disabled Get it from http://www.libssh.org Checking for Oracle (libocci.so libclntsh.so / oci.h) ... ... NOT found, module Orac le disabled Checking for GUI req's (pkg-config, gtk+-2.0) ... ... found Hydra will be installed into .../bin of: /usr/local (change this by running ./configure --prefix=path) Writing Makefile.in ... Cygwin detected, if compilation fails just update your installation. Windres found, will attach icons to hydra cygwin executables now type make Hubert@Hubert-PC ~/Hydra $ 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: Hubert@Hubert-PC ~ $ apt-cyg find pcre Working directory is /setup Mirror is ftp://mirror.mcs.anl.gov/pub/cygwin --2011-11-16 22:31:12-- ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2 = `.listing' Resolving mirror.mcs.anl.gov (mirror.mcs.anl.gov)... 146.137.96.7, 146.137.96.15 , 2620:0:dc0:1800:214:4fff:fe7d:1b9 Connecting to mirror.mcs.anl.gov (mirror.mcs.anl.gov)|146.137.96.7|:21... connec ted. Logging in as anonymous ... Logged in! == SYST ... done.== PWD ... done. == TYPE I ... done. == CWD (1) /pub/cygwin ... done. == PASV ... done.== LIST ... done. [ = ] 1,043 --.-K/s in 0s 2011-11-16 22:31:14 (4.76 MB/s) - `.listing' saved [1043] Removed `.listing'. --2011-11-16 22:31:14-- ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2 = `setup.bz2' == CWD not required. == PASV ... done.== RETR setup.bz2 ... done. Length: 276018 (270K) 100%[==] 276,018 169K/s in 1.6s 2011-11-16 22:31:16 (169 KB/s) - `setup.bz2' saved [276018] Updated setup.ini Searching for installed packages matching pcre: libpcre-devel libpcre0 libpcrecpp-devel libpcrecpp0 pcre Searching for installable packages matching pcre: libpcre-devel libpcre0 libpcrecpp-devel libpcrecpp0 pcre pcre-devel Hubert@Hubert-PC ~ $ pcre is installed already, so I have no idea why Cygwin says it is not (I also thought I had postgres, but instead I found postgresql which seems not to be what's needed). Generally speaking, most of the packages is missing, so the compiled Hydra would lack many of its capabilities (and that I don't want). The reason for which I started looking around was to gather everything and make everything work. So that is one thing. The other one is that when I wanted to update libstdc++, in order to later work with GCC, I got this: error: Failed dependencies: /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5 libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5 libc.so.6(GLIBC_2.0) is needed by compat-libstdc++-33-3.2.3-55.fc5 libc.so.6(GLIBC_2.1) is needed by compat-libstdc++-33-3.2.3-55.fc5 libc.so.6(GLIBC_2.1.3) is needed by
Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
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/or updating libtool as said in the very title. When I want to compile Hydra, I get this: Hubert@Hubert-PC ~ $ cd Hydra Hubert@Hubert-PC ~/Hydra $ ./configure Starting hydra auto configuration ... Checking for openssl (libssl, libcrypto, ssl.h, sha.h) ... ... found Checking for idn (libidn.so) ... ... NOT found, unicode logins and passwords will no t be supported Checking for pcre (libpcre.so, pcre.h) ... ... NOT found, server response checks wil l be less reliable Checking for Postgres (libpq.so, libpq-fe.h) ... ... NOT found, module postgres disa bled Checking for SVN (libsvn_client-1 libapr-1.so libaprutil-1.so) ... ... NOT found, mo dule svn disabled Checking for firebird (libfbclient.so) ... ... NOT found, module firebird disabled Checking for MYSQL client (libmysqlclient.so, math.h) ... ... NOT found, module Mysq l will not support version 4.x Checking for AFP (libafpclient.so) ... ... NOT found, module Apple Filing Protocol d isabled - Apple sucks anyway Checking for NCP (libncp.so / nwcalls.h) ... ... NOT found, module NCP disabled Checking for SAP/R3 (librfc/saprfc.h) ... ... NOT found, module sapr3 disabled Get it from http://www.sap.com/solutions/netweaver/linux/eval/index.asp Checking for libssh (libssh/libssh.h) ... ... NOT found, module ssh disabled Get it from http://www.libssh.org Checking for Oracle (libocci.so libclntsh.so / oci.h) ... ... NOT found, module Orac le disabled Checking for GUI req's (pkg-config, gtk+-2.0) ... ... found Hydra will be installed into .../bin of: /usr/local (change this by running ./configure --prefix=path) Writing Makefile.in ... Cygwin detected, if compilation fails just update your installation. Windres found, will attach icons to hydra cygwin executables now type make Hubert@Hubert-PC ~/Hydra $ 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: Hubert@Hubert-PC ~ $ apt-cyg find pcre Working directory is /setup Mirror is ftp://mirror.mcs.anl.gov/pub/cygwin --2011-11-16 22:31:12-- ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2 = `.listing' Resolving mirror.mcs.anl.gov (mirror.mcs.anl.gov)... 146.137.96.7, 146.137.96.15 , 2620:0:dc0:1800:214:4fff:fe7d:1b9 Connecting to mirror.mcs.anl.gov (mirror.mcs.anl.gov)|146.137.96.7|:21... connec ted. Logging in as anonymous ... Logged in! == SYST ... done.== PWD ... done. == TYPE I ... done. == CWD (1) /pub/cygwin ... done. == PASV ... done.== LIST ... done. [=] 1,043 --.-K/s in 0s 2011-11-16 22:31:14 (4.76 MB/s) - `.listing' saved [1043] Removed `.listing'. --2011-11-16 22:31:14-- ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2 = `setup.bz2' == CWD not required. == PASV ... done.== RETR setup.bz2 ... done. Length: 276018 (270K) 100%[==] 276,018 169K/s in 1.6s 2011-11-16 22:31:16 (169 KB/s) - `setup.bz2' saved [276018] Updated setup.ini Searching for installed packages matching pcre: libpcre-devel libpcre0 libpcrecpp-devel libpcrecpp0 pcre Searching for installable packages matching pcre: libpcre-devel libpcre0 libpcrecpp-devel libpcrecpp0 pcre pcre-devel Hubert@Hubert-PC ~ $ pcre is installed already, so I have no idea why Cygwin says it is not (I also thought I had postgres, but instead I found postgresql which seems not to be what's needed). Generally speaking, most of the packages is missing, so the compiled Hydra would lack many of its capabilities (and that I don't want). The reason for which I started looking around was to gather everything and make everything work. So that is one thing. The other one is that when I wanted to update libstdc++, in order to later work with GCC, I got this: Dear Hubert, 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 same for libidn
Re: filename with HASH
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!: Unable to access document. lynx: Can't access startfile $ lynx -stdin -dump index.html # abc #[1]A to Z [2]BBC Help [3]Terms of Use [4]British Broadcasting Corporation BBC Home [ ... snip ... ] cheers, DaveK -- 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 =) -- View this message in context: http://old.nabble.com/filename-with-HASH-tp32858658p32861926.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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: Rolling back to 1.6.x Subversion
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 that) made me forget how often that project changes formats in the working copies and the ramifications of that behavior. On my memory, it wasn't changed even once in four years. Or all changes were transparent. The main problem with 1.7 I see myself, I described earlier: No way to tell at a glance, if the directory you're working with is versioned or not. 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. I know I remember seeing the client request to upgrade my working copies at least once before anyway. Whether or not that upgrade was required, I can't say. Regardless of the time period between minor version bumps, that rate of change in working copies seems excessive to me given the relative stability of other SCM tools, but that's just my likely ignorant opinion. ;-) Maybe like you say, the other transitions allowed for some backward compatible support. It's odd then that they wouldn't allow for that in the 1.7 client. I would expect the 1.7 client to at least support *using* existing version 1.6 working copies in order to avoid exactly this sort of interoperability issue, but it sounds like it does not. That's very unfortunate if true. If true, maybe it would make sense to allow for parallel installation of svn versions that differ by minor number and use the alternatives system to allow the user to select a particular one if they decided to install both. In other words, it would be handy to offer something like subversion16 and subversion17 packages as well as an alias package named just subversion that would pull in the latest version. That's probably more work than it's worth though given the number of sub-packages also offered with subversion. -Jeremy -- 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: Rolling back to 1.6.x Subversion
On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp jer...@bopp.net 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 anything more than the command line for svn (infrequently at that) made me forget how often that project changes formats in the working copies and the ramifications of that behavior. On my memory, it wasn't changed even once in four years. Or all changes were transparent. The main problem with 1.7 I see myself, I described earlier: No way to tell at a glance, if the directory you're working with is versioned or not. 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. I know I remember seeing the client request to upgrade my working copies at least once before anyway. Whether or not that upgrade was required, I can't say. This is all explained quite clearly in the documentation on the Subversion web site. Each minor release is allowed to change the working copy format in a non-compatible way (the lower numbered clients can't safely use it). This simplifies the development of Subversion but causes a (to me at least) very minor annoyance that all clients that will use the same working copy must be at the same minor release. This, however, doesn't stop anyone else who writes Subversion clients from transparently supporting multiple client versions simultaneously (and dealing with the complexity that creates). Regardless of the time period between minor version bumps, that rate of change in working copies seems excessive to me given the relative stability of other SCM tools, but that's just my likely ignorant opinion. ;-) Maybe like you say, the other transitions allowed for some backward compatible support. It's odd then that they wouldn't allow for that in the 1.7 client. I would expect the 1.7 client to at least support *using* existing version 1.6 working copies in order to avoid exactly this sort of interoperability issue, but it sounds like it does not. That's very unfortunate if true. If true, maybe it would make sense to allow for parallel installation of svn versions that differ by minor number and use the alternatives system to allow the user to select a particular one if they decided to install both. In other words, it would be handy to offer something like subversion16 and subversion17 packages as well as an alias package named just subversion that would pull in the latest version. That's probably more work than it's worth though given the number of sub-packages also offered with subversion. -Jeremy -- 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 -- 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: Rolling back to 1.6.x Subversion
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 endings are two possible trouble spots that come to mind. I regularly use Cygwin's SVN and Subclipse in a Windows version of Eclipse and never had any problems. I had to postpone upgrading to the Subversion 1.7 Cygwin package until Subclipse 1.8 came out, which supports the 1.7 working copy format. One of the really smart things that the SVN project has done is insulate the working copy from most of the horrors of line ending differences. The administrative files appear to either have a strict line ending definition for all platforms or (more likely) clients are expected to be flexible regarding line ending handling within the files. The use of the svn:eol-style property on source files allows for a great deal of flexibility regarding management of line endings within the working copy. Ultimately, any problems boil down to the text editors in use and not the various SVN clients. As far as I can see, only the combination of setting svn:eol-style to native and using a crummy text editor could expose unexpected problems when mixing Cygwin and Windows SVN clients within a single working copy. Those problems would really only be in the text editor and not SVN however since the text editor could receive a file with unsupported line endings if the Cygwin client checked the file out. Either SVN client would do the right thing with the file upon commit regardless of the line endings it ended up having after editing. There can't be very many users out there mixing both Cygwin and Windows SVN clients with a text editor that completely chokes on Unix line endings. :-) I've been really impressed with how gracefully SVN handles this whole line ending issue. -Jeremy -- 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: Rolling back to 1.6.x Subversion
On 11/17/2011 10:09, Jon Clugston wrote: On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp jer...@bopp.net 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. I know I remember seeing the client request to upgrade my working copies at least once before anyway. Whether or not that upgrade was required, I can't say. This is all explained quite clearly in the documentation on the Subversion web site. Each minor release is allowed to change the working copy format in a non-compatible way (the lower numbered clients can't safely use it). This simplifies the development of Subversion but causes a (to me at least) very minor annoyance that all clients that will use the same working copy must be at the same minor release. This, however, doesn't stop anyone else who writes Subversion clients from transparently supporting multiple client versions simultaneously (and dealing with the complexity that creates). 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 version back in order to ease interoperability between SVN client implementations. I could see that the new clients wouldn't *create* older version working copies in order to encourage adoption of the changes, but it wouldn't seem too hard on the face of it to keep around a compatibility layer from the last minor version in order to *use* an older working copy. It's the maintainers' decision how they build their project, of course. I just find this aspect surprising. -Jeremy -- 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: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
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 pcre Searching for installable packages matching pcre: libpcre-devel libpcre0 libpcrecpp-devel libpcrecpp0 pcre pcre-devel Hubert@Hubert-PC ~ $ pcre is installed already, I think you need pcre-devel if you're looking to compile stuff that depends on it... -- WBR, Andrey Repin (anrdae...@freemail.ru) 17.11.2011, 22:47 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: Rolling back to 1.6.x Subversion
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, as you pointed out, they all must be of the same version. I've always been wary of that due to fear of subtle differences in working copy format. Working copy format is dictated by the Subversion client layer http://svnbook.red-bean.com/en/1.7/svn.developer.layerlib.html#svn.developer.layerlib.client not by a program or moon phase. Character encoding and line endings are two possible trouble spots that come to mind. Subversion on inside using UTF-8. But this could be a problem when dealing with files outside Subversion. I've certainly seen problems with CVS: Windows CVS clients often convert to Windows line endings on checkout, whereas Cygwin CVS doesn't, so if you check out with one and then do a 'cvs diff' with the other, it says that every line has changed. This could only happen, if you intentionally set svn:eol-style to native. Otherwise, it will preserve line endings, or even convert them to the desired format upon submission. -- WBR, Andrey Repin (anrdae...@freemail.ru) 17.11.2011, 22:52 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: Rolling back to 1.6.x Subversion
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 version back in order to ease interoperability between SVN client implementations. Unfortunatelly, changes in WC format for 1.7 was QUITE drastic... As said, you can find more info on http://subversion.apache.org/ This is the wrong mailing list to discuss them. I could see that the new clients wouldn't *create* older version working copies in order to encourage adoption of the changes, but it wouldn't seem too hard on the face of it to keep around a compatibility layer from the last minor version in order to *use* an older working copy. It's the maintainers' decision how they build their project, of course. I just find this aspect surprising. -- WBR, Andrey Repin (anrdae...@freemail.ru) 17.11.2011, 22:50 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: Rolling back to 1.6.x Subversion
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 them. Running that command fixed the symptom. Does this not work for you, or is this what you mean by checking them out anew? Or if you want to tell at a glance, if a directory you're working with is a versioned one... which is not possible for 1.17 :/ $ ls -d .svn -- 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: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
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 same for libidn /usr/bin/cygidn-11.dll libpq /usr/bin/cygpq.dll and so on. These are upstream bugs in configure, looking for the lib is wrong as different platforms have different conventions. They should only look for the header. Well, they could look for the lib too, as long as they used the correct autoconf macro (AC_CHECK_LIB or AC_SEARCH_LIB) to do so. Rather than try searching in arbitrary and unknown places for unknown file names, that just tries running a compile with the relevant -l flag and seeing if it succeeds - which for the purposes of the build is more definitively accurate anyway. cheers, DaveK -- 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: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
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 the test and leave only the check for pcre.h same for libidn /usr/bin/cygidn-11.dll libpq /usr/bin/cygpq.dll and so on. These are upstream bugs in configure, looking for the lib is wrong as different platforms have different conventions. They should only look for the header. Well, they could look for the lib too, as long as they used the correct autoconf macro (AC_CHECK_LIB or AC_SEARCH_LIB) to do so. Whoops, no they can't. The hydra configure script isn't from autconf at all; it's just hand-written. Well, at least it serves as an object lesson in why you shouldn't do that (see also: reinventing the wheel, NIH syndrome). cheers, DaveK -- 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
[ANNOUNCEMENT] Updated: {gd/libgd2/libgd-devel}-2.0.36RC1-12: An open source code library for the dynamic creation of images.
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 list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
[ANNOUNCEMENT] Updated: {gnutls/libgnutls26/libgnutls-devel}-2.12.14-1: Library implementing TLS 1.0 and SSL 3.0 protocols
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 when the provided buffer is not enough. ** API and ABI modifications: No changes since last version. Version 2.12.13 (released 2011-11-07) ** minitasn1: Upgraded to libtasn1 version 2.10. ** libgnutls: Fixed possible buffer overflow in gnutls_session_get_data(). Reported and fix by Alban Crequy. ** API and ABI modifications: No changes since last version. Version 2.12.12 (released 2011-10-20) ** gnulib: updated ** libgnutls: Fixes to enable external signing callback to operate with TLS 1.2. ** API and ABI modifications: No changes since last version. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
[ANNOUNCEMENT] Updated: {liblzo2/liblzo2_2/liblzo2-devel}-2.06-1: A data compression library which is suitable for data de-/compression in real-time
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. * Fixed overly strict malloc() misalignment check in examples. Changes in 2.05 (23 Apr 2011) * Converted the configure system to non-recursive Automake. * Applied some overdue speed optimizations for modern x86/x64 architectures and current compilers like gcc 4.6 and MSVC 2010. Changes in 2.04 (31 Oct 2010) * Fixed a gcc-4.5 aliasing issue in lzo_init(). * Updated the configure system. * Assorted cleanups. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
[ANNOUNCEMENT] Updated: multitail-5.2.8-1: View one or multiple files like tail but with multiple windows.
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 unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Perl not completely downloading for cygwin
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 Windows versions of perl on here (ActiveState and Strawberry), but I want this one mostly so that I can just run `ack' with other unix-like tools on my windows box. Does anybody know if there is a known issue with this? Thanks, Matt -- 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: Rolling back to 1.6.x Subversion
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 running svn upgrade with current one. After I got svn 1.7 via setup.exe, svn commands began failing in preexisting checkout directories, telling me I needed to svn upgrade them. Running that command fixed the symptom. Does this not work for you, or is this what you mean by checking them out anew? Or if you want to tell at a glance, if a directory you're working with is a versioned one... which is not possible for 1.17 :/ $ ls -d .svn 1.7 working copy do not have .svn dirs in nested directories. http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng -- WBR, Andrey Repin (anrdae...@freemail.ru) 18.11.2011, 02:24 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: [ANNOUNCEMENT] Updated: multitail-5.2.8-1: View one or multiple files like tail but with multiple windows.
' Please Unsubsribe My Name ' John Boyd On Thu, Nov 17, 2011 at 12:09 PM, Dr. Volker Zell dr.volker.z...@oracle.com 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: === o No NEWS available CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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 -- John Boyd -- 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: Rolling back to 1.6.x Subversion
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, before running svn upgrade with current one. I've done three successful tree upgrades with just an svn upgrade. Perhaps the cleanup is only needed in uncommon cases? $ ls -d .svn 1.7 working copy do not have .svn dirs in nested directories. http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng Sorry, I remembered that too late. How about svn st -q .? -- 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
Updated: {gd/libgd2/libgd-devel}-2.0.36RC1-12: An open source code library for the dynamic creation of images.
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 list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: {gnutls/libgnutls26/libgnutls-devel}-2.12.14-1: Library implementing TLS 1.0 and SSL 3.0 protocols
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 when the provided buffer is not enough. ** API and ABI modifications: No changes since last version. Version 2.12.13 (released 2011-11-07) ** minitasn1: Upgraded to libtasn1 version 2.10. ** libgnutls: Fixed possible buffer overflow in gnutls_session_get_data(). Reported and fix by Alban Crequy. ** API and ABI modifications: No changes since last version. Version 2.12.12 (released 2011-10-20) ** gnulib: updated ** libgnutls: Fixes to enable external signing callback to operate with TLS 1.2. ** API and ABI modifications: No changes since last version. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: gnubg-0.90.0-3: A backgammon player and analysis tool.
Hi A new version of 'gnubg' has been uploaded to a server near you. o Update to latest nightly build o Build for cygwin 1.7.9 with gcc-4.5.3 gnubg NEWS: === o There's no official NEWS file so you have to read the ChangeLog file CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: {libidn/libidn11/libidn-devel}-1.22-1: International Domain Name library
Hi New versions of 'libidn/libidn11/libidn-devel' have been uploaded to a server near you. o Update to latest upstream release o Build for cygwin 1.7.1 with gcc-4 libidn NEWS: === * Version 1.22 (released 2011-05-04) [stable] ** libidn: Add -liconv as static library requirement in libidn.pc, for MinGW. Reported by Volker Grabsch v...@notjusthosting.com. ** libidn: Fix memory leak in idna_to_ascii_4z when idna_to_ascii_4i fails. Reported by and tiny patch from Olga Limburg olimb...@gmail.com. ** libidn: Ran clang-analyze on the code. Fixed some dead assignments/initializations. ** build: Really distribute win32/libidn4win.mk. ** API and ABI is backwards compatible with the previous version. * Version 1.21 (released 2011-04-24) [stable] ** build/gettext: Demand gettext = 0.18.1 in order to get newer M4 files. The old M4 files associated with 0.17 caused problems on Solaris, hopefully now fixed. Reported by Dagobert Michelsen d...@opencsw.org in http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/25522. ** build: Improve MinGW cross-compile makefile, see win32/libidn4win.mk. ** build: Visual Studio files fixed to define LIBIDN_BUILDING. Tiny patch from Waqas Hussain waqa...@gmail.com. ** API and ABI is backwards compatible with the previous version. * Version 1.20 (released 2011-03-01) [stable] ** libidn: Fix bug in ToUnicode to compare 'xn--' case-insensitively. The problem is typically noticed when an upper ACE case string is converted to Unicode. Before, this would return the input rather than converting the ACE form to Unicode. Reported by Stepan Golosunov ste...@golosunov.pp.ru in http://bugs.debian.org/610617. ** tests: Added self-test tst_idna3 to catch any regression of problem above. ** idn: Only print copyright and license blurb when used interactively. Reported by Andrew O. Shadoura bugzi...@tut.by and Roman Mamedov r...@romanrm.ru in http://bugs.debian.org/615947 and http://bugs.debian.org/615949 respectively. ** Update gnulib files and translations. ** API and ABI is backwards compatible with the previous version. * Version 1.19 (released 2010-05-22) [stable] ** doc: Typo fixes. Added PDF version of API reference manual. See doc/reference/libidn.pdf. ** build: Update gnulib files. ** build: Use valgrind -q to reduce verbosity. ** API and ABI is backwards compatible with the previous version. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: {liblzo2/liblzo2_2/liblzo2-devel}-2.06-1: A data compression library which is suitable for data de-/compression in real-time
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. * Fixed overly strict malloc() misalignment check in examples. Changes in 2.05 (23 Apr 2011) * Converted the configure system to non-recursive Automake. * Applied some overdue speed optimizations for modern x86/x64 architectures and current compilers like gcc 4.6 and MSVC 2010. Changes in 2.04 (31 Oct 2010) * Fixed a gcc-4.5 aliasing issue in lzo_init(). * Updated the configure system. * Assorted cleanups. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: multitail-5.2.8-1: View one or multiple files like tail but with multiple windows.
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 unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
