Processed: Re: Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly

To: Martin Pitt <mpitt@debian.org>
Cc: GNU Libc Maintainers <debian-glibc@lists.debian.org>(libc6 #290118), Oliver Elphick <Oliver.Elphick@lfix.co.uk>(postgresql #290118)
Subject: Processed: Re: Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 13 Jan 2005 01:33:17 -0800
Message-id: <[🔎] handler.s.C.110560853721491.transcript@bugs.debian.org>
In-reply-to: <20050113092826.GA14413@box79162.elkhouse.de>
References: <20050113092826.GA14413@box79162.elkhouse.de>

Processing commands for control@bugs.debian.org:

> severity 290118 normal
Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
Severity set to `normal'.

> tag 290118 upstream
Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
There were no tags set.
Tags added: upstream

> reassign 290118 libc6
Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
Bug reassigned from package `postgresql' to `libc6'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Reply to:

Prev by Date: Re: valgrind: doesn't start (cannot allocate memory)
Next by Date: Fwd: Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
Previous by thread: Re: valgrind: doesn't start (cannot allocate memory)
Next by thread: Fwd: Bug#290118: postgresql could not be configured to handle characters others than ASCII correctly
Index(es):
- Date
- Thread