Opened 14 years ago
Closed 13 years ago
#7412 closed bug (fixed)
Error converting string from 'UTF-8' to native encoding during download from svn
Reported by: | taos | Owned by: | leavengood |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta1 |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #7495 | Blocking: | |
Platform: | All |
Description
Using hrev41122 (gcc2hybrid).
When downloading Haiku's source code from svn I get the following error:
svn: Can't convert string from 'UTF-8' to native encoding: svn: /SVN/trunk/src/data/keymaps/French (B?\195?\169po).keymap svn: Can't convert string from 'UTF-8' to native encoding: svn: /SVN/trunk/src/data/keymaps/French (B?\195?\169po).keymap
When updating the error is:
svn: Error converting entry in directory '/SVN/trunk/src/data/keymaps' to UTF-8 svn: Can't convert string from native encoding to 'UTF-8': svn: French (B?\195?\169po)p-0.keymap svn: Error converting entry in directory '/SVN/trunk/src/data/keymaps' to UTF-8 svn: Can't convert string from native encoding to 'UTF-8': svn: French (B?\195?\169po)p-0.keymap
Used to work fine with hrev41094.
Last change to haiku/trunk/src/data/keymaps/French (Bépo).keymap was some 4 months ago ([39571]).
Attachments (2)
Change History (17)
comment:2 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 14 years ago
This is probably related to this issue: http://ports.haiku-files.org/ticket/422 And most likely related to apr/apr-util builds?
by , 14 years ago
Attachment: | apr_old.png added |
---|
by , 14 years ago
Attachment: | apr_new.png added |
---|
comment:5 by , 14 years ago
scottmc: having pondered things a bit more, I'm actually inclined to believe that your latest packages of apr/apr-util are more correct than the 2010-11-12 ones, for two reasons:
- Using the new packages, Tracker now displays 'Bépo' correctly (see attached screenshots) after deleting the src/data/keymaps folder and svn up'ing.
- Haiku now behaves exactly like my Linux installation, it needs
export LC_CTYPE="en_US.UTF-8"
, else it throws the "svn: Can't convert string from 'UTF-8'..." error.
comment:6 by , 14 years ago
There was a thread on the HaikuPorts mailing list regarding the issue. The first mail doesn't quite hit it, but the outcome is that the current behavior -- "UTF-8" must be specified via environment variable -- is entirely expected and that for a login shell some script (/etc/profile
?) should set the locale environment variable(s).
comment:7 by , 14 years ago
Owner: | changed from | to
---|
follow-up: 10 comment:8 by , 14 years ago
So we need add LC_CTYPE="en_US.UTF-8" to /etc/profile, or perhaps /boot/system/boot/SetupEnvironment?
The readd of the new apr package has broken this again, but executing export LC_CTYPE="en_US.UTF-8" on the commandline then let's subversion do a full checkout of haiku's source code. So it seems we just need to add it to a script. /boot/system/boot/SetupEnvironment seems like a logical place, can it be overridden in case a user wants a different setting?
If no objections then I'll add it.
comment:10 by , 14 years ago
Replying to scottmc:
So we need add LC_CTYPE="en_US.UTF-8" to /etc/profile, or perhaps /boot/system/boot/SetupEnvironment?
No. We need a command line tool that fetches the current locale settings (via the locale kit) and returns a corresponding POSIX locale string. In /etc/profile
the locale environment variable(s) should be set using this command. SetupEnvironment
would not be the best place as it is executed only on boot-up, so it cannot work for multi-user and locale settings changes wouldn't take effect until reboot.
The readd of the new apr package has broken this again, but executing export LC_CTYPE="en_US.UTF-8" on the commandline then let's subversion do a full checkout of haiku's source code. So it seems we just need to add it to a script. /boot/system/boot/SetupEnvironment seems like a logical place, can it be overridden in case a user wants a different setting?
If no objections then I'll add it.
I guess it doesn't harm as a temporary work-around.
comment:11 by , 14 years ago
Blocked By: | 7495 added |
---|
comment:12 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Created #7495, to clarify the desired solution.
comment:13 by , 13 years ago
Milestone: | R1 → R1/beta1 |
---|
comment:14 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | reopened → assigned |
Taking ownership as I also took ownership on the blocking ticket #7495.
comment:15 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I have fixed the blocking ticket so I'm marking this as fixed.
Yes, I noticed it as well this weekend on a gcc4 installation that I cross-compiled from Ubuntu 10.10 (32-bit). A nightly vmware build worked fine, however. I'll see if I can narrow down the regression range.
IIRC, to work around the problem, type:
export LC_CTYPE="en_US.UTF-8"