Bug#877900: How to get 24-hour time on en_US.UTF-8 locale now?

2019-02-08 Thread Wouter Verhelst
On Thu, Feb 07, 2019 at 02:05:33PM +0100, Adam Borowski wrote:
> > LC_TIME="en_US.UTF-8"

If you don't want US time, don't set US time.

Instead, do something like:

LC_TIME=en_BE.UTF-8

which means "I want time in English, but using Belgian customs, not the
US ones".

You may have to custom edit that time definition, though. Alternatively,
set LC_TIME to en_GB.UTF-8 or whatever other pre-existing locale.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard



Bug#877900: general: en-us locale defaults to 24-hour "military" time on stock install

2017-10-19 Thread Wouter Verhelst
On Sat, Oct 07, 2017 at 07:17:56AM +0200, Adam Borowski wrote:
[time formats]
> * en_US (.UTF-8) is used as the default English locale for all places that
>   don't have a specific variant (and often even then).  Generally, technical
>   users use English as a system locale as translations of computing terms
>   tend to be a horror show: for example, in Polish even such a basic term
>   as "file" has two versions ("zbiór" — correct, and "plik" — Microsoftese)
>   that are not intelligible between some groups of people.  Anything more
>   complex gets bad enough that no one bothers translating advanced technical
>   documentation or running servers (rather than user-facing systems) in
>   pl_PL locale.  And as far as I know, same applies to most languages.

Yes, but this bug is about time formats, not about messages -- i.e.,
it's about LC_TIME, not about LC_MESSAGES. It's perfectly possible to
set LC_TIME to pl_PL, and LC_MESSAGES to en_US if that's what you want.

(same with other things, like LC_PAPER or LC_MONETARY, that would differ
between those regions)

Meanwhile, I think that indeed setting LC_TIME to en_US should result in
the time format most common in the region served by that locale.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab



Bug#389945: nbd.h broken

2006-09-28 Thread Wouter Verhelst
Package: linux-kernel-headers
Version: 2.6.18-1
Severity: normal
File: /usr/include/linux/nbd.h

Hi,

when I try to compile nbd-server against the nbd.h currently in
linux-kernel-headers, I get the following output:

if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2 -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include   -g -O2 -MT nbd_server-nbd-server.o -MD -MP -MF 
.deps/nbd_server-nbd-server.Tpo -c -o nbd_server-nbd-server.o `test -f 
'nbd-server.c' || echo './'`nbd-server.c; \
then mv -f .deps/nbd_server-nbd-server.Tpo 
.deps/nbd_server-nbd-server.Po; else rm -f .deps/nbd_server-nbd-server.Tpo; 
exit 1; fi
In file included from cliserv.h:42,
 from nbd-server.c:90:
/usr/include/linux/nbd.h:80: error: expected specifier-qualifier-list before 
‘__be32’
/usr/include/linux/nbd.h:96: error: expected specifier-qualifier-list before 
‘__be32’
nbd-server.c: In function ‘mainloop’:
nbd-server.c:655: error: ‘struct nbd_reply’ has no member named ‘magic’
nbd-server.c:656: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:667: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:667: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:668: error: ‘struct nbd_request’ has no member named ‘type’
nbd-server.c:668: error: ‘struct nbd_request’ has no member named ‘type’
nbd-server.c:670: error: ‘struct nbd_request’ has no member named ‘type’
nbd-server.c:682: error: ‘struct nbd_request’ has no member named ‘len’
nbd-server.c:684: error: ‘struct nbd_request’ has no member named ‘magic’
nbd-server.c:693: error: ‘struct nbd_reply’ has no member named ‘handle’
nbd-server.c:693: error: ‘struct nbd_request’ has no member named ‘handle’
nbd-server.c:693: error: ‘struct nbd_reply’ has no member named ‘handle’
nbd-server.c:694: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:696: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:696: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:700: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:701: error: ‘struct nbd_request’ has no member named ‘type’
nbd-server.c:704: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:704: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:708: error: ‘struct nbd_request’ has no member named ‘type’
nbd-server.c:713: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:716: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:716: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:726: error: ‘struct nbd_request’ has no member named ‘from’
nbd-server.c:728: error: ‘struct nbd_reply’ has no member named ‘error’
nbd-server.c:728: error: ‘struct nbd_reply’ has no member named ‘error’
make[1]: *** [nbd_server-nbd-server.o] Error 1

Which is not supposed to happen.

(note that the nbd source package contains a separate nbd.h file which
is used instead, since it also needs to build on non-Linux ports; to
reproduce, remove that file before building)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#364098: mumble, mumble

2006-04-21 Thread Wouter Verhelst

-- 
Fun will now commence
  -- Seven Of Nine, Ashes to Ashes, stardate 53679.4
Applying patch localedata/locale-de_CH.diff
patching file localedata/locales/de_CH

Applying patch locale-ru_RU.diff
patching file intl/locale.alias

Applying patch localedata/locale-eo_EO.diff
patching file localedata/locales/eo
patching file localedata/SUPPORTED

Applying patch localedata/locale-no_NO.diff
patching file localedata/locales/no_NO

Applying patch glibc-i686-timing.diff
patching file sysdeps/generic/ldsodefs.h
Hunk #1 succeeded at 451 (offset 193 lines).
Hunk #2 succeeded at 662 (offset 200 lines).
patching file sysdeps/i386/hp-timing.h
patching file elf/dl-altinit.c
patching file elf/Makefile
Hunk #1 succeeded at 23 with fuzz 2.

Applying patch glibc-sparc-timing.diff
patching file sysdeps/sparc/sparc32/hp-timing.h

Applying patch makeconfig.diff
patching file Makeconfig
Hunk #1 succeeded at 544 (offset 3 lines).

Applying patch ldconfig.diff
patching file elf/ldconfig.c
Hunk #1 succeeded at 992 (offset 20 lines).

Applying patch ldd.diff
patching file elf/ldd.bash.in

Applying patch fhs-linux-paths.diff
patching file sysdeps/unix/sysv/linux/paths.h
Hunk #1 succeeded at 67 (offset -4 lines).

Applying patch glibc22-nss-upgrade.diff
patching file nss/nsswitch.c
Hunk #1 succeeded at 344 (offset 11 lines).

Applying patch sparc64-fixups.diff
patching file elf/ldconfig.c
Hunk #1 succeeded at 320 (offset 33 lines).

Applying patch glibc22-ttyname-devfs.diff
patching file sysdeps/unix/sysv/linux/ttyname_r.c
Hunk #5 succeeded at 150 (offset 7 lines).
patching file sysdeps/unix/sysv/linux/ttyname.c
Hunk #1 succeeded at 33 with fuzz 2 (offset 3 lines).
Hunk #2 succeeded at 42 (offset 3 lines).
Hunk #3 succeeded at 58 (offset 3 lines).
Hunk #4 succeeded at 81 (offset 3 lines).
Hunk #5 succeeded at 115 (offset 5 lines).
Hunk #6 succeeded at 152 (offset 5 lines).

Applying patch powerpc-sysconf.diff
patching file sysdeps/unix/sysv/linux/powerpc/getsysstats.c

Applying patch glibc23-hppa-Rminkernel.diff
patching file sysdeps/unix/sysv/linux/configure.in
Hunk #1 succeeded at 69 (offset 4 lines).
patching file sysdeps/unix/sysv/linux/configure
Hunk #1 succeeded at 109 (offset 3 lines).

Applying patch glibc23-asserth-decls.diff
patching file assert/assert.h

Applying patch glibc23-cmov.diff
patching file sysdeps/i386/dl-procinfo.h

Applying patch hurd-enable-ldconfig.diff
patching file sysdeps/mach/hurd/configure
Hunk #1 succeeded at 90 with fuzz 2 (offset -25 lines).
patching file sysdeps/mach/hurd/configure.in
patching file elf/ldconfig.c
Hunk #1 succeeded at 57 (offset 8 lines).
patching file sysdeps/mach/hurd/dl-cache.c

Applying patch sparcv8-target.diff
patching file configure
Hunk #1 succeeded at 1798 (offset 2 lines).
patching file configure.in
Hunk #1 succeeded at 307 (offset -30 lines).

Applying patch 50_glibc232-arm-dwarf2-buildfix.diff
patching file sysdeps/arm/framestate.c
patching file sysdeps/arm/unwind-pe.c

Applying patch 50_glibc232-m68k-dwarf2-buildfix.diff
patching file sysdeps/m68k/framestate.c
patching file sysdeps/m68k/unwind-pe.c

Applying patch glibc-2.3.2-ldconfig-tls.diff
patching file elf/cache.c

Applying patch 90_glibc233_tcsetaddr.diff
patching file sysdeps/unix/sysv/linux/tcsetattr.c
Hunk #1 succeeded at 48 (offset -7 lines).
Hunk #2 succeeded at 85 (offset -7 lines).

Applying patch localedef-fix-trampoline.diff
patching file locale/programs/3level.h
Hunk #1 succeeded at 202 (offset -2 lines).

Applying patch localedata/locale-eu_FR.diff
patching file localedata/locales/eu_FR
patching file localedata/SUPPORTED
Hunk #1 succeeded at 163 with fuzz 1 (offset -3 lines).
patching file localedata/locales/[EMAIL PROTECTED]

Applying patch glibc23-mips-lazy-eval.diff
patching file elf/do-lookup.h
Hunk #1 succeeded at 192 (offset -17 lines).

Applying patch glibc235-gcc4-wcstol_l.diff
patching file sysdeps/wordsize-64/strtol_l.c
patching file sysdeps/wordsize-64/wcstol_l.c

Applying patch glibc235-gcc4-ppc-procfs.diff
Patch glibc235-gcc4-ppc-procfs.diff does not exist


Bug#343885: nl_BE wrongly has sunday as start of week

2005-12-18 Thread Wouter Verhelst
Package: locales
Version: 2.3.5-8.1
Severity: normal

Hi,

In Belgium, the week is percieved as starting on Mondays. However, the
locale does not seem to export this correctly.

(I'm assuming the locale contains this information because the GTK+ API
documentation suggests a GtkCalendar gets that information from the
locale. If that is wrong, I'll need to find out something else
somewhere...)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.2
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

Versions of packages locales depends on:
ii  debconf [debconf-2.0] 1.4.62 Debian configuration management sy
ii  libc6 [glibc-2.3.5-3] 2.3.5-8GNU C Library: Shared libraries an

locales recommends no packages.

-- debconf information:
* locales/default_environment_locale: [EMAIL PROTECTED]
* locales/locales_to_be_generated: en_US.UTF-8 UTF-8, en_US ISO-8859-1, 
nl_BE.UTF-8 UTF-8, [EMAIL PROTECTED] ISO-8859-15, [EMAIL PROTECTED] UTF-8, 
nl_BE ISO-8859-1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#225594: [Paul.Clements@SteelEye.com: Re: 2.6 nbd.h]

2003-12-30 Thread Wouter Verhelst
Package: linux-kernel-headers
Version: 2.5.999-test7-bk-10
Severity: normal

Hi,

There's an error in the 2.6 linux/nbd.h; to make userspace
compilations work, the following patch needs to be applied:

---cut here---
--- linux-2.6.0-test11/include/linux/nbd.h.orig Mon Dec 15 09:48:53 2003
+++ linux-2.6.0-test11/include/linux/nbd.h  Mon Dec 15 09:54:02 2003
@@ -35,6 +35,9 @@
 /* Define PARANOIA to include extra sanity checking code in here  driver */
 #define PARANOIA
 
+/* userspace doesn't need the nbd_device structure */
+#ifdef __KERNEL__
+
 struct nbd_device {
int flags;
int harderror;  /* Code of hard error   */
@@ -52,6 +55,8 @@
int blksize;
u64 bytesize;
 };
+
+#endif
 
 /* This now IS in some kind of include file... */
---cut here---

Paul Clements, the kernel-side NBD maintainer, sent this in for
inclusion in 2.6.0, but apparantly it didn't make it in time.

It would be nice if you could apply this patch to linux-kernel-headers
already; but note that it isn't really urgent since my nbd package now
includes this header in the source package (which actually is the right
thing to do, as that will allow it at some point to be compiled on
non-linux ports, too).
 
-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
Stop breathing down my neck. My breathing is merely a simulation.
So is my neck, stop it anyway!
  -- Voyager's EMH versus the Prometheus' EMH, stardate 51462.


signature.asc
Description: Digital signature


Bug#225594: [Paul.Clements@SteelEye.com: Re: 2.6 nbd.h]

2003-12-30 Thread Wouter Verhelst
Package: linux-kernel-headers
Version: 2.5.999-test7-bk-10
Severity: normal

Hi,

There's an error in the 2.6 linux/nbd.h; to make userspace
compilations work, the following patch needs to be applied:

---cut here---
--- linux-2.6.0-test11/include/linux/nbd.h.orig Mon Dec 15 09:48:53 2003
+++ linux-2.6.0-test11/include/linux/nbd.h  Mon Dec 15 09:54:02 2003
@@ -35,6 +35,9 @@
 /* Define PARANOIA to include extra sanity checking code in here  driver */
 #define PARANOIA
 
+/* userspace doesn't need the nbd_device structure */
+#ifdef __KERNEL__
+
 struct nbd_device {
int flags;
int harderror;  /* Code of hard error   */
@@ -52,6 +55,8 @@
int blksize;
u64 bytesize;
 };
+
+#endif
 
 /* This now IS in some kind of include file... */
---cut here---

Paul Clements, the kernel-side NBD maintainer, sent this in for
inclusion in 2.6.0, but apparantly it didn't make it in time.

It would be nice if you could apply this patch to linux-kernel-headers
already; but note that it isn't really urgent since my nbd package now
includes this header in the source package (which actually is the right
thing to do, as that will allow it at some point to be compiled on
non-linux ports, too).
 
-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
Stop breathing down my neck. My breathing is merely a simulation.
So is my neck, stop it anyway!
  -- Voyager's EMH versus the Prometheus' EMH, stardate 51462.


signature.asc
Description: Digital signature


Bug#188079: close() and/or fork() misbehaving

2003-04-09 Thread Wouter Verhelst
severity 188079 normal
thanks

Op wo 09-04-2003, om 01:55 schreef GOTO Masanori:
  Since I did not modify any C code in this package at the time the bug
  appeared, the problem must lie somewhere else. Running nbd-server in
  strace shows that it accept()s the client's call, then fork()s, as it
  should. Next, when the parent does a close() of the socket acquired with
  accept(), a FIN packet is sent to the client, closing the connection,
  although the child process still has the socket open. When it tries to
  send() something through that socket, it of course gets a SIGPIPE.
  
  Attached, the two files that form the output of 
  
  strace -ff -o nbd-server-trace nbd-server 1234 /export/m68k/exp-bl-dev
 
 Why did you assign this bug to libc6 with grave severity?

Sorry, I indeed forgot to lower the severity. It's a cloned bug that is
indeed a valid grave bug for nbd, but not for libc6. Changed that with
this message.

If I'm not the only one with this problem, it might be a higher severity
than normal, though; I'll leave that up to you.

 What is the
 problem?  Which version was it worked?

The differences between nbd-server 1:2.3-4 and 1:2.3-6 is only
differences of packaging; I converted to po-debconf, and added some
translations from ddtp.d.o. There were no modifications to the C source.

However, 1:2.3-4 works, while 1:2.3-6 doesn't. This leads me to believe
it's a problem with either libc6, binutils, or gcc. I assigned the bug
to libc6 because that seemed the most valid candidate to me; however, it
might be that I'm misguided, and that the bug is in fact not libc6's
fault. To be sure, I ran nbd-server from within gdb, and checked what
happened; it looked as if the socket for the child process was closed
when the parent closed it, which obviously is incorrect.

IIRC, 1:2.3-4 was compiled using libc6 2.3.1-1, because I remember
waiting for it to be on my system. 1:2.3-6 has been compiled using an
up-to-date sid system, last week.

 If I can not get valid
 information, I reassign this bug back to package nbd.

What extra information do you want me to provide?

-- 
wouter at grep dot be
An expert can usually spot the difference between a fake charge and a
full one, but there are plenty of dead experts. 
  -- National Geographic Channel, in a documentary about large African beasts.


signature.asc
Description: Dit berichtdeel is digitaal gesigneerd