Oops, I didn't know that missing /etc/debian_version was a bug and sent a
PR to certbot on GitHub to support Devuan:

https://github.com/certbot/certbot/pull/4515

It failed on a fresh Jessie install because it hadn't /etc/debian_version,
and I tought that was right for future releases, so I didn't want to
symlink /etc/devuan_version.

With a little change on certbot-auto I was able to successfuly create a
Let's Encrypt certificate from my Devuan box.

Cheers,
Emiliano.

On Sat, Apr 15, 2017 at 8:06 AM, Jaromil <jaromil@???> wrote:

> On Fri, 14 Apr 2017, Gregory Nowak wrote:
>
> > cat: /etc/debian_version: no such file or directory.
> >
> > I can probably put that file back, and all would be good. However,
> > my question is what is still looking for that file during apt-get
> > dist-upgrade, and more to the point, how can I make this message
> > during upgrades stop without bringing back /etc/debian_version?
>
> Devuan does have already its own /etc/devuan_version which can be
> symlinked from /etc/debian_version especially since the correct value
> its jessie for both.
>
> Yet I believe we should file this as a bug as /etc/debian_version is
> not there on new installs. The /etc/debian_version file is checked by
> an enormous quantity of scripts in all sorts of deployements, we have
> encountered this problem also with Vagrant, that I remember. So we
> shall keep that file around and fill it with the Debian version we use
> to fallback packages in each release, that is so far:
>
> Jessie -> Jessie
> Ascii -> Stretch
>
> After Ascii is yet to be seen if we'll keep relying on Debian.
>
> ciao
>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>