Upgrading to libkexif-0.2.1 broke showimg, and showimg builds with libkexif support only with libkexif 0.1 Showimg can be built also with libkexif support disabled, but there's no way in the ebuild to control it. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I don't want to make it optional and it wouldn't be a solution too, since users who want to have it installed, still face the problem. Having likexif-0.2.1 installed doesn't stop you to to install showimg w/o it. If I set a blocking dependency, I get bugs regarding alternating up/downgrades. It's a bit unfortunate, that the involved developers do not time their releases. It's not stable, so it's not an issue. If you want showimg w/ libkexif, please mask 0.2.1 locally.
Maybe this error message comes from this incompatibility? Viewing an image in embedd mode (konqueror) i get this: There was an error loading the module ShowImg Image Viewer. The diagnostics is: libkexif.so.0: cannot open shared object file: No such file or directory qpkg -I -v libexif libexif-0.5.12-r1
ooops, i mean qpkg -I -v lib_k_exif media-libs/libkexif-0.2.1
Thomas: You have to emerge showimg again or to go back to likexif-0.1.
That's not a solution, re-emerging showimg with libkexif 0.2.1 will build the package WITHOUT libkexif support.
The developer of showimg is informed about this. He will realease -0.9.4a later on...
The dependecy bug is fixed in 0.9.4-1 You may test it out. See http://listes.jalix.org/wws/arc/showimg-users/2005-01/msg00002.html
Created attachment 48100 [details] Ebuild for 0.9.4-1 test package
Compiles fine but also media-plugins/kipi-plugins need to be recompiled against new libkexif.
Thanks for your support, Thomas. I'll add it, when upstream does release it. >Compiles fine but also media-plugins/kipi-plugins need to be recompiled against new libkexif. Your job, Luigi. Portage doesn't support reverse dependencies yet. `revdep-rebuild` helps in most cases.
Released upstream adopt changes...
in cvs
