| Summary: | || ( unstable stable[unset-flag] ) dependency causes portage to choose the unstable package | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Adam Piątyszek <ediap> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | loki_val, SebastianLuther |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Adam Piątyszek
2009-04-19 14:55:14 UTC
You have some of the unstable poppler-libs keyworded. See http://xrl.us/bephtt for a list of which ebuilds to keyword or not keyword, depending on whether you want the stable or the unstable versions of poppler. Hi Peter,
I have none poppler* packages keyworded at all:
ediap@tataj ~/tmp/mc_cc $ cat /etc/portage/package.keywords/* |grep pop
ediap@tataj ~/tmp/mc_cc $
Here is what I have installed:
ediap@tataj ~/tmp/mc_cc $ eix -I poppler
[I] app-text/poppler
Available versions: 0.8.7 0.10.4 ~0.10.5 0.10.5-r1 {cjk doc jpeg zlib}
Installed versions: 0.10.5-r1(19:47:17 18.04.2009)(-doc)
Homepage: http://poppler.freedesktop.org/
Description: PDF rendering library based on the xpdf-3.0 code base
[I] app-text/poppler-data
Available versions: 0.2.1
Installed versions: 0.2.1(19:46:09 18.04.2009)
Homepage: http://poppler.freedesktop.org/
Description: Data files for poppler to support uncommon encodings without xpdfrc
[I] virtual/poppler
Available versions: 0.8.7+v 0.10.4+v 0.10.5+v ~0.10.6+v
Installed versions: 0.10.5+v(19:47:27 18.04.2009)
Homepage: http://poppler.freedesktop.org/
Description: Virtual package, includes packages that contain libpoppler-glib.so
[I] virtual/poppler-utils
Available versions: 0.8.7+v 0.10.4+v 0.10.5+v ~0.10.6+v {abiword}
Installed versions: 0.10.5+v(19:47:23 18.04.2009)(abiword)
Homepage: http://poppler.freedesktop.org/
Description: Virtual package, includes packages that contain the psto* utilities
app-text/poppler is installed as a dependency for virtual/poppler, which is required by dev-tex/luatex-0.30.3 on my system.
What I was trying to report here is the fact that the poppler-glib package is keyworded as ~amd64, but it is required by the stable epdfview-0.1.6-r1:
ediap@tataj ~/tmp/mc_cc $ eix epdfview
* app-text/epdfview
Available versions: 0.1.6-r1 ~0.1.7-r1 {cups debug nls test}
Homepage: http://trac.emma-soft.com/epdfview/
Description: Lightweight PDF viewer using Poppler and GTK+ libraries.
ediap@tataj ~/tmp/mc_cc $ eix poppler-glib
* dev-libs/poppler-glib
Available versions: ~0.10.5 ~0.10.6 {cairo}
Homepage: http://poppler.freedesktop.org/
Description: Glib bindings for poppler
* virtual/poppler-glib
Available versions: 0.8.7+v 0.10.4+v 0.10.5+v ~0.10.6+v {cairo}
Homepage: http://poppler.freedesktop.org/
Description: Virtual package, incl
I know, that I can unmask/keyword some of the dependencies, but this bug report is for stable system.
Hope this clarifies the situation.
/Adam
epdfview depends on:
>=virtual/poppler-glib-0.5.0[cairo]
Which can be satisfied by either poppler-bindings[gtk,cairo]
USE="cairo gtk" emerge -1 poppler-bindings
should solve your problems in other words. I am puzzled by portage pulling in poppler-glib. It really shouldn't.
Can you confirm that the proposed fix works?
Yes this solves the problem. Adding "app-text/poppler-bindings cairo" to /etc/portage/package.use results in correct calculation of dependencies by portage: tataj ~ # emerge -av epdfview These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-text/poppler-bindings-0.10.5-r1 USE="cairo gtk -qt3 -qt4 -test" 0 kB [ebuild N ] virtual/poppler-glib-0.10.5 USE="cairo" 0 kB [ebuild N ] app-text/epdfview-0.1.6-r1 USE="cups nls -test" 0 kB Without the cairo flag, portage requests me to unmask "poppler-glib". /Adam IMO, portage should never say that the needed package is the unstable one in this situation.
I'll probably fix this by making virtual/poppler*-0.10.5 depend on only app-text/poppler{,-bindings}
(In reply to comment #5) > IMO, portage should never say that the needed package is the unstable one in > this situation. > I'll probably fix this by making virtual/poppler*-0.10.5 depend on only > app-text/poppler{,-bindings} > If you just reorder the it so the preferred package is on the left then that will probably solve it. *nod*, but if I touch the virtuals, I might as well remove the split popplers from consideration, since they're due to be punted anyway ( bug 263028 ) |
