Subject: fwupd: Missing sysvinit script

From: Dennis Camera <[email-masked]>
Date: Mon, 19 Jul 2021 10:53:28 +0200

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.

---

From: Mark Hindley <[email-masked]>
Date: Mon, 19 Jul 2021 11:26:15 +0100

Control: tags -1 moreinfo

Dennis,

Thanks for this. It is not software I am farmiliar with, but I have had a quick
look an installed it in a VM.

> To be functional on Devuan it should ship sysvinit scripts and a refresh cron job, instead.

AFAICS the service files are dbus activatable. As such they still work on
Devuan. The thing that is missing is a cron script.

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?

Is there anything else, from a functional perspective, that you expect to
happen?

Thanks.

Mark

---

From: Dennis Camera <[email-masked]>
Date: Mon, 19 Jul 2021 13:15:57 +0200

Dear Mark,

> On 19 Jul 2021, at 12:26, Mark Hindley <[email-masked]> wrote:
> 
> Devuan. 

Oh, it didn’t occur to me that .service files can be launched by anything else than systemd.

> The thing that is missing is a cron script.

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).

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.

> org.freedesktop.fwup service had been started correctly.

Yes, when I execute fwupdmgr, the fwupd daemon is started automatically.

> Is there anything else, from a functional perspective, that you expect to

Currently, I don’t know. I couldn’t get fwupd to work as I wanted to, yet.
At first I thought it was because of the package assuming systemd to be present,
but as it turns out this is not the issue.

Possibly adding a cron job for the refresh process could be seen as an improvement,
but I can imagine that opinions differ on that.

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

Thanks for your assistance.
- Dennis

---

From: Mark Hindley <[email-masked]>
Date: Mon, 19 Jul 2021 12:54:38 +0100

> 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.

> 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.

> Yes, when I execute fwupdmgr, the fwupd daemon is started automatically.

Good!

Thanks.

Closing.

Mark