Your message dated Fri, 11 Jan 2008 20:39:48 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#172752: dpkg-dev: dpkg-buildpackage messes up Description:
inUTF-8 locale
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dpkg-dev
Version: 1.10.9
When I dowload dosemu source using apt-src dpkg-source complains
about malformed UTF-8 chararcter
[EMAIL PROTECTED]:/home/petr/_Work/dosemu# apt-src install dosemu
Couldn't stat source package list http://shakti.ath.cx ./ Packages
(/var/lib/apt/lists/shakti.ath.cx_debian_kde3.1-rc2_._Packages) - stat (2
není souborem ani adresářem)
You may want to run apt-get update to correct these problems
Reading Package Lists... Done
Building Dependency Tree... Done
Need to get 1717kB of source archives.
Get:1 http://http.us.debian.org stable/contrib dosemu 1.0.2.1-7 (dsc) [788B]
Get:2 http://http.us.debian.org stable/contrib dosemu 1.0.2.1-7 (tar) [1693kB]
Get:3 http://http.us.debian.org stable/contrib dosemu 1.0.2.1-7 (diff)
[23.3kB]
Fetched 1717kB in 1s (1113kB/s)
Malformed UTF-8 character (unexpected end of string) at /usr/bin/dpkg-source
line 604, <GZIP> line 1429.
dpkg-source: extracting dosemu in dosemu-1.0.2.1
W: Couldn't stat source package list http://shakti.ath.cx ./ Packages
(/var/lib/apt/lists/shakti.ath.cx_debian_kde3.1-rc2_._Packages) - stat (2 No
such file or directory)
W: You may want to run apt-get update to correct these problems
[EMAIL PROTECTED]:/home/petr/_Work/dosemu# locale
LANG=czech
LC_CTYPE="cs_CZ.UTF-8"
LC_NUMERIC="cs_CZ.UTF-8"
LC_TIME="cs_CZ.UTF-8"
LC_COLLATE="cs_CZ.UTF-8"
LC_MONETARY="cs_CZ.UTF-8"
LC_MESSAGES="cs_CZ.UTF-8"
LC_PAPER="cs_CZ.UTF-8"
LC_NAME="cs_CZ.UTF-8"
LC_ADDRESS="cs_CZ.UTF-8"
LC_TELEPHONE="cs_CZ.UTF-8"
LC_MEASUREMENT="cs_CZ.UTF-8"
LC_IDENTIFICATION="cs_CZ.UTF-8"
LC_ALL=cs_CZ.UTF-8
--
Petr Baláš (petr at balas dot cz)
--- End Message ---
--- Begin Message ---
On Thu, 12 Dec 2002, Radovan Garabik wrote:
> I ahev a package with Description in UTF-8. Until some time ago,
> all worked well, dpkg-buildpackage placed the Description verbatim
> into debian package. However, I found out now that if I compile the
> package in UTF-8 locale, Description is mangled. It seems that
> the encoding is assumed to be in ISO-8859-1 and is converted into
> UTF-8. Of course, since it was already in UTF-8, the result is mojibake.
>
> In 8-bit locales the Description is copied verbatim and all works well.
> I guess it has something to do with new perl's UTF-8 capabilities
> (as many other bugs already reported)
I just read perluniintro(1), perlunicode(1) and PerlIO(3) and the latest
perl version can't have such problems since it will always keep strings as
8 bit internally, until an unicode character > 0xFF is somehow added
to the string (ie there's no conversion of input by default).
Furthermore none of the filehandles use UTF8 by default. One need to use
-C to explicitely enable that (or PERL_UNICODE).
So I'm closing both bugs on the topic. They were rightfully tagged
unreproducible already.
Though I agree it's good style to call binmode() when we handle known
binary data. I have made the changes locally and I'll commit them if all
seems to go well.
With this, I also fixed dpkg-genchanges, dpkg-gencontrol and dpkg-source
to write *.dsc, *.changes and DEBIAN/control files as UTF-8. And here Perl
might implicitely do some conversion if the input is not valid UTF-8.
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
--- End Message ---
