Steve,

Apparently the issue with unattended-upgrades is that Devuan support is in the Debian source, but the source also needs to be recompiled on a Devuan system.

I have added preliminary support for us doing that to the Devuan jenkins instance. Could you please test these artifacts and report back?

Thanks

Mark

OK, then if you want to use mx.devuan.org directly, then you will need to make your IP address reverse resolvable to your hostname, or at least to something.

~% host 151.62.1.237                                                   
Host 237.1.62.151.in-addr.arpa. not found: 3(NXDOMAIN)

It is possible that mx.devuan.org is more picky than debian's reportbug mx in this respect.

We are considering setting up another SMTP server for Devuan, so we might be able to look at relaxing this if it doesn't produce too much spam.

So, it sounds as if networking is not properly set up on this system.

You need a valid host and domain. What does /etc/hostname contain?

Or do you you have an SMTP server running? In which case you should be using that to send through.

Hi,

Is the Default-release setting actually required? You only appear to have beowulf sources.

I have a beowulf VM that installs security updates fine without Default-release being set. Both beowulf and beowulf-security being priority 500.

If you want to report this as a bug, then amprolla is the correct package to report against using reportbug. It is a pseudo-package so you will need to put 'other' at the first package prompt to get to the list of available pseudopackages.

Mark