When kdegraphics was upgraded from 3.1.3 to 3.1.4, kamera did not get built even though a useable version of gphoto2 is installed. Kamera was built and working in version 3.1.3 of kdegraphics. Side Note: I've noticed several versions of kdegraphics has been troublesome when it comes to building kamera. Reproducible: Always Steps to Reproduce: 1. Add gphoto2 to your use flags 2. emerge kdegraphics 3. Actual Results: kdegraphics was built and installed but the kio slave for kamera was not built and installed. Expected Results: Built and installed the kamera kio slave. Portage 2.0.49-r13 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r7) ================================================================= System uname: 2.4.20-gentoo-r7 i686 AMD Athlon(tm) processor Gentoo Base System version 1.4.3.10p1 distcc 2.9 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.2 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -mmmx -m3dnow -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /usr/X11R6/lib/X11/xkb /etc/env.d" CXXFLAGS="-march=athlon-tbird -mmmx -m3dnow -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/local/share/data/pub/linux/gentoo/distfiles" FEATURES="sandbox autoaddcvs ccache distcc userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j" PKGDIR="/usr/local/share/data/pub/linux/gentoo/packages/athlon-tbird" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/share/data/pub/linux/gentoo/portage" SYNC="rsync://charge.electrostatic.org/gentoo-portage" USE="x86 oss apm avi crypt foomaticdb gif jpeg libg++ mpeg ncurses pdflib png spell truetype xv zlib gdbm berkdb slang readline arts tetex java mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt motif opengl 3dnow alsa cdr cups dga -encode evms2 -gnome gphoto2 gtk2 kde ldap -mad -mikmod mmx -nls offensive pda quicktime svga xml xml2 xmms samba tcltk tiff v4l xvid"
Created attachment 19338 [details] portage log for kdegraphics 3.1.4 The output shows that kamera was not selected for building and there is no indication why.
What does your config.log from the workdir show? It may give us some insight into why it wasn't set to compile kamera.
Created attachment 19822 [details] kdegraphics-3.1.4 config.log Here is copy of config.log. I had to run ebuild with the 'compile' option to regenerate the config.log. This time it showed kamera would be compiled, however, the kamera kio slave still did not get installed after running ebuild with the 'package' option. I wouldn't think anything changed for the configure process to now say kamera would be built but something had to change. The only thing that I have done is upgrade packages on the system. The kernel hasn't been changed so I know it wouldn't be the cause of the problem. Interesting, I took a look at the package tbz2 file and it shows the kamera kio slave files are in it but they were not installed on my system. Here are the kamera files in the tbz2: ./usr/kde/3.1/lib/kde3/kcm_kamera.la ./usr/kde/3.1/lib/kde3/kcm_kamera.so ./usr/kde/3.1/lib/kde3/kio_kamera.la ./usr/kde/3.1/lib/kde3/kio_kamera.so ./usr/kde/3.1/share/doc/HTML/en/kamera/ ./usr/kde/3.1/share/doc/HTML/en/kamera/common ./usr/kde/3.1/share/doc/HTML/en/kamera/index.cache.bz2 ./usr/kde/3.1/share/doc/HTML/en/kamera/index.docbook ./usr/kde/3.1/share/applnk/Settings/Peripherals/kamera.desktop ./usr/kde/3.1/share/services/kamera.protocol
I ran 'emerge -K kdegraphics' this round to force emerge to use the package file and now the kamera components are installed. Any ideas what might of caused this behavior?
Wow, what a strange bug. I dunno if it's a portage related thing or not. I wonder if it has something to do with a cached copy of the ebuild from the previous attempt?
Who knows. If you want to keep this bug open and do some more research, that's fine. Just let me know if you need so info. Otherwise, you can just close the bug because I don't think we will find the cause of the original bug.
unable to reproduce - at least with the 3.2 series. closing as fixed.
