I'm happy to sponsor kblueproximity, upload it for you etc.

Took a quick look at your prelim packaging, and made some minor
changes. See github.com/barak/kblueproximity where I evicted debian/*
from branch master and put it in a new branch debian/latest, where I
updated some stuff.

Two issues I see before it's ready for prime time.

First, since it is a daemon, it would be appropriate to have a systemd
user system unit for it, so you can just systemctl --user start
kblueproximity or whatever. That's a minor issue though.

Second, a more major one: I'm running Gnome and it doesn't seem to work for me.

$ kblueproximity
Creating new config directory '/home/barak/.kblueproximity'.
Creating new configuration.
Using config file 'standard'.
Traceback (most recent call last):
  File "<frozen runpy>", line 203, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/share/kblueproximity/kblueproximity/__main__.py", line
15, in <module>
    main()
    ~~~~^^
  File "/usr/share/kblueproximity/kblueproximity/__main__.py", line 11, in main
    raise SystemExit(run_app())
                     ~~~~~~~^^
  File "/usr/share/kblueproximity/kblueproximity/ui/app.py", line 552,
in run_app
    p = Proximity(config[1])
  File "/usr/share/kblueproximity/kblueproximity/core.py", line 40, in __init__
    self.logger.configureFromConfig(self.config)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/usr/share/kblueproximity/kblueproximity/logger.py", line 75,
in configureFromConfig
    self.enable_syslogging(config['log_syslog_facility'])
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/kblueproximity/kblueproximity/logger.py", line 30,
in enable_syslogging
    self.syslog_facility = self.getFacilityFromString(facility)
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/share/kblueproximity/kblueproximity/logger.py", line 27,
in getFacilityFromString
    return log_dict[facility]
           ~~~~~~~~^^^^^^^^^^
KeyError: "'local7'"

Reply via email to