[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342094: marked as done (www.debian.org: mirror/sponsors cannot be build in japanese)



Your message dated Fri, 8 Dec 2006 23:27:15 +0100
with message-id <20061208222715.GA21461@dedibox>
and subject line www.debian.org: mirror/sponsors is build in japanese
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: www.debian.org
Severity: normal

the source for the mirror sponsors contains characters that cannot be 
converted for the japanese pages.

Results are error messages in sponsors.ja.html:

478:   <td>debian.funlam.edu.co</td>
479:   <td>
480: #### 64 byte(s) unconvertable ####
481: #### 7 byte(s) unconvertable ####
482: #### 5 byte(s) unconvertable ####

can somebody repair the sources for the mirror sponsors, please?

Jutta


-- System Information:
Debian Release: 3.1
Architecture: powerpc (ppc)
Kernel: Linux 2.6.8-powerpc
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)


--- End Message ---
--- Begin Message ---
On Mon, Dec 05, 2005 at 11:09:31AM +0100, Jutta Wrage wrote:
> Package: www.debian.org
> Severity: normal
> 
> the source for the mirror sponsors contains characters that cannot be 
> converted for the japanese pages.
> 
> Results are error messages in sponsors.ja.html:
> 
> 478:   <td>debian.funlam.edu.co</td>
> 479:   <td>
> 480: #### 64 byte(s) unconvertable ####
> 
> can somebody repair the sources for the mirror sponsors, please?

Hello Jutta,

http://www.debian.org/mirror/sponsors.ja.html is correctly build now.

So, I close this bug.

Regards,

-- 
Simon Paillard

--- End Message ---

Reply to: