| Summary: | net-wireless/bluez-4.101 - !!! newbin: apitest does not exist | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mike Callahan <s2x0nl902> |
| Component: | Current packages | Assignee: | Tiziano Müller (RETIRED) <dev-zero> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bruce, crabbedhaloablution, eugene.shalygin, mobile+disabled, pacho, pda, polidevk.polidevk |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build log
emerge --info output patch to remove abitest from bluez-4.101.ebuild |
||
|
Description
Mike Callahan
2012-06-24 15:49:38 UTC
Created attachment 316181 [details] emerge --info output --- /usr/portage/net-wireless/bluez/bluez-4.101.ebuild 2012-06-23 13:46:55.000000000 +0200 +++ /usr/local/portage/net-wireless/bluez/bluez-4.101.ebuild 2012-06-24 20:11:35.330868861 +0200 @@ -119,7 +119,7 @@ dobin simple-agent simple-service monitor-bluetooth newbin list-devices list-bluetooth-devices rm test-textfile.{c,o} || die # bug #356529 - for b in apitest hsmicro hsplay test-* ; do + for b in hsmicro hsplay test-* ; do newbin "${b}" "bluez-${b}" done insinto /usr/share/doc/${PF}/test-services Then it compiles. For me this version doesn't work at all. Kernel modules are loaded, but the bluetooth dongle stays dead. No error logs either. I downgraded to the last working version 4.99. I don't think the patch is correct, since, apparently, the build system does create an `api-test' under certain circumstances. (In reply to comment #2) > I don't think the patch is correct, since, apparently, the build system does > create an `api-test' under certain circumstances. At least the "apitest" python script was removed from the "test" directory in the source package. There could be replacements in some way? (In reply to comment #1) > For me this version doesn't work at all. Kernel modules are loaded, but the > bluetooth dongle stays dead. No error logs either. I downgraded to the last > working version 4.99. I've been having the same issue on my ~amd64 laptop. The issues was reported in bug 423513 The problem is that nothing is starting bluetoothd. I've struggled with this for days thinking this issue was related to the recent polkit upgrade and some sort of ownership / permission issue. But since the polkit issues now seem to have been resolved, I tried hunting down a solution. The only way I seem to get bluetooth again running was to downgrade to 4.99 I hope the devs can get this sorted out soon. Created attachment 316621 [details, diff]
patch to remove abitest from bluez-4.101.ebuild
Sorry I didn't properly get my comments attached with the patch. Here goes: apitest was only compatible with bluez 3.x so it doesn't make sense to have it in any bluez 4.x release, so here's a patch This does nothing to alleviate the error of upstream's decision to remove the udev activation of the bluetooth daemon here: http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=2ea98a6a043710ad4958355b62c682b4767f292e We have bug 423513 addressing that; hopefully we can get systemd removed from udev for use in Gentoo because these types of issues will probably come up on many other pkgs. (In reply to comment #6) > Sorry I didn't properly get my comments attached with the patch. Here goes: > > apitest was only compatible with bluez 3.x so it doesn't make sense to have > it in any bluez 4.x release, so here's a patch > Where did you get that information about it being only compatible with bluez-3.x? Thanks for the info > This does nothing to alleviate the error of upstream's decision to remove > the udev activation of the bluetooth daemon here: > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > h=2ea98a6a043710ad4958355b62c682b4767f292e > > We have bug 423513 addressing that; hopefully we can get systemd removed > from udev for use in Gentoo because these types of issues will probably come > up on many other pkgs. (In reply to comment #7) > (In reply to comment #6) > > Sorry I didn't properly get my comments attached with the patch. Here goes: > > > > apitest was only compatible with bluez 3.x so it doesn't make sense to have > > it in any bluez 4.x release, so here's a patch > > > > Where did you get that information about it being only compatible with > bluez-3.x? Thanks for the info > > > This does nothing to alleviate the error of upstream's decision to remove > > the udev activation of the bluetooth daemon here: > > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > > h=2ea98a6a043710ad4958355b62c682b4767f292e > > > > We have bug 423513 addressing that; hopefully we can get systemd removed > > from udev for use in Gentoo because these types of issues will probably come > > up on many other pkgs. From Johan Hedberg. I think he's one of the bluez devs. I remembered him from the ml (I helped maintain bluez on my previous distro), and glad to see you just posted the question there. Johan told me about the udev issue, "if there's disagreement this should be taken to the linux-bluetooth mailing list." Told him I'm not a Gentoo dev or maintainer of bluez so I'd wait to discuss it with you. Now you've posted so we'll see what they say. + 30 Jun 2012; Pacho Ramos <pacho@gentoo.org> bluez-4.101.ebuild: + Apitest is no longer provided, bug #423331 by Mike Callahan and others. + |
