Agustin Martin wrote:
>On Fri, Jun 17, 2005 at 01:33:49PM +0200, Bastian Blank wrote:
>
>
>>Package: bacula-director-pgsql
>>Version: 1.36.3-1
>>Severity: important
>>
>>The director fails to write files into the db. I setup the PostgreSQL
>>with Unicode as charset, so the bacula db inherit this encoding if not
>>explicitely overwritten.
>>
>>Now it don't filter the filenames and fails to insert them with the
>>following error:
>>| 17-Jun 13:23 wavehammer-dir: Shockwave_Home.2005-06-17_13.22.55 Fatal
>>error: catreq.c:346 Attribute create error. sql_create.c:685 Create db
>>Filename record INSERT INTO Filename (Name) VALUES ('her') failed. ERR=ERROR:
>> invalid byte sequence for encoding "UNICODE": 0xecb408
>>
>>
>
>Hi, Bastian,
>
>This seems to be the same as
>
>#313227: bacula-director-pgsql:
>omits to set character encoding when creating database
>
>that Jose Luis Tallon (bacula maintainer) closed in 1.36.3-2.
>
>I have received another bugreport against aspell-es package, complaining that
>one of the filenames was single-byte 8-bit,
>
>#328744: aspell-es:
>Contains a filename in ISO-8859-1, even on unicode systems
>
>that seems to be the same already fixed bacula problem. I am still waiting for
>feedback from submitter, but in any case I plan to reassign it to
>bacula-director-pgsql and tag it as closed as of 1.36.3-2, unless Jose Luis
>objects.
>
>
No problem at all. Setting enconding upon catalog creation was
incorporated a while ago.
I plan on releasing a new version soon, addressing the recent CAN issue
(minor importance)
Thanks for CC'ing me on this
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
