Bug#950520: blueman: Ship blueman-mechanism.service under /lib/systemd/system

2020-05-23 Thread Christopher Schramm
Control: close 950520 Control: fixed 950520 2.1.3-1 I'm not sure if moving '/usr/lib/systemd/user/blueman-applet.service' to '/lib/systemd/user/blueman-applet.service' is the correct solution here. No, it's not. It caused #961215 and is thus reverted in 2.1.3-2. According to the systemd.unit

Bug#950520: blueman: Ship blueman-mechanism.service under /lib/systemd/system

2020-05-22 Thread Tomasz Nitecki
Control: reopen 950520 Control: block 961215 by 950520 Hey, I'm not sure if moving '/usr/lib/systemd/user/blueman-applet.service' to '/lib/systemd/user/blueman-applet.service' is the correct solution here. According to the systemd.unit(5) man [1], the user unit search path contains '/usr/lib/sys

Bug#950520: blueman: Ship blueman-mechanism.service under /lib/systemd/system

2020-02-02 Thread Nicolas Braud-Santoni
Package: blueman Version: 2.1.1-1+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, On my system, blueman shipped blueman-mechanism.service to /usr/lib/systemd/system/ (and is the only package to use that directory) While systemd does find it, it is a fairly s