Hi,

Quoting Johannes Schauer Marin Rodrigues (2023-09-16 09:23:43)
> On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues
> <jo...@debian.org> wrote:
> > after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems 
> > that
> > this new version changed the init script for a systemd unit where the latter
> > ignores the contents of /etc/default/mini-httpd.
> > 
> > If that is intentional and not an oversight, there should at least be a
> > NEWS entry so that users upgrading to 1.30-4 learn about this breaking
> > change and are also told how to convert their existing configuration to
> > the new style.
> > 
> > If possible it would of course be nice if the systemd service would not 
> > break
> > user's setups and would continue to consume /etc/default/mini-httpd.
> 
> this issue has now made the mmdebstrap jenkins job fail for 10 days in a row:
> 
> https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/
> 
> Even if you do not have time to fix this soon, could you maybe advise on how
> you plan to fix this? Is the behaviour change introduced by the last upload
> supposed to stay and I should adjust my setup accordingly? Or will you restore
> compatibility with existing setups using /etc/default/mini-httpd so that I
> need to do nothing and just wait for an upload fixing this?

I asked in #debian-systemd and the fix could be as simple as setting the
following in the .service file:

EnvironmentFile=-/etc/default/mini-httpd

Can you confirm?

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to