:: [devuan-dev] bug#593: marked as don…
Top Page
Delete this message
Reply to this message
Author: Devuan bug Tracking System
To: Mark Hindley
Subject: [devuan-dev] bug#593: marked as done (fwupd: Missing sysvinit script)
Your message dated Mon, 19 Jul 2021 12:54:38 +0100
with message-id <YPVn/vF90pMOQEGF@???>
and subject line Re: bug#593: fwupd: Missing sysvinit script
has caused the Devuan bug report #593,
regarding fwupd: Missing sysvinit script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@???

593: https://bugs.devuan.org/cgi/bugreport.cgi?bug=593
Devuan Bug Tracking System
Contact owner@??? with problems
Package: fwupd
Version: 1.5.7-4

Dear maintainer,

The fwupd package on Devuan only ships systemd services and timers.
To be functional on Devuan it should ship sysvinit scripts and a refresh cron job, instead.

I verified this "bug" to occur on beowulf and chimaera.
On Mon, Jul 19, 2021 at 01:15:57PM +0200, Dennis Camera wrote:
> Now that I’m thinking more about this, one can argue if the package should install e cron job by default.
> Maybe some users wouldn’t want to have fwupd auto-update (like apt-get also
> doesn’t auto-update by default).

AFAICS, the systemd timer to update motd requires manual activation by the
sysadmin, so Debian maintainers agree with you on this! See data/motd/README.md
in the source.

> Maybe just adding a section on how to create such a cron job to README.Debian or
> adding a debconf question would be the better choice.

Devuan doesn't currently fork this package, so maybe the best solution is to
submit a cron fragment to Debian for inclusion in contrib or similar.

> > I ran '/usr/bin/fwupdmgr refresh' from the command line without issue or
> > error. After running this, the output of 'busctl' showed that the
> > org.freedesktop.fwup service had been started correctly.
> >
> > Can you verify that?
> Yes, when I execute fwupdmgr, the fwupd daemon is started automatically.


> As far as I’m concerned this bug can be closed.