Bug 754523
| Summary: | bluez-compat either in violation of the packaging guidelines or lacking native systemd units | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> |
| Component: | bluez | Assignee: | Bastien Nocera <bnocera> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | bnocera, dwmw2, kalevlember, marcel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | bluez-5.8-1.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-15 11:19:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 751869 | ||
|
Description
Jóhann B. Guðmundsson
2011-11-16 18:06:41 UTC
Don't care. It's in -compat because they shouldn't be needed, but people still request them. I really don't care whether somebody ports them or they get removed. Hum perhaps it's best to hear from someone who requested it before dropping it which might be? If we drop pand then /etc/sysconfig/network-scripts/ifup-bnep will want to be fixed to handle whatever replaces it. It's also worth checking that we have a viable replacement for the pand init script which makes it run in NAP mode. The other thing I can think of that bluez-compat still gets used for is to create a persistent mapping from /dev/rfcommX to a specific device which gets connected on demand. I have Bluetooth serial ports like this, for example. They *are* just /dev/rfcomm0 and there's no faffing to set them up. As long as that is supported and the replacement for /etc/bluetooth/rfcomm.conf is properly documented, and PAN client/server support is supported, I think we should be able to get away with dropping bluez-compat. (In reply to comment #3) > If we drop pand then /etc/sysconfig/network-scripts/ifup-bnep will want to be > fixed to handle whatever replaces it. > > It's also worth checking that we have a viable replacement for the pand init > script which makes it run in NAP mode. I'll see if I cant convert that to a unit > > The other thing I can think of that bluez-compat still gets used for is to > create a persistent mapping from /dev/rfcommX to a specific device which gets > connected on demand. I have Bluetooth serial ports like this, for example. They > *are* just /dev/rfcomm0 and there's no faffing to set them up. Can this be handled via Udev rule which in turn triggers a unit? > As long as that is supported and the replacement for /etc/bluetooth/rfcomm.conf > is properly documented, and PAN client/server support is supported, I think we > should be able to get away with dropping bluez-compat. Roger that let's see if I cant cook something up This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 The -compat subpackage is now gone in rawhide (F20) as part of the BlueZ 5 update. http://pkgs.fedoraproject.org/cgit/bluez.git/commit/?id=e321c716dddf55724776b8686de01cd7f45cbc4a |