| Summary: | After removing USE=”python perl” from the default profile, evince needs to force libxml2 to compile with python enabled | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Torsten Stets <akusai> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Evince does not depend on libxml2[python] because evince never directly calls the libxml2 python module. Instead, libxml2[python] is a required dependency of some of evince's dependencies. If you had run "emerge --deep evince", emerge would have told you that libxml2 with the python USE flag is required. Since "emerge --deep" is (unfortunately) not the default, and since a significant number of packages, including evince, in effect fail to build without libxml2[python], the USE flag for libxml2 is now been enabled by default on desktop profiles; see bug 385843. *** This bug has been marked as a duplicate of bug 385843 *** |
Running emerge -avuDN world compiles a lot of packages without python support. One of them is libxml2. After that, an emerge of evince will fail with errors about missing libxml2 python modules. Reproducible: Always Steps to Reproduce: 1. run emerge --sync 2. run emerge -avuDN world 3.1 try opening a pdf with evince -> unsupported filetype pdf 3.2 try re-emerging evince -> fails to emerge because of missing python modules Actual Results: Unable to open PDF's / unable to re-emerge evince Expected Results: evince should continue to open pdf's or be able to be re-emerged. Making evince depend on libxml2 to be compiled with python support should fix the problem. e.g. in evince-2.32.0-r3.ebuild in line 24 change >=dev-libs/libxml2-2.5:2 to >=dev-libs/libxml2-2.5:2[python] should get rid of the problem.