Hide Forgot
You currently ahave 96 open bugs, dating back to 2010, to which you have not responded at all. As such, I am now starting the unresponsive package maintainer policy steps as per https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers, so deem this as step #2: filing a bug. For a search result of all bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=assignee%3Anushio%40fedoraproject.org&list_id=1990738 Please respond to this bug as soon as possible, or I will proceed with the policy.
Hi Patrick. I'm still alive, I retired ownership of the package as well as the package. Sorry for being unresponsive. I'm just caught up in too much real life work to get anything done for Fedora nowadays. If anyone else is interested in Blueman, there's a fork available, but I haven't had a chance to test it out and see if it works, but it definitely doesn't work with Bluez 5, yet. [1] https://github.com/cschramm/blueman
Hi Juan, No problem. Please note that you have not orphaned it for all branches (f18/f19), and as such all bugs still get assigned to you: https://admin.fedoraproject.org/pkgdb/acls/name/blueman Could you please orphan those, and put a comment in all tickets saying this is broken and they can package the fork if they want, closing them? Thanks, and sorry for the hassle. Patrick
Done. I had orphaned it only for the recent Fedoras but now it's orphaned in F17, F18, F19 and F20+ I'm notifying Christopher Schramm about the old bugs, as he's the new upstream Blueman Maintainer. If Blueman 2.0 is ever released with functional BlueZ 5.0 support, I'll look into re-packaging it into Fedora.
As the packager has been responding, I will close this bug.