I just ran into this doing a debootstrap install of ascii. Here's a way around it. The needed packages are in ascii-proposed. When they move into the main ascii repo, this will no longer be a problem.

In chroot: add the following line to /etc/apt/sources.list (note that it's /devuan not /merged like the others.)

deb http://pkgmaster.devuan.org/devuan/ ascii-proposed main

Then run

apt-get update
apt-get -t ascii-proposed install util-linux libfdisk1

Then you can install other things. I have no idea what's missing in your system now. I had to do the above before I could install the kernel. You probably need to run upgrade and dist-upgrade again, maybe apt --fix-missing, or maybe you'll get other instructions.

I have a partial answer to the original dilemma. I made a live usb of devuan ascii (and udev), with persistence. There's no 70-persistent-net.rules in the live isos by design, and there's none in my ascii anyway. Normally (jessie and older) with persistence, the one that gets created at boot sticks around, and you have to either delete it or change your settings to eth1, 2... or wlan1, 2 (I think I've gone up to 8 in the past.)

This particular system has wicd on it, and there are settings for default wired and wireless interfaces. They're set to eth0 and wlan0. I added net.ifnames=0 so that the old names will be used.

Booted one laptop and was automatically connected with the wire. Wicd saw the nearby wireless signals.
Booted another laptop and was automatically connected. Wicd worked, too.
In both cases, the only interfaces were eth0 and wlan0. They did not increment.

Explanation: Hand-waving-argument, magic. I don't know. But I think you'll be ok when you move your system to different hardware.

Bug me in a couple of weeks to see if I tried it with eudev yet.

Huh? What's missing? What extra stuff is disturbing you? I never noticed a difference.

To enable multi-arch:

dpkg --add-architecture i386

Then you should be able to install the i386 versions of packages.

It's safer if you use codenames. Use "jessie" instead of "stable" and "ascii" rather than "testing." When ascii becomes the stable release, you can change sources.list to say "ascii" instead of "jessie." That way, you get to decide when you do the dist-upgrade instead of running into it when it happens.

I know we're drifting off topic here, but this is relevant to the drift and potentially very important:
https://yro.slashdot.org/story/17/11/20 … -keystroke

@golinux: I like the greens better than the roots.

All the installer isos must be used with auto.mirror.devuan.org (or some-country-code.mirror.devuan.org or packages.devuan.org). They do not have the signing key for amprolla3 (pkgmaster.devuan.org). If/when there's a point-release of jessie, that situation will be remedied.

Instructions for putting the image on the device are in the README.txt found in the same directory as the images. But I will assume that you already know how to do that, because you did it with Debian. Say a little more about what you did and what doesn't work, and maybe someone will have a solution.

'update-rc.d remove' will remove the symlinks. You do not need to remove the init script. I'm not sure if the symlinks will be regererated with normal updates, but. I just checked, and wicd is still installed here and turned off since I installed the system almost two years ago.

Here's a bug report. I guess you can ignore the warning.
https://lists.debian.org/deity/2015/10/msg00085.html

Check your version of apt. It's supposed to be fixed in 1.1. Jessie has 1.0.9 and ascii should have 1.4.

dpkg -l apt

The 10, 100 and 500 are priority numbers. All except the 500 are there because I pinned those repos at lower priority to prevent accidental install from the wrong repo. However, I haven't actually tested that. I won't share my full sources.list because it would be hazardous for anyone to use it. Including me. It's like that only so I can see what versions are in which release. One of these days I'll need to comment out all but the jessie repos and do another upgrade. Or maybe not - I really want to switch my main system to ascii soon.

I'll delete those posts from that other thread.

I'm sure there were changes upstream from 1.6 to 1.75 in debian. I think the only changes that devuan made to 1.75 was to remove the dependency on libsystemd0, but it may have been more involved than that. The only way to know for sure what changes were made would be to compare the source code of both packages.

One possible simple solution is to try one of the generic drivers. I think you'll find them at the end of the list of drivers when you're adding a printer in the cups admin. (http://localhost:631)

Right now, all the devs are focused on ascii, so getting changes/fixes in jessie or doing anything with wheezy packages is unlikely to happen. There may be a way to get your printer working by editing some cups config files, but I don't know my way around that enough to even give you a hint.