Dear D1rs,

Since we are talking of creating a local or LAN Devuan mirror, I
thought that posting a working configuration for apt-mirror could be
found useful. Please find at the bottom an example of what you should
have in your /etc/apt/mirrors.list in order to get a full local Devuan
repo for amd64, i386, and sources. You can use deb.devuan.org instead
of pkgmaster.devuan.org, if you like, or any of the package mirrors
listed at:

  https://pkgmaster.devuan.org/mirror_list.txt

Notice that the program apt-mirror must be executed by the user
"apt-mirror", who should have rwx access to the base_path specified in
the mirrors.list file. For more information, man apt-mirror

Useful information on setting up a Devuan package mirror can be found
at:

  https://pkgmaster.devuan.org/devuan_mir … hrough.txt

If you want to setup a *public* Devuan package mirror instead, please
follow the instructions reported in the walkthrough and get in touch
as specified therein.

HTH

KatolaZ

  -+-+-+-

############# config ##################
#
# base_path is the local path where your mirror will be created
set base_path    /srv/apt-mirror
#
# set mirror_path  $base_path/mirror
# set skel_path    $base_path/skel
# set var_path     $base_path/var
# set cleanscript $var_path/clean.sh
# set defaultarch  <running host architecture>
# set postmirror_script $var_path/postmirror.sh
# set run_postmirror 0
set nthreads     20
set _tilde 0
#
############# end config ##############

# mirroring package sources
deb-src http://pkgmaster.devuan.org/merged ascii main contrib non-free

# mirroring binary architectures
deb-amd64 http://pkgmaster.devuan.org/merged ascii main contrib non-free main/debian-installer
deb-i386  http://pkgmaster.devuan.org/merged ascii main contrib non-free main/debian-installer
deb-amd64 http://pkgmaster.devuan.org/devuan ascii main contrib non-free main/debian-installer
deb-i386  http://pkgmaster.devuan.org/devuan ascii main contrib non-free main/debian-installer

# cleanup obsolete stuff
clean http://pkgmaster.devuan.org/merged

I issued $locate systemd
and got 200 lines of output, including
/etc/systemd/system/* (23 files)
/lib/systemd/system/* (60 files)
/lib/x86_64-linux-gnu/libsystemd.so.0 (and 0.17.0)
/usr/lib/systemd (25 files)
/usr/bin/deb-systemd-helper ((and deb-systemd-invoke)
/var/lib/systemd/deb-systemd-helper-enabled/* (68 files)
/var/lib/dpkg/info/libsystemd):amd64* (5 files)

This seems a lot to me.  Please could you confirm that an ascii
installation should contain 200 systemd files as part of a normal
ascii installation.  Sorry to trouble you if these are trivial
questions, but they feel far from that.
Many thanks
leloft

Most of those "alarming" files are just systemd units files, put there
by daemons/packages/utilities who "also" support systemd in a way or
another. So they are not alarming but just *totally* *harmless* if you
don't have a running systemd as PID 1, since only systemd understands
and can run them.  It would be *totally* *useless* (and utterly
*stupid* IMHO) to fork, rebuild, and maintain a few more hundred
packages only because they happen to provide a systemd unit file for
those systems where systemd is used.

libsystemd0 is used by some daemons to verify if systemd is running or
not. If it's not, libsystemd is *totally* *harmless*.

HND

KatolaZ