bluez-utils started storing link keys in ASCII text and using a device name cache with version 2.16. The storage directory path was hardcoded to /var/lib/bluetooth. Version 2.17 allows the storage directory path to be set through localstatedir when running configure. This is set to /var/lib/lib/bluetooth when using econf. Reproducible: Always Steps to Reproduce: 1. emerge bluez-utils-2.17: # emerge -v =bluez-utils-2.17 2. start bluetooth services: # /etc/init.d/bluetooth start 3. scan for nearby bluetooth devices: # hcitool scan 4. Check /var/lib to see where device name cache has been created: # ls -l /var/lib Actual Results: There is another lib directory under /var/lib which contains a bluetooth directory. i.e. /var/lib/lib/bluetooth Expected Results: Created a bluetooth directory under /var/lib. i.e. /var/lib/bluetooth Portage 2.0.51.19 (default-linux/x86/2004.2/gcc34, gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.5 [2.3.5 (#1, Jun 4 2005, 10:02:03)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.2.3-r5, 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://192.168.1.5/gentoo/ http://premium.planetmirror.com/pub/gentoo/ http://mirror.pacific.net.au/linux/Gentoo/" LANG="en_AU" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/opt/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.1.5/gentoo-portage" USE="x86 X aalib alsa apache2 avi bash-completion berkdb bitmap-fonts bonobo cdr crypt cups curl dbus divx4linux dvd dvdr eds emboss encode esd flac font-server foomaticdb fortran gdbm gif gnome gnutls gpm gstreamer gtk gtk2 gtkhtml guile hal imagemagick imap imlib jack java jpeg junit libg++ libwww mad mikmod mmx mono motif mozilla mp3 mpeg mysql ncurses nls nptl nptlonly odbc ogg oggvorbis opengl oss pam pdflib perl pic png ppds python quicktime readline ruby samba sdl slang spell sqlite sse sse2 ssl svga tcltk tcpd theora truetype truetype-fonts type1-fonts usb vorbis xine xml xml2 xmms xprint xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS, LINGUAS
Created attachment 61160 [details, diff] patch to bluez-utils-2.17.ebuild Patches bluez-utils configure script to use ${localstatedir}/bluetooth (/var/lib/bluetooth) instead of ${localstatedir}/lib/bluetooth (/var/lib/lib/bluetooth).
fixed in a simplier way. commiting to 2.17-r1. thanks for your report!
Re-opening due to new ebuild not emerging for me. Here is the output: supergroove / # emerge -v =bluez-utils-2.17-r1 Calculating dependencies ...done! >>> emerge (1 of 1) net-wireless/bluez-utils-2.17-r1 to / >>> md5 files ;-) bluez-utils-2.17.ebuild >>> md5 files ;-) bluez-utils-2.12.ebuild >>> md5 files ;-) bluez-utils-2.10-r1.ebuild >>> md5 files ;-) bluez-utils-2.17-r1.ebuild >>> md5 files ;-) bluez-utils-2.16.ebuild >>> md5 files ;-) bluez-utils-2.16-r1.ebuild >>> md5 files ;-) bluez-utils-2.15.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/bluez-utils-2.3-rfcomm_fflush.patch >>> md5 files ;-) files/bluez-utils-2.10-handsfree.patch >>> md5 files ;-) files/pin.sample >>> md5 files ;-) files/bluez-utils-2.3-bluepin.patch >>> md5 files ;-) files/bluez-utils-2.3-bluepin-gtk2.patch >>> md5 files ;-) files/digest-bluez-utils-2.10-r1 >>> md5 files ;-) files/digest-bluez-utils-2.16-r1 >>> md5 files ;-) files/digest-bluez-utils-2.17-r1 >>> md5 files ;-) files/2.15-bluepin.patch >>> md5 files ;-) files/digest-bluez-utils-2.12 >>> md5 files ;-) files/digest-bluez-utils-2.15 >>> md5 files ;-) files/digest-bluez-utils-2.16 >>> md5 files ;-) files/digest-bluez-utils-2.17 >>> md5 files ;-) files/bluetooth.rc >>> md5 files ;-) files/2.16/bluetooth.rc >>> md5 files ;-) files/2.10-r1/pin >>> md5 files ;-) files/2.10-r1/pin-helper.sh >>> md5 files ;-) files/2.10-r1/bluetooth.rc >>> md5 src_uri ;-) bluez-utils-2.17.tar.gz >>> Unpacking source... >>> Unpacking bluez-utils-2.17.tar.gz to /opt/tmp/portage/bluez-utils-2.17-r1/work * Applying 2.15-bluepin.patch ... [ ok ] >>> Source unpacked. * econf: updating bluez-utils-2.17/config.guess with /usr/share/gnuconfig/config.guess * econf: updating bluez-utils-2.17/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-cups --enable-alsa --disable-pcmcia --disable-bluepin --enable-dbus --enable-usb --disable-initscripts --enable-obex --enable-hid2hci --enable-bcm203x --localstatedir=/var emake configure: WARNING: you should use --build, --host, --target checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking whether to enable maintainer-specific portions of Makefiles... no checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of i686-pc-linux-gnu-gcc... none checking whether i686-pc-linux-gnu-gcc accepts -fPIE... yes checking for a BSD-compatible install... /bin/install -c checking for bison... bison -y checking for flex... flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking build system type... Invalid configuration `emake': machine `emake' not recognized configure: error: /bin/sh ./config.sub emake failed !!! Please attach the config.log to your bug report: !!! /opt/tmp/portage/bluez-utils-2.17-r1/work/bluez-utils-2.17/config.log !!! ERROR: net-wireless/bluez-utils-2.17-r1 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message.
Created attachment 61949 [details] config.log as requested by ebuild error message
What does `grep Header /usr/portage/net-wireless/bluez-utils/bluez-utils-2.17-r1.ebuild` say? It needs to be at least version 1.2 of the ebuild. If it is 1.1, please emerge --sync and recheck.
This issue was fixed in bug #97029.
