Sunil Mohan:
> Daniel, thank you for the bug report.
> 
>> Verified. It seems this was missed in the switch from individual
>> debhelper calls to dh in debian/rules.
>>
>> Thanks very much for reporting this. Will fix ASAP.
> 
> Thank you for the quick response and fix. It would you really nice to
> have the fixed package uploaded soon as we are planning to show Mumble
> during FreedomBox Demo on Oct 30.  FreedomBox is currently running on
> sid :(

I'll do my best.  I'm trying to track down an issue with dpkg-buildflags
concerning one file being shipped that may partially be missing the FORTIFY
flag.  At least some functions are fortified but there doesn't seem to be a
good verification tool to know if lintian is reporting a false-positive or
if there's a QMAKE file missing dpkg-buildflags.

>> I have a systemd unit file written for mumble-server, BTW, but I'm
>> unclear how to include it alongside the init script. If anyone has a
>> hint about that, please send it to this bug report. Thanks.
> 
> The init script and systemd unit should both be shipped.  systemd will
> simply ignore the init script when a unit with the same name is
> present[1].  (If you want a different name to the systemd unit that is
> possible too with 'Alias=' option).
> 
> After you are done with basic stuff in the unit file, consider adding
> security features to the unit file[2].  This will bring many of the
> security advantages of containers without containers.  This will be
> pretty sweet thing for FreedomBox :)

There are a few wrinkles with shipping a systemd unit file.

 - There's a bug with mumble-server startup under systemd and
   upstart (#780300).  You can see the service file I created
   in testing the bug here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;msg=49;filename=mumble-server.service;bug=780300
   Using a setting of "host=::" is a workaround, but I don't
   consider that a true solution to the bug.

 - mumble-server ships an /etc/default/mumble-server file to
   disable the daemon by default, and there's no clean way
   under systemd to disable a unit based on the contents of an
   environment variable in a file.

https://wiki.ubuntu.com/SystemdForUpstartUsers#A.2BAC8-etc.2BAC8-default_files_which_enable.2BAC8-disable_jobs

 - As discussed on [debian-devel] in the "init script, installed but
   not activated" thread, it's tricky to ship a systemd service file
   that isn't active by default.

  -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to