Bug 263756 – sys-apps/portage-2.2_rc27: package fails when "epydoc" USE flag is set

• Status: RESOLVED DUPLICATE of bug 208759
• Product: Gentoo Linux

[Description Sergei Danilov 2009-03-25 17:26:58 UTC]

emerge sys-apps/portage-2.2_rc27 fails  when  "epydoc" user flag is enabled

Reproducible: Always



Expected Results:  
compilation should go fine with epydoc use flag

Writing pt04.html for part(qa)                                                              
Writing index.html for book(portage)                                                        
xmlto xhtml-nochunks -m custom.xsl portage.docbook                                          
 * Generating api docs                                                                      


UNEXPECTED ERROR:
'utf8' codec can't decode bytes in position 589-591: invalid data

[Comment 1 Sergei Danilov 2009-03-25 17:28:08 UTC]

Created attachment 186235 [details]
here is full emerge log

[Comment 2 Zac Medico 2009-03-26 21:40:34 UTC]

It works for me with epydoc-3.0.1. Which version of epydoc do you have?

[Comment 3 Sergei Danilov 2009-03-27 05:02:43 UTC]

I'am using the same version of epydoc
dev-python/epydoc-3.0.1  USE="-doc -latex"
maybe it depends on python version?
here is mine: dev-lang/python-2.5.4-r2  USE="doc gdbm ncurses readline ssl threads xml -berkdb -build -examples -ipv6 -sqlite -tk -ucs2 -wininst"

[Comment 4 Zac Medico 2009-03-27 06:25:25 UTC]

Mine is pretty close to yours:

dev-lang/python-2.5.4-r2  USE="doc gdbm ipv6 ncurses readline sqlite ssl threads tk xml -berkdb -build -examples -ucs2 -wininst"
dev-python/epydoc-3.0.1  USE="doc -latex"

Can you edit the portage ebuild, add --debug to the epydoc command, and post the output that it gives you then?

[Comment 5 Sergei Danilov 2009-03-27 09:20:55 UTC]

Created attachment 186396 [details]
Sure , I attached new portage log called portage-2.2_rc27:20090327-091614.log

[Comment 6 Zac Medico 2009-03-27 18:56:30 UTC]

Created attachment 186466 [details, diff]
patch epydoc to show some more info about the UnicodeDecodeError

Can you apply this patch to epydoc, and generate the error again? This will allow us to see which module it was processing, and the specific characters that triggered the error.

[Comment 7 Zac Medico 2009-03-27 19:01:55 UTC]

After you apply the patch, you should regenerate the associated *.pyc and *.pyo in order to avoid a potential sandbox violation:

x=/usr/lib64/python2.5/site-packages/epydoc
python -c "from compileall import compile_dir; compile_dir('$x')"
python -O -c "from compileall import compile_dir; compile_dir('$x')"

[Comment 8 Sergei Danilov 2009-03-27 21:07:55 UTC]

Created attachment 186480 [details]
Done , new attachment called portage-2.2_rc27:20090327-210356.log

[Comment 9 Zac Medico 2009-03-27 22:40:49 UTC]

It seems that dev-python/pysqlite contains some invalid characters inside the author's name in the header of /usr/lib64/python2.5/site-packages/pysqlite2/dbapi2.py:

#-*- coding: utf-8 -*-
# pysqlite2/dbapi2.py: the DB-API 2.0 interface
#
# Copyright (C) 2004-2007 Gerhard H�ring <[e-mail]>
#

*** This bug has been marked as a duplicate of bug 208759 ***