I wish you had been able to solve your dilemma.  I'm curious if your preferred setup is still possible on Stretch.

Devuan's main concern is to provide a stable base system.  At times there has been discussion of providing only that and leaving desktop development to the derivatives.  That being said there were developers who stepped forward to provide functional desktop options for ASCII.

Well, perhaps your predicament might be incentive to learning those skills. 

Above every message box there is a line of BBCode options in this order:
underline, bold. italic, inline code, delete, insert, emphasis, color, header, code (that's the one you want), quote, url, and list options.  Highlight the section you want to format and click on the option you want to use.  Done.

Because Devuan users should be aware that packages installed from Ubuntu could have "unintended consequences" on their Devuan system.  It is a bit like Russian roulette.  But your box, your choice.

Not the Devuan team.   https://pkginfo.devuan.org/cgi-bin/d1pk … elease=any  Talk to Debian.  We have not touched that package.

Ozi rocks!

You do too but this is Ozi's moment . . .

I am very tired so this will be short.

The package in question should be in jessie-security by now.

Also look at the sources options on this page.

The reason auto.mirror is still mentioned is because that is the repo used on the install isos.  But the warning that it is deprecated is also there.

Since your IP has been cleared I hope you won't get snaplocked again.

Thanks Ralph . . . getting back on topic . . . policykit-1 has been repackaged and is now available for testing at jessie-proposed-security main.  Centurion_Dan suggested using
deb http://pkgmaster.devuan.org/devuan but I don't see why deb.devuan.org wouldn't work as well.  Maybe KatolaZ needs to set up that new repo on the mirror.  For those who don't know . . . auto.mirror is now deprecated.

@dev-1-dash-1 . . . as per your note on #d1g-users . . . you are not banned.  You are a welcome member of this forum.  It looks like you IP was caught by our snaplock as "dubious".  I will clear it and you should be back.  Maybe ralph.ronnquist will stop by to explain the technical reasons you might have been slammed.  Or you can search this forum where this has been discussed elsewhere several times.

Please check out the links in this post.   That usually gets most of these backend issues sorted.

@a_flj_ . . . does the same thing happen on Debian Stretch?  If so, please file a bug upstream.  If it's Devuan specific, feel free to provide a patch.

I moved it back and removed CrowZ from the subject so more people might take a look.

Yes, just ask your question and stay logged for an answer.   You can read the logs here or here but if you are not logged in you may not receive a response.