Please upload: ddrescue 1.6-1
Please upload: http://franke.dvrdns.org/cygwin/release/ddrescue/ddrescue-1.6-1.tar.bz2 http://franke.dvrdns.org/cygwin/release/ddrescue/ddrescue-1.6-1-src.tar.bz2 setup.hint is unchanged. Christian
Re: Please upload: ddrescue 1.6-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christian Franke on 11/16/2007 2:39 PM: Please upload: http://franke.dvrdns.org/cygwin/release/ddrescue/ddrescue-1.6-1.tar.bz2 http://franke.dvrdns.org/cygwin/release/ddrescue/ddrescue-1.6-1-src.tar.bz2 Uploaded, leaving 1.4-1 as previous. Do you want 1.3-1 deleted? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnhJ84KuGfSFAYARAuI4AJ0dtkNZXhAzRLa+BRUECau0eB9eyACg2SDm JDaTH8fc2SOEjG/9SsdIVQU= =Swux -END PGP SIGNATURE-
Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6
Hi all: I recently hit the foreign keyboard problem described in section 4.1.6 of the Cygwin/X FAQ. That is, I started with: $ setxkbmap.exe de -model pc105 Couldn't interpret _XKB_RULES_NAMES property [...] and then I tried what the FAQ said, but I got the following error: $ xkbcomp -w 3 -xkm -m de /etc/X11/xkb/keymap/xfree86 localhost:0.0 Error:Can't find file xfree86 for keycodes include Exiting Abandoning keycodes file it I googled for it, and after a while, I found the solution: I had the same problem... By copying the /etc/X11/xkb directory into /usr/X11R6/lib/X11/xkb It seems to work pretty well now... (just in case, I renamed the existing file C:\cygwin\usr\X11R6\lib\X11\xkb.lnk beforehand to xkb.bak.lnk before copying over) I don't know enough about Cygwin to realise how and why that is; all I know is, when I copy that directory, my German keyboard works fine in my X apps. I'm not sure if it's a bug that could be fixed, but the FAQ entry could be updated to help people like me. Who's maintaining the FAQ? Many thanks, Ruben __ Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6
[EMAIL PROTECTED] wrote: Hi all: I recently hit the foreign keyboard problem described in section 4.1.6 of the Cygwin/X FAQ. That is, I started with: $ setxkbmap.exe de -model pc105 Couldn't interpret _XKB_RULES_NAMES property [...] and then I tried what the FAQ said, but I got the following error: $ xkbcomp -w 3 -xkm -m de /etc/X11/xkb/keymap/xfree86 localhost:0.0 Error:Can't find file xfree86 for keycodes include Exiting Abandoning keycodes file it I googled for it, and after a while, I found the solution: I had the same problem... By copying the /etc/X11/xkb directory into /usr/X11R6/lib/X11/xkb It seems to work pretty well now... (just in case, I renamed the existing file C:\cygwin\usr\X11R6\lib\X11\xkb.lnk beforehand to xkb.bak.lnk before copying over) I don't know enough about Cygwin to realise how and why that is; all I know is, when I copy that directory, my German keyboard works fine in my X apps. http://cygwin.com/acronyms/#WJFFM I'm not sure if it's a bug that could be fixed, but the FAQ entry could be updated to help people like me. Who's maintaining the FAQ? No one at the moment. :-( Would you be interested in taking it up? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: [Patch] Encode invalid chars in /proc/registry entries
Hi Christian,
On Nov 15 22:56, Christian Franke wrote:
Registry key and value names may contain chars which are not allowed within
file names ('/', '\', :). But Cygwin's /proc/registry returns these names
unchanged to the app. The obvious effect is that such entries cannot be
accessed.
But if an entry name is identical to an existing path, more interesting
results occur. Cygwin itself adds registry entries which are testcases for
this issue :-))
[...]
The attached patch encodes the critical chars with %XX to avoid such
problems.
Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not
actually tested. Therefore, no changelog provided yet.
Thanks for this patch. Apart from the missing ChangeLog I'm inclined
to apply it to the upcoming 1.5.25 release, but I don't like to have it
in HEAD as is.
The reason is that the patch introduces more usages of CYG_MAX_PATH plus
static buffers of that size. That's ok for 1.5, but that's not ok
anymore for 1.7. We're heading to support PATH_MAX = ~32K paths. The
registry also supports long paths, unfortunately with undefined max
length. The current definition in MSDN(*) is
Max name length of keys: 255 chars
Max name length of values: 16383 chars
Max tree depth: 512 levels
So, for HEAD I'd like to ask you to allow arbitrary path lengths in your
code. Personally I could live with restricting registry paths to
PATH_MAX as well.
While you're digging in registry code anyway... would you be interested
to convert the entire registry code to wide char and long path names?
I'd be glad for any help.
Corinna
(*) http://msdn2.microsoft.com/en-us/library/ms724872.aspx
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
Re: [Patch] Encode invalid chars in /proc/registry entries
On Fri, Nov 16, 2007 at 08:35:48PM +0100, Christian Franke wrote: Christopher Faylor wrote: .. Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. Thanks for this patch. Apart from the missing ChangeLog I'm inclined to apply it to the upcoming 1.5.25 release, but I don't like to have it in HEAD as is. I'm not so sure it's appropriate for either yet. Isn't it possible to use at least some of the managed mode functions which deal with munging characters to do some of encoding? It seems like the patch duplicates some of the functionality from path.cc. I realize that the registry is sort of the opposite of a managed mount but it seems like the encoding functions might be potentially used in reverse for this. I actually consulted path.cc before starting the patch but did not find any function which provides the required functionality OOTB. Therefore, I solved the tradeoff between reuse and do not change working code if you don't have time for thorough regression testing by the latter :-) I'm sorry but reuse is a fairly important concept in a project like this. The proc functions, in particular, have been prone to NIH and I don't want to see even more there if we can possibly help it. So, I'll reiterate my suggestion that you look at, e.g., mount_item::fnmunge and possibly think about generalizing it if it isn't quite up to the task. I'll also go on record as advocating that this not be part of a bugfix release. It seems too much like a last minute change to me. Getting it into cvs main, however, seems like a good idea. cgf
Re: [Patch] Encode invalid chars in /proc/registry entries
On Fri, Nov 16, 2007 at 12:09:01PM +0100, Corinna Vinschen wrote:
Hi Christian,
On Nov 15 22:56, Christian Franke wrote:
Registry key and value names may contain chars which are not allowed within
file names ('/', '\', :). But Cygwin's /proc/registry returns these names
unchanged to the app. The obvious effect is that such entries cannot be
accessed.
But if an entry name is identical to an existing path, more interesting
results occur. Cygwin itself adds registry entries which are testcases for
this issue :-))
[...]
The attached patch encodes the critical chars with %XX to avoid such
problems.
Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not
actually tested. Therefore, no changelog provided yet.
Thanks for this patch. Apart from the missing ChangeLog I'm inclined
to apply it to the upcoming 1.5.25 release, but I don't like to have it
in HEAD as is.
I'm not so sure it's appropriate for either yet.
Isn't it possible to use at least some of the managed mode functions
which deal with munging characters to do some of encoding? It seems
like the patch duplicates some of the functionality from path.cc.
I realize that the registry is sort of the opposite of a managed mount
but it seems like the encoding functions might be potentially used in
reverse for this.
cgf
Re: [Patch] Encode invalid chars in /proc/registry entries
Hi Corinna,
Corinna Vinschen wrote:
...
Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not
actually tested. Therefore, no changelog provided yet.
Thanks for this patch. Apart from the missing ChangeLog I'm inclined
to apply it to the upcoming 1.5.25 release, but I don't like to have it
in HEAD as is.
Thanks, I would appreciate to have this issue fixed in the bugfix release.
Here is a new version of the patch and a ChangeLog.
The names . and .. are now also encoded. Theses are also valid as
Key/Value Names and .. may result in infinite recursion.
The reason is that the patch introduces more usages of CYG_MAX_PATH plus
static buffers of that size. That's ok for 1.5, but that's not ok
anymore for 1.7. We're heading to support PATH_MAX = ~32K paths. The
registry also supports long paths, unfortunately with undefined max
length. The current definition in MSDN(*) is
Max name length of keys: 255 chars
Max name length of values: 16383 chars
Max tree depth: 512 levels
So, for HEAD I'd like to ask you to allow arbitrary path lengths in your
code. Personally I could live with restricting registry paths to
PATH_MAX as well.
Agree. Probably Cygwin should never descend paths that exceed PATH_MAX,
as an application using PATH_MAX may have no buffer overflow check.
While you're digging in registry code anyway... would you be interested
to convert the entire registry code to wide char and long path names?
I'd be glad for any help.
I will have a look at it, but be patient. Is current HEAD a reasonable
starting point or is there a better (more stable) snapshot?
Christian
2007-11-16 Christian Franke [EMAIL PROTECTED]
* fhandler_registry.cc (must_encode): New function.
(encode_regname): Ditto.
(decode_regname): Ditto.
(fhandler_registry::exists): Encode name before path compare.
(fhandler_registry::fstat): Pass decoded name to win32 registry call.
(fhandler_registry::readdir): Return encoded name to user.
(fhandler_registry::open): Store decoded name into value_name.
(open_key): Pass decoded name to win32 registry call.
--- cygwin-1.5.24-2.orig/winsup/cygwin/fhandler_registry.cc 2006-01-27 22:50:40.00100 +0100
+++ cygwin-1.5.24-2/winsup/cygwin/fhandler_registry.cc 2007-11-16 16:34:45.0 +0100
@@ -86,6 +86,69 @@ static const char *DEFAULT_VALUE_NAME =
static HKEY open_key (const char *name, REGSAM access, bool isValue);
+/* Return true if char must be encoded.
+ */
+static inline bool
+must_encode (char c)
+{
+ return (isdirsep (c) || c == ':' || c == '%');
+}
+
+/* Encode special chars in registry key or value name.
+ */
+static int
+encode_regname (char * dst, const char * src)
+{
+ int di = 0;
+ for (int si = 0; src[si]; si++)
+{
+ char c = src[si];
+ if (must_encode (c) ||
+ (c == '.' si == 0 (!src[1] || (src[1] == '.' !src[2]
+ {
+ if (di + 3 = CYG_MAX_PATH)
+ return ENAMETOOLONG;
+ __small_sprintf (dst + di, %%%02x, c);
+ di += 3;
+ }
+ else
+ dst[di++] = c;
+}
+ dst[di] = 0;
+ return 0;
+}
+
+/* Decode special chars in registry key or value name.
+ */
+static int
+decode_regname (char * dst, const char * src, int len = -1)
+{
+ if (len 0)
+len = strlen (src);
+ int di = 0;
+ for (int si = 0; si len; si++)
+{
+ char c = src[si];
+ if (c == '%')
+ {
+ if (si + 2 = len)
+ return EINVAL;
+ char s[] = {src[si+1], src[si+2], '\0'};
+ char *p;
+ c = strtoul (s, p, 16);
+ if (!(must_encode (c) ||
+ (c == '.' si == 0 (len == 3 || (src[3] == '.' len == 4)
+ return EINVAL;
+ dst[di++] = c;
+ si += 2;
+ }
+ else
+ dst[di++] = c;
+}
+ dst[di] = 0;
+ return 0;
+}
+
/* Returns 0 if path doesn't exist, 0 if path is a directory,
* 0 if path is a file.
*
@@ -166,8 +229,9 @@ fhandler_registry::exists ()
NULL, NULL))
|| (error == ERROR_MORE_DATA))
{
- if (pathmatch (buf, file) || (buf[0] == '\0'
- pathmatch (file, DEFAULT_VALUE_NAME)))
+ char enc_buf[CYG_MAX_PATH];
+ if ( (buf[0] == '\0' pathmatch (file, DEFAULT_VALUE_NAME))
+ || (!encode_regname (enc_buf, buf) pathmatch (enc_buf, file)))
{
file_type = -1;
goto out;
@@ -246,9 +310,11 @@ fhandler_registry::fstat (struct __stat6
while (!isdirsep (*value_name))
value_name--;
value_name++;
+ char dec_value_name[CYG_MAX_PATH];
DWORD dwSize;
- if (ERROR_SUCCESS ==
- RegQueryValueEx (hKey, value_name, NULL, NULL, NULL,
+ if (!decode_regname (dec_value_name, value_name)
+ ERROR_SUCCESS ==
+ RegQueryValueEx (hKey, dec_value_name, NULL, NULL, NULL,
dwSize))
buf-st_size = dwSize;
}
@@ -338,8 +404,8 @@ retry:
/* We get here if `buf' contains valid data. */
if (*buf == 0)
strcpy (de-d_name, DEFAULT_VALUE_NAME);
- else
-strcpy (de-d_name, buf);
+
Re: [Patch] Encode invalid chars in /proc/registry entries
Christopher Faylor wrote: .. Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. Thanks for this patch. Apart from the missing ChangeLog I'm inclined to apply it to the upcoming 1.5.25 release, but I don't like to have it in HEAD as is. I'm not so sure it's appropriate for either yet. Isn't it possible to use at least some of the managed mode functions which deal with munging characters to do some of encoding? It seems like the patch duplicates some of the functionality from path.cc. I realize that the registry is sort of the opposite of a managed mount but it seems like the encoding functions might be potentially used in reverse for this. I actually consulted path.cc before starting the patch but did not find any function which provides the required functionality OOTB. Therefore, I solved the tradeoff between reuse and do not change working code if you don't have time for thorough regression testing by the latter :-) Christian
RE: Reliable old script... - seems to be an AVS program
On 16 November 2007 09:45, Thomas Baker wrote: I uninstalled Anti-Vir [1], and the script has run hundreds of times on several different data sources with no errors yet, so this may indeed be the problem! There's another one for the list then I guess. Ouch. Nothing's worse than data loss. Question: Is the kernel itself part of one of the packages installed by setup.exe, and is it possible to use setup.exe to go back to a previous kernel (i.e., to 1.5.22) after one has updated to the most recent version? Yep. The kernel of cygwin is implemented as a DLL, /bin/cygwin1.dll, and is shipped in the cygwin setup package (along with a few essential related files). You can use setup.exe to wind it forward or back. I see there was a thread last month about AVS programs [2] but see no clear recommendations except one for Anti-Vir [3] -- the problem that is causing me problems now! -- and one recommendation for AVG [4,5]. Been running it for several years now, both free and for the past couple paid-for versions, on many and varied cygwin hosts. No problems. Did once get a false positive on a couple of dlls, but shrugs can happen to anybody; notified grisoft, fetched them back from the virus vault, next update fixed the bad detect. Thoroughly impressed by the reliability and low overhead. cheers, DaveK [*] - -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Reliable old script... - seems to be an AVS program
On Wed, Nov 14, 2007 at 06:03:42PM -0500, Larry Hall (Cygwin) wrote: These machines have an anti-virus program, but the same one I have been using for the past two or three years. The filenames either have no extension, or .txt. That's most likely the problem anyway, what happens if you turn it off? This is possible, particularly if the AV program has been updated. If so, turning it off is typically not enough to avoid the problems introduced by it though. You may need to uninstall it (and reboot) to completely rule it out. I uninstalled Anti-Vir [1], and the script has run hundreds of times on several different data sources with no errors yet, so this may indeed be the problem! One way for me to confirm that the problem is _not_ the kernel would be to update Cygwin on my laptop, which currently uses CYGWIN_NT-5.1 1.5.22(0.156/4/2) 2006-11-13 17:01 However, the laptop is currently my only reliably functioning machine, so I'm deeply reluctant to do so unless I have an easy and reliable way to go back to the kernel 1.5.22 if a problem occurs. Question: Is the kernel itself part of one of the packages installed by setup.exe, and is it possible to use setup.exe to go back to a previous kernel (i.e., to 1.5.22) after one has updated to the most recent version? I see there was a thread last month about AVS programs [2] but see no clear recommendations except one for Anti-Vir [3] -- the problem that is causing me problems now! -- and one recommendation for AVG [4,5]. Tom [1] http://www.free-av.com/ [2] http://sourceware.org/ml/cygwin/2007-10/msg00341.html [3] http://sourceware.org/ml/cygwin/2007-10/msg00342.html [4] http://sourceware.org/ml/cygwin/2007-10/msg00348.html [5] http://free.grisoft.com/ -- Tom Baker - [EMAIL PROTECTED] - [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Launching java process trouble
Jeannot Lelapin wrote: Hello Larry, Thank's dor your explanation. i read all the cygwin cron man page ( prehaps i don't how to do that ). I didn't find another explanation. Perhaps this link is more clear? http://www.adminschoice.com/docs/crontab.htm#Environment In short, you get a minimal environment with cron. If you want/need more than that, you have to make sure your crontab includes more. My guess is that you're missing CLASSPATH and perhaps other settings that you need to make your job work. Like I said though, this is not Cygwin-specific. The same holds true for cron on any platform. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Intermittent 'make' segfaults in Cygwin
Hi all, We've recently begun using Cygwin and Make to build one of our larger software products on Windows, so that we can use the same build system between win32 and the various Linux platforms. Unfortunately, on our Windows machines, we've been seeing intermittent segmentation faults in make, apparently non-reproducible. While attempts to come up with a small test case that can reproduce the problem have failed, it occurs frequently enough that a complete build of the product (taking around 3 hours or more under ideal conditions) produces two or three such failures fairly reliably, though always in different areas. Running a build with full debug output suggests that when such segfaults occur, they have something in common: Reaping winning child 0x01899388 PID 2900 Live child 0x01899770 (../intermediate/win32/release/ConformerUtilities/SOURCES.list) PID 3148 Live child 0x01899388 (../intermediate/win32/release/ConformerUtilities/IDLSOURCES.list) PID 1532 Live child 0x0189c7c0 (../intermediate/win32/release/ConformerUtilities/IPISOURCES.list) PID 2400 Live child 0x0189ad80 (../intermediate/win32/release/ConformerUtilities/RCSOURCES.list) PID 3584 Reaping winning child 0x01899388 PID 1532 Removing child 0x01899388 PID 1532 from chain. Released token for child 0x01899388 (../intermediate/win32/release/ConformerUtilities/IDLSOURCES.list). /bin/sh: line 2: 2184 Segmentation fault (core dumped) make -C ConformerUtilities build While they occur with vastly different targets each time, the common theme is that the last lines of debug output are either 'Reaping (winning|losing) child', 'Removing child from chain', or 'Released token for child'. This may, of course, be a complete red herring, but seems worth mentioning. Despite the output stating 'core dumped', there haven't been any in evidence with the current setup. Some brief testing with changed parameters suggests that the frequency of these is inversely related to the stack size set on the make.exe and bash.exe binaries -- on one machine shrinking these caused more segfaults, while increasing them to approximately double the default settings allowed two builds to complete without it. However, I'm loathe to rely on that to cover up the problem until I'm more certain it won't reoccur in the future. The same makefiles, using the same make version (3.81), work without problems on Linux (RHEL 3), leading me to believe that this is likely to be a Cygwin oddity of some sort. Given the intermittent, non-reproducible nature of this problem, we're not exactly swimming in ideas for how to attempt to solve it. Has anyone seen similar behaviour in the past, or has suggestions for where to begin investigating? This is currently a major issue for us; any help would be gratefully received. Accelrys Limited (http://www.accelrys.com) Registered office: 334 Cambridge Science Park, Cambridge, CB4 0WN, UK Registered in England: 2326316 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin install from download
On Fri, Nov 16, 2007 at 09:51:51AM -0500, [EMAIL PROTECTED] wrote: Thank you for responding but I'm not sure I understand your answer as that link doesn't appear to lead to a useful place. I have tried copying that DLL into both C:\cygwin\bin and C:\cygwin\usr\bin but that doesn't resolve the problem. Nor should it have when you reported that the DLL already existed on your system. Sorry about that. Is this a known, common problem? No. Please check out http://cygwin.com/problems.html . In particular, providing cygcheck output as described there would probably be helpful. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin install from download
Thank you for responding but I'm not sure I understand your answer as that link doesn't appear to lead to a useful place. I have tried copying that DLL into both C:\cygwin\bin and C:\cygwin\usr\bin but that doesn't resolve the problem. Is this a known, common problem? Thanks On Nov 15, 2007 12:37 PM, Thorsten Kampe [EMAIL PROTECTED] wrote: * (Thu, 15 Nov 2007 12:16:37 -0500) I've installed cygwin on a net-attached XP host with no problems and love it. I've tried downloading cygwin and installing it to an unconnect host and the install constantly fails at the end with not being able to find cygintl-8.dll. Interestingly, that dll does exist in c:\cygwin\bin. I've tried just installing the base package with all the defaults, re-installing but nothing seems to work. Is there some trick? http://cygwin.com/cgi-bin2/package-grep.cgi?grep=cygintl-8.dll -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Intermittent 'make' segfaults in Cygwin
On 16 November 2007 16:58, Stephen Bennett wrote: worth mentioning. Despite the output stating 'core dumped', there haven't been any in evidence with the current setup. Try using %CYGWIN%=error_start to get either gdb or dumper.exe attached at the exact moment of failure. Check the user guide http://cygwin.com/cygwin-ug-net/using-cygwinenv.html for full usage information. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated: unison2.13, unison2.17, unison2.27
The man page for alternatives (8) does not seem to specify the allowed range for priority values, but using 2017 for unison 2.17 and 2027 for unison 2.27 seem to upset it: ajm /usr/sbin/alternatives.exe --display unison path to alternate expected in /var/lib/alternatives/unison ajm Editing /var/lib/alternatives/unison as follows seems to fix things: ajm cat /var/lib/alternatives/unison auto /usr/bin/unison /usr/bin/unison-2.17 17 /usr/bin/unison-2.27 27 ajm /usr/sbin/alternatives.exe --display unison unison - status is auto. link currently points to /usr/bin/unison-2.27 /usr/bin/unison-2.17 - priority 17 /usr/bin/unison-2.27 - priority 27 Current `best' version is /usr/bin/unison-2.27. ajm ~ I can't reproduce this problem on my host: $ alternatives --display unison unison - status is auto. link currently points to /usr/bin/unison-2.27 /usr/bin/unison-2.13 - priority 2013 /usr/bin/unison-2.17 - priority 2017 /usr/bin/unison-2.27 - priority 2027 Current `best' version is /usr/bin/unison-2.27. $ cat /var/lib/alternatives/unison auto /usr/bin/unison /usr/bin/unison-2.13 2013 /usr/bin/unison-2.17 2017 /usr/bin/unison-2.27 2027 I also found a mixture of names - the new versions install unison symlinks, but the older versions installed unison.exe symlinks. Some of this may have been my hand edits to fix things up though. I'm not sure. At this point I recommend that you remove and reinstall all of the unison alternatives on your host, as follows: rm /var/lib/alternatives/unison for f in /etc/postinstall/unison* ; do $f ; done and see if that clears up the problem. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
posix_fallocate clarfication
Is posix_fallocate in any released version of cygwin? Or is it only in CVS? I've seen it in snapshots since August of last year but cannot successfully determine if it is in a released version or not so I'd thought I'd just ask. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: posix_fallocate clarfication
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Rob Bosch on 11/16/2007 4:18 PM: Is posix_fallocate in any released version of cygwin? Or is it only in CVS? I've seen it in snapshots since August of last year but cannot successfully determine if it is in a released version or not so I'd thought I'd just ask. It is only in CVS. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPicF84KuGfSFAYARAoMHAJ9fFMeRZNa9S4lh3GjTdG2ktjkiEACfdOmO Gz4YpSlguqvmKV/TO+9tJjQ= =PpN7 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
how to set a cygwin root
Hi I have created a cygwin environment on one host and everything is OK. When I copied the whole dir to another host, the cygwin root is switched from C:/cygwin to C:/.(The cygwin root on the original host is C;/cygwin). I don't want to reinstall a cygwin on the other host because it is difficult to set up the whole development environment again. Is there a quick way to change cygwin root dir? Thanks -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: how to set a cygwin root
On Sat, Nov 17, 2007 at 12:04:11PM +0800, Chen Yue wrote: Hi I have created a cygwin environment on one host and everything is OK. When I copied the whole dir to another host, the cygwin root is switched from C:/cygwin to C:/.(The cygwin root on the original host is C;/cygwin). I don't want to reinstall a cygwin on the other host because it is difficult to set up the whole development environment again. Is there a quick way to change cygwin root dir? Yes. Check out man mount. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: bashdb-3.1_0.09-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bashdb, 3.1_0.09-1, is available for use, replacing 3.1-0.08-1 as the current version. NEWS: = This is a new upstream release. It works with either bash 3.1 or bash 3.2. A list of changes from bashdb-3.1-0.08-1 is below; see also the /usr/share/doc/bashdb-3.1_0.09/ directory. DESCRIPTION: A bash shell script debugger, with command line, emacs, and ddd interfaces. It is possible to debug a bash shell script using 'bashdb file' or 'bash --debugger file'. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'bashdb' from the 'Devel' category. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question, the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin bashdb maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnlK84KuGfSFAYARAsp5AJ9wDmWSzXJ+/09DUbOXGmPjrv/NHwCfc0X2 iNRoM18+d+PJdczxaTMmgj8= =0KHt -END PGP SIGNATURE- Version 3.1 0.09 2007-10-27 - Add set/show trace-commands to make the same as gdb 6.6 - show commands now allows for a starting number and +, same as gdb - Reduce assumption that undefined means '' - initialize more variables. (working towards inserting set -u. - variable and tilde expansion now occurs in cd command. Note gdb does tilde expansion but not variable expansion like $HOME. - add linetrace delay - make FreeBSD tests work, cygwin signals are working so test are run there - documentation updates - emacs code improved - some installation bugs fixed - file name was sometimes incorrectly reported when debugged script set IFS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: asciidoc-8.2.4-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new version of the asciidoc package, asciidoc 8.2.4-1, is now available for download, replacing 8.2.3-1 as current. NEWS: = This is a new upstream release, with upstream changes listed below. See also the package documentation in /usr/share/doc/asciidoc-8.2.4/. DESCRIPTION: AsciiDoc is a text document format for writing short documents, articles, books and UNIX man pages. AsciiDoc files can be translated to HTML and DocBook markups using the asciidoc(1) command. AsciiDoc is highly configurable: both the AsciiDoc source file syntax and the backend output markups (which can be almost any type of SGML/XML markup) can be customized and extended by the user. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'asciidoc' from the 'Devel' category. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin asciidoc maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnk784KuGfSFAYARAvz7AJ45S0DAQ5kp59QYwcSz4mjhuoBzggCdG0go Mj9qv6snA2iOLZL2B8/FuOs= =NPwL -END PGP SIGNATURE- Version 8.2.4 (2007-11-10) -- .Additions and changes - You can now use the `lang` attribute to set the DocBook language attribute. - Attribute values can now contain attribute references. - If the `lang` attribute is defined then configuration files named like `lang-lang.conf` will be loaded automatically. - The help file name `help-lang.conf` is based on the AsciiDoc `lang` attribute, defaults to `help.conf` (English). - Admonition, figure and table captions have been factored into a predefined set of `caption_*` attributes. They only apply to directly generated (X)HTML outputs (DocBook stylesheets generate their own language specific captions based on the `lang` attribute). - Dropped platform dependent `doc/asciidoc.chm` file from distribution documentation formats. .Bug fixes - The spurious warning 'with will become a reserved keyword in Python 2.6' has been suppressed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: findutils-4.3.10-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of findutils, 4.3.10-1, is available for use, leaving 4.3.8-1 as the previous version. NEWS: = This is a new upstream release, fixing several issues as documented below, including all of the cygwin-specific patches that I was previously maintaining. The release is marked beta upstream, but the 4.3 series has, in general, been enough of an improvement over the stable 4.2 series that I have focused on 4.3 releases as the primary cygwin release. Although the news file mentions the partial addition of birthtime support, it requires rebuilding from source against a cygwin snapshot to take advantage of this feature, since birthtime will not be supported officially until cygwin 1.7.0. See also /usr/share/doc/findutils-4.3.10/. DESCRIPTION: The findutils package contains programs which will help you locate files on your system. The find utility searches through a hierarchy of directories looking for files which match a certain set of criteria (such as a filename pattern). The xargs utility builds and executes command lines from standard input arguments (usually lists of file names generated by the find command). The locate utility scans a database of filenames and displays matches. The updatedb utility builds the database for locate. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'findutils' from the 'Base' category (it should already be selected). DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin findutils maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnlb84KuGfSFAYARApXxAJ0cZ7/0il+DvezOLlZ9EplfUpNMjwCfYe++ XP484Dhyk3onVkwGigHNjzY= =GnUj -END PGP SIGNATURE- * Major changes in release 4.3.10, 2007-11-13 ** Bug Fixes #21568: findutils gnulib code does not match the date in import-gnulib.config. We now check out the gnulib code via git-cvs-pserver. * Major changes in release 4.3.9, 2007-11-11 ** Licensing Findutils version 4.3.9 is released under version 3 of the GNU General Public License. ** Bug Fixes #20834: Avoid segmentation violation for -execdir when $PATH is unset. Assume that the PATH is safe in this situation. #20310: configure uses hosts's support status for sort -z when generating the updatedb script for use on the target. This is inappropriate when cross-compiling, so avoid doing that. #20263: Compilation fix for DEC Alpha OSF/1 cc, which forbids the ordering comparison of function pointers. #20139: find -[acm]time -N (wrongly) includes files from N days ago, as well as (correctly) from less than N days ago. #20273: When xargs is successful without consuming all of stdin (for example, with the -E option), and stdin is seekable, xargs now correctly restores the file position, even on platforms where exit() does not follow the POSIX rules of doing likewise. Likewise for find (for example, with the -ok action). #20547: The version information printed by find, xargs, locate, updatedb, frcode and code now complies with the GNU Project's coding standards. #20662: Avoid memory leak in find -name and other places affected by gnulib dirname module. The leak had been present since 4.3.1. #20751: Avoid memory corruption in find -ls that has been present since 4.3.1. #20871: Assertion failure introduced in 4.3.3, when oldfind is invoked in a directory where the parent directory lacks search permission. ** Enhancements #20594: Allow fine-tuning of the default argument size used by xargs and find at ./configure time. #20688: The warning printed by -name or -iname when the pattern to match contains a slash can now be silenced by -nowarn. This warning was originally introduced unconditionally in 4.2.21. Translation of locate --limit problems is improved. POSIX will standardise -path, so the documentation no longer
[ANNOUNCEMENT] Updated: git-1.5.3.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of git, 1.5.3.5-1, has been uploaded, replacing 1.5.3.2-1 as the current version. NEWS: = This is a new upstream release. See also the package documentation in /usr/share/doc/git-1.5.3.5/, along with the attached upstream release notes. When compiled out of the box, the upstream git maintainers cater to older cygwin releases, and intentionally disable certain features that have been reported on their mailing list, even though they work with the latest cygwin. Therefore, this build turns those features back on. However, it means that this version does assume that you are not using FAT or FAT32 to hold your repositories, since they do not store file permissions very accurately. DESCRIPTION: Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source projects, most notably the Linux kernel. Git falls in the category of distributed source code management tools, similar to e.g. GNU Arch or Monotone (or BitKeeper in the proprietary world). Every Git working directory is a full-fledged repository with full revision tracking capabilities, not dependent on network access or a central server. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'git' from the 'Devel' category. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin git maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnls84KuGfSFAYARAsxHAKCLsomVifql5f5L6N/MbPjSLGC3oQCeMsw/ N0TJkgDfiIeaAd9BjBfSXW4= =DFD2 -END PGP SIGNATURE- GIT v1.5.3.5 Release Notes == Fixes since v1.5.3.4 * Comes with git-gui 0.8.4. * git-config silently ignored options after --list; now it will error out with a usage message. * git-config --file failed if the argument used a relative path as it changed directories before opening the file. * git-config --file now displays a proper error message if it cannot read the file specified on the command line. * git-config, git-diff, git-apply failed if run from a subdirectory with relative GIT_DIR and GIT_WORK_TREE set. * git-blame crashed if run during a merge conflict. * git-add -i did not handle single line hunks correctly. * git-rebase -i and git-stash apply failed if external diff drivers were used for one or more files in a commit. They now avoid calling the external diff drivers. * git-log --follow did not work unless diff generation (e.g. -p) was also requested. * git-log --follow -B did not work at all. Fixed. * git-log -M -B did not correctly handle cases of very large files being renamed and replaced by very small files in the same commit. * git-log printed extra newlines between commits when a diff was generated internally (e.g. -S or --follow) but not displayed. * git-push error message is more helpful when pushing to a repository with no matching refs and none specified. * git-push now respects + (force push) on wildcard refspecs, matching the behavior of git-fetch. * git-filter-branch now updates the working directory when it has finished filtering the current branch. * git-instaweb no longer fails on Mac OS X. * git-cvsexportcommit didn't always create new parent directories before trying to create new child directories. Fixed. * git-fetch printed a scary (but bogus) error message while fetching a tag that pointed to a tree or blob. The error did not impact correctness, only user perception. The bogus error is no longer printed. * git-ls-files --ignored did not properly descend into non-ignored directories that themselves contained ignored files if d_type was not supported by the filesystem. This bug impacted systems such as AFS. Fixed.
Re: Reliable old script... AVS problem - RESOLUTION
On Fri, Nov 16, 2007 at 10:40:27AM -, Dave Korn wrote: On 16 November 2007 09:45, Thomas Baker wrote: I uninstalled Anti-Vir [1], and the script has run hundreds of times on several different data sources with no errors yet, so this may indeed be the problem! There's another one for the list then I guess. Ouch. Nothing's worse than data loss. Further testing strongly suggests (so far) that the problem is indeed caused by Anti-Vir. The solution, however, appears to be as simple as configuring Anti-Vir to check files only upon reading, _not_ upon writing. (I was going to try AVG, but that no longer seems necessary.) Four weeks and three machines later, at least I know now. Can anyone explain why check-on-write would cause this problem -- maybe because Anti-Vir was holding up writing to disk until after the next command in my script had been executed and had tried to read the file that was not yet written? Though not a Cygwin problem per se, I'm guessing that other people must have this problem as well - maybe a line of explanation could be added to future BLODA lists and/or the Cygwin FAQ. Many thanks to everyone who took the time to respond to my postings. Tom Baker -- Tom Baker - [EMAIL PROTECTED] - [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
答复: how to set a cygwin root
It really works. Thank you Chritopher -邮件原件- 发件人: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 代表 Christopher Faylor 发送时间: 2007年11月17日 12:29 收件人: cygwin@cygwin.com 主题: Re: how to set a cygwin root On Sat, Nov 17, 2007 at 12:04:11PM +0800, Chen Yue wrote: Hi I have created a cygwin environment on one host and everything is OK. When I copied the whole dir to another host, the cygwin root is switched from C:/cygwin to C:/.(The cygwin root on the original host is C;/cygwin). I don't want to reinstall a cygwin on the other host because it is difficult to set up the whole development environment again. Is there a quick way to change cygwin root dir? Yes. Check out man mount. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Updated: bashdb-3.1_0.09-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bashdb, 3.1_0.09-1, is available for use, replacing 3.1-0.08-1 as the current version. NEWS: = This is a new upstream release. It works with either bash 3.1 or bash 3.2. A list of changes from bashdb-3.1-0.08-1 is below; see also the /usr/share/doc/bashdb-3.1_0.09/ directory. DESCRIPTION: A bash shell script debugger, with command line, emacs, and ddd interfaces. It is possible to debug a bash shell script using 'bashdb file' or 'bash --debugger file'. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'bashdb' from the 'Devel' category. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question, the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin bashdb maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnlK84KuGfSFAYARAsp5AJ9wDmWSzXJ+/09DUbOXGmPjrv/NHwCfc0X2 iNRoM18+d+PJdczxaTMmgj8= =0KHt -END PGP SIGNATURE- Version 3.1 0.09 2007-10-27 - Add set/show trace-commands to make the same as gdb 6.6 - show commands now allows for a starting number and +, same as gdb - Reduce assumption that undefined means '' - initialize more variables. (working towards inserting set -u. - variable and tilde expansion now occurs in cd command. Note gdb does tilde expansion but not variable expansion like $HOME. - add linetrace delay - make FreeBSD tests work, cygwin signals are working so test are run there - documentation updates - emacs code improved - some installation bugs fixed - file name was sometimes incorrectly reported when debugged script set IFS
Updated: findutils-4.3.10-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of findutils, 4.3.10-1, is available for use, leaving 4.3.8-1 as the previous version. NEWS: = This is a new upstream release, fixing several issues as documented below, including all of the cygwin-specific patches that I was previously maintaining. The release is marked beta upstream, but the 4.3 series has, in general, been enough of an improvement over the stable 4.2 series that I have focused on 4.3 releases as the primary cygwin release. Although the news file mentions the partial addition of birthtime support, it requires rebuilding from source against a cygwin snapshot to take advantage of this feature, since birthtime will not be supported officially until cygwin 1.7.0. See also /usr/share/doc/findutils-4.3.10/. DESCRIPTION: The findutils package contains programs which will help you locate files on your system. The find utility searches through a hierarchy of directories looking for files which match a certain set of criteria (such as a filename pattern). The xargs utility builds and executes command lines from standard input arguments (usually lists of file names generated by the find command). The locate utility scans a database of filenames and displays matches. The updatedb utility builds the database for locate. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'findutils' from the 'Base' category (it should already be selected). DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin findutils maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnlb84KuGfSFAYARApXxAJ0cZ7/0il+DvezOLlZ9EplfUpNMjwCfYe++ XP484Dhyk3onVkwGigHNjzY= =GnUj -END PGP SIGNATURE- * Major changes in release 4.3.10, 2007-11-13 ** Bug Fixes #21568: findutils gnulib code does not match the date in import-gnulib.config. We now check out the gnulib code via git-cvs-pserver. * Major changes in release 4.3.9, 2007-11-11 ** Licensing Findutils version 4.3.9 is released under version 3 of the GNU General Public License. ** Bug Fixes #20834: Avoid segmentation violation for -execdir when $PATH is unset. Assume that the PATH is safe in this situation. #20310: configure uses hosts's support status for sort -z when generating the updatedb script for use on the target. This is inappropriate when cross-compiling, so avoid doing that. #20263: Compilation fix for DEC Alpha OSF/1 cc, which forbids the ordering comparison of function pointers. #20139: find -[acm]time -N (wrongly) includes files from N days ago, as well as (correctly) from less than N days ago. #20273: When xargs is successful without consuming all of stdin (for example, with the -E option), and stdin is seekable, xargs now correctly restores the file position, even on platforms where exit() does not follow the POSIX rules of doing likewise. Likewise for find (for example, with the -ok action). #20547: The version information printed by find, xargs, locate, updatedb, frcode and code now complies with the GNU Project's coding standards. #20662: Avoid memory leak in find -name and other places affected by gnulib dirname module. The leak had been present since 4.3.1. #20751: Avoid memory corruption in find -ls that has been present since 4.3.1. #20871: Assertion failure introduced in 4.3.3, when oldfind is invoked in a directory where the parent directory lacks search permission. ** Enhancements #20594: Allow fine-tuning of the default argument size used by xargs and find at ./configure time. #20688: The warning printed by -name or -iname when the pattern to match contains a slash can now be silenced by -nowarn. This warning was originally introduced unconditionally in 4.2.21. Translation of locate --limit problems is improved. POSIX will standardise -path, so the documentation no longer
Updated: git-1.5.3.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of git, 1.5.3.5-1, has been uploaded, replacing 1.5.3.2-1 as the current version. NEWS: = This is a new upstream release. See also the package documentation in /usr/share/doc/git-1.5.3.5/, along with the attached upstream release notes. When compiled out of the box, the upstream git maintainers cater to older cygwin releases, and intentionally disable certain features that have been reported on their mailing list, even though they work with the latest cygwin. Therefore, this build turns those features back on. However, it means that this version does assume that you are not using FAT or FAT32 to hold your repositories, since they do not store file permissions very accurately. DESCRIPTION: Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source projects, most notably the Linux kernel. Git falls in the category of distributed source code management tools, similar to e.g. GNU Arch or Monotone (or BitKeeper in the proprietary world). Every Git working directory is a full-fledged repository with full revision tracking capabilities, not dependent on network access or a central server. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'git' from the 'Devel' category. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin git maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPnls84KuGfSFAYARAsxHAKCLsomVifql5f5L6N/MbPjSLGC3oQCeMsw/ N0TJkgDfiIeaAd9BjBfSXW4= =DFD2 -END PGP SIGNATURE- GIT v1.5.3.5 Release Notes == Fixes since v1.5.3.4 * Comes with git-gui 0.8.4. * git-config silently ignored options after --list; now it will error out with a usage message. * git-config --file failed if the argument used a relative path as it changed directories before opening the file. * git-config --file now displays a proper error message if it cannot read the file specified on the command line. * git-config, git-diff, git-apply failed if run from a subdirectory with relative GIT_DIR and GIT_WORK_TREE set. * git-blame crashed if run during a merge conflict. * git-add -i did not handle single line hunks correctly. * git-rebase -i and git-stash apply failed if external diff drivers were used for one or more files in a commit. They now avoid calling the external diff drivers. * git-log --follow did not work unless diff generation (e.g. -p) was also requested. * git-log --follow -B did not work at all. Fixed. * git-log -M -B did not correctly handle cases of very large files being renamed and replaced by very small files in the same commit. * git-log printed extra newlines between commits when a diff was generated internally (e.g. -S or --follow) but not displayed. * git-push error message is more helpful when pushing to a repository with no matching refs and none specified. * git-push now respects + (force push) on wildcard refspecs, matching the behavior of git-fetch. * git-filter-branch now updates the working directory when it has finished filtering the current branch. * git-instaweb no longer fails on Mac OS X. * git-cvsexportcommit didn't always create new parent directories before trying to create new child directories. Fixed. * git-fetch printed a scary (but bogus) error message while fetching a tag that pointed to a tree or blob. The error did not impact correctness, only user perception. The bogus error is no longer printed. * git-ls-files --ignored did not properly descend into non-ignored directories that themselves contained ignored files if d_type was not supported by the filesystem. This bug impacted systems such as AFS. Fixed.
