<ulm> !meta -v bluez <Willikins> ulm: Package: net-wireless/bluez Herd: mobile, pda Maintainer: dev-zero@gentoo.org, betelgeuse@gentoo.org <ulm> ^ ping <dev-zero> ulm: hmm? <ulm> why does bluez now depend on pam unconditionally? <ulm> gives me some trouble with one of my systems which is "pam-free" so far <dev-zero> ulm: because of consolekit <ulm> hm, but pam base isn't needed at build time? <dev-zero> no <ulm> so can't you RDEPEND on pam? ( pambase ) <dev-zero> I'm doing that already * ulm checks again <ulm> RDEPEND="${CDEPEND} sys-auth/pambase[consolekit]" <ulm> ^ from bluez-4.39.ebuild <dev-zero> that's correct, yes <ulm> dev-zero: so where's the USE flag in that dependency? :p <dev-zero> there is none <ulm> o.O <ulm> <dev-zero> I'm doing that already <dev-zero> ah, sorry, I referred to the rdepend, not the use flag :) <dev-zero> ulm: the story is this: dbus uses pam_console's user files in /var/run/console to perform the at_console check for dbus policies <dev-zero> bluetooth uses at_console for letting client tools access the bluetoothd daemon depending on whether it is a local user or not <dev-zero> with pam_console gone it's functionality got replaced by ConsoleKit and pam_ck <ulm> dev-zero: so without pam you can run bluetooth clients only as root? <dev-zero> yes <ulm> hm <dev-zero> or use the plugdev-group hack in the dbus-policy instead <dev-zero> but that somehow makes the whole bluetooth-"security" with entering pins locally pointless <ulm> yeah, but there are several of these problems on systems without pam <ulm> so I think the pam flag should be honored <ulm> and people using -pam (like myself ;-) get what they deserve <dev-zero> hmm <ulm> otherwise it's pointless to have the flag at all <dev-zero> not really, no. There are surely packages which just loose some kind of flexibility without pam <ulm> dev-zero: how about changing the dependency to "pam? ( pambase )" and displaying a big fat warning in pkg_postinst? <dev-zero> I mean: I could add "+pam" to it and a big fat warning for USE="-pam" <ulm> :) <ulm> sounds good <dev-zero> is next release soon enough? <ulm> sure <dev-zero> that would be in 2-3 weeks guessing from their release schedule <ulm> should I open a bug so that you don't forget it? ;) <dev-zero> ulm: would be nice, yes
Is there any patch/trick/workaround to install bluez without pam on pamless system or will I wait 3 weeks to tranfer my files from my phone?
(In reply to comment #1) > Is there any patch/trick/workaround to install bluez without pam on pamless > system or will I wait 3 weeks to tranfer my files from my phone? You may add pambase to /etc/portage/profile/package.provided, "man portage" for an explanation of the file's format.
Bluez-4.40 is out: http://www.bluez.org/bluez-440/
Still not fixed and now bluez-4.41 has been released.
Still not fixed and bluez-4.50 is out.
ebuild for bluez 4.60 on bug #270859 fixes this. It has a consolekit USE flag to select pambase or not. Can we close this bug when the that ebuild get merged?
This was fixed some time ago: *bluez-4.39-r2 (20 Sep 2009) 20 Sep 2009; Nirbheek Chauhan <nirbheek@gentoo.org> +bluez-4.39-r2.ebuild: Add IUSE=consolekit to control pambase dep. Give all rights to users in plugdev only if we're not using ConsoleKit. Also, use +consolekit (upstream defaults)
