Just want to make sure you understand that <release codename> will need to be replaced with jessie or ascii (without the < >).

When devuan was just starting, there was some testing of amprolla that merged the main repos with backports and I got a bit burned by that so I always comment backports even though I know it's OK to just use -t.  Not a problem since I really don't need anything from there.

I don't know if amprolla will recognize and update packages installed directly from Debian. 

Then why would you use Debian repos when it says this in several places on the website:

I'm pretty sure that the backports repo in ascii is pinned so you must use `-t ` to download and no need to comment.  You'd have to ask  on the debian forums whether you would have to comment those lines from their repo.  Probably wouldn't hurt.

Backports can be useful to accommodate newer hardware etc.  But never use Debian or other 3rd party repos like mint or ubuntu.  Use the devuan backports.  All this information is on devuan.org so please have a look there..

That would only be useful if a new user actually bothers to read anything. These days users tend to leap before looking. A garish flashing popup is the only thing that MIGHT grab someone's attention . . .

FYI . . . this is on the download page of the devuan website and I'm pretty sure repeated on the repo pages too.  Those who do not seek will not find:

Sounds like you're on your way!  Let us know how it works out.  FWIW, I use the cli version also.  We'll be adding a page with screenshots for a cli install too.

I'm not quite clear what you are trying to do.  Can you provide a little more information?

This beta is a WIP but very close to finished: https://beta.devuan.org/os/documentatio … e-gui.html.  I will be making some changes later today.

Also please read the RELEASE NOTES on the desktop if you have not already done so

You're right of course.  Devuan users tend to be pretty savvy but I should not assume we all are.  We also tend to be pretty thick-skinned. 

The Debian wiki is quite clear about not mixing repositories: Don't make a FrankenDebian

Why would you think they would be?  It is a _very bad idea_ to use Debian-related packages from other sources on Devuan.

Perhaps someone will step up to do that.

My understanding is that it just fools FF into thinking pulseaudio is there.  It has been discussed off and on for the last several years on the DNG mail list and this very forum so a little search fu might give you some ideas.   I'm still on jessie so no need to go there yet.  Good luck and let us know how it works for you.

OK.  I booted my pretty vanilla beowulf and ran this:

# apt-cache rdepends pulseaudio
pulseaudio
Reverse Depends:
  pulseaudio-equalizer
  firefox-esr
  xpra
  xfce4-pulseaudio-plugin
  surf-display
  speech-dispatcher
  sdrangelove
  scratch
  python3-x2go
  python-x2go
  pulseaudio-utils
  pulseaudio-module-zeroconf
  pulseaudio-module-raop
  pulseaudio-module-lirc
  pulseaudio-module-jack
  pulseaudio-module-gsettings
  pulseaudio-module-bluetooth
  cairo-dock-impulse-plug-in
  projectm-pulseaudio
  plasma-pa
  persepolis
  pavucontrol-qt
  pavucontrol
  pamix
  osspd-pulseaudio
  mpg123
  mpd
  morse
  minimodem
  ltsp-server
  ltsp-client-core
  ltsp-client
  lives
  libpulse0
  libcanberra-pulse
 |kde-telepathy-call-ui
  impressive-display
  gqrx-sdr
  gnome-settings-daemon
  gnome-core
  firefox-esr
  education-ltsp-server
  cinnamon-settings-daemon

xfce4-pulseaudio-plugin and firefox-esr are the ones that will trip me up when I transition to beowulf as my daily driver.

Not sure whether that's possible anymore.  You try installing parts of xfce4 from scratch without the meta package and without recommends/suggests.  If pulseaudio shows up in a package's list of dependencies, you can decide whether to install it or not.  Disclaimer:  My daily driver is still jessie.