bug#35405: Patch for 35405

2019-06-30 Thread Ludovic Courtès
Hi John, Apologies for the late reply. John Ralls skribis: > From f2de9d206b33bc2e27acde1e751df9ba8faf60a9 Mon Sep 17 00:00:00 2001 > From: John Ralls > Date: Tue, 23 Apr 2019 15:06:48 -0700 > Subject: [PATCH] Fix build on MinGW-w64 > > Fixes bug 35405 > >* lib/poll.h: MinGW provides s

bug#35405: Patch for 35405

2019-06-30 Thread Ludovic Courtès
Hi John, Apologies for the late reply. John Ralls skribis: > From f2de9d206b33bc2e27acde1e751df9ba8faf60a9 Mon Sep 17 00:00:00 2001 > From: John Ralls > Date: Tue, 23 Apr 2019 15:06:48 -0700 > Subject: [PATCH] Fix build on MinGW-w64 > > Fixes bug 35405 > >* lib/poll.h: MinGW provides s

bug#36350: [2.2.5] ‘read-headers’ blocks, thereby breaking web servers

2019-06-30 Thread Ludovic Courtès
Hi, Mark H Weaver skribis: > Ludovic Courtès writes: >> Perhaps we should consider releasing 2.0.6 soon and use that in Guix >> on ‘core-updates’. > > Sure, sounds like a good idea. Done in a152a67d3865cc6e7f9d7abd8f17a6e905b8e841. The test is simple but would catch regressions like this one.

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-06-30 Thread Ludovic Courtès
Hi Mark, Mark H Weaver skribis: > Here's a patch that might fix the problem, but I don't have time to test > it right now. It works! :-) I wrote tests and pushed it as ab2fd70ef1e36c6532128b73082809ef3c056556. I forgot to change the commit author to you before pushing, apologies! Thanks, Lud

bug#34860: Probing broken symlinks always involves errors

2019-06-30 Thread Ludovic Courtès
Hi Tim, Tim Gesthuizen skribis: > Mark H Weaver writes: >> Anyway, I'm inclined to simply suggest using 'false-if-exception'. >> >> What do you think? > > I'm fine with this solution. My point was more about lowering the entry > barrier for beginners than performance. > If the change breaks ABI

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-06-30 Thread Mark H Weaver
reopen 35920 thanks Hi Ludovic, > Mark H Weaver skribis: > >> Here's a patch that might fix the problem, but I don't have time to test >> it right now. > > It works! :-) I wrote tests and pushed it as > ab2fd70ef1e36c6532128b73082809ef3c056556. On my system, I found that my proposed patch caus

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-06-30 Thread John Cowan
That's a mug's game: I've been there and tried it (not in Scheme). I recommend writing a strftime in Scheme from scratch. It's not that hard; the most annoying thing is getting into the locale files to handle the locale-sensitive directives (month name, weekday name, AM/PM, and the ordering of dat

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-06-30 Thread Mark H Weaver
Hi John, John Cowan writes: > That's a mug's game: I've been there and tried it (not in Scheme). I > recommend writing a strftime in Scheme from scratch. It's not that > hard; the most annoying thing is getting into the locale files to > handle the locale-sensitive directives (month name, weekd

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-06-30 Thread John Cowan
On Sun, Jun 30, 2019 at 7:06 PM Mark H Weaver wrote: Is there a portable way to find the relevant locale files and interpret > them, on both POSIX and Windows systems? If so, can you point out the > relevant documentation? > Portable in the sense that the information can be obtained on both Pos