Merge branch 'void-linux:master' into fde-musl-link

Author: kz6wk9

README.md

@@ -13,7 +13,7 @@ Void packages:
 
 - `mdBook`
 - `findutils`
-- `pandoc`
+- `lowdown` (version 0.8.1 or greater)
 - `texlive`
 - `perl`
 - `perl-JSON`

res/build.sh

@@ -6,20 +6,33 @@
 set -e
 PATH="$PWD/res:$PATH"
 
+if [ -z "$SOURCE_DATE_EPOCH" ]; then
+    export SOURCE_DATE_EPOCH=$(git log --pretty='%ct' -1)
+    if [ -z "$SOURCE_DATE_EPOCH" -a "$BUILD_MANPAGES" = 1 ]; then
+      echo "git or SOURCE_DATE_EPOCH are needed to build man pages!"
+      exit 1
+    fi
+fi
+
 # Build HTML mdbook
 echo "Building mdBook"
 mdbook build
 
-
 if [ "$BUILD_MANPAGES" = "1" ]; then
     # Build mandoc version
     echo "Building man pages"
-    mkdir -p mandoc
     cd src
 
     find . -type d -exec mkdir -p "../mandoc/{}" \;
+
     find . -type f -name "*.md" -exec sh -c \
-        'file="{}"; filew="${file%.md}"; pandoc -V "title=${filew##*/}" -V section=7 -V "header=Void Docs" -s -o "../mandoc/${filew}.7" "$file"' \;
+      'file="{}"; filew="${file%.md}"; \
+          man_date="$(git log --pretty=%cs -1 "$file" 2>/dev/null || date -d "@$SOURCE_DATE_EPOCH" +%F)";
+          lowdown -Tman \
+          ${man_date:+-m "date: $man_date"} \
+          -m "title: ${filew##*/}" \
+          -m "section: 7" -m "source: Void Docs" -m "volume: Void Docs" \
+          -s -o "../mandoc/${filew}.7" "$file"' \;
 
     cd -
 fi

src/config/media/pulseaudio.md

@@ -19,6 +19,11 @@ terminal as follows:
 $ pulseaudio --daemonize=no --exit-idle-time=-1
 ```
 
+On the other hand, PulseAudio can also end up being auto activated when it isn't
+desired. To inhibit this behavior, the `autospawn` directive from
+[pulse-client.conf(5)](https://man.voidlinux.org/pulse-client.conf.5) can be set
+to `no`.
+
 There are several methods of allowing PulseAudio to access to audio devices. The
 simplest one is to add your user to the `audio` group. Alternatively, you can
 use a session manager, like `elogind`.

src/config/services/logging.md

@@ -9,11 +9,12 @@ implementations available in the Void repositories.
 
 [socklog(8)](https://man.voidlinux.org/socklog.8) is a syslog implementation
 from the author of [runit(8)](https://man.voidlinux.org/runit.8). Use socklog if
-you're not sure which syslog implementation to use. To use it, install the
-`socklog-void` package, and enable the `socklog-unix` and `nanoklogd` services.
+you're not sure which syslog implementation to use. To enable it, install the
+`socklog-void` package and enable the `socklog-unix` and `nanoklogd` services.
+Ensure no other syslog daemon is running.
 
 The logs are saved in sub-directories of `/var/log/socklog/`, and `svlogtail`
-can be used to help access them conveniently.
+can be used to access them conveniently.
 
 The ability to read logs is limited to `root` and users who are part of the
 `socklog` group.

src/installation/guides/chroot.md

@@ -225,14 +225,14 @@ For example, the partition scheme used throughout previous examples yields the
 following `fstab`:
 
 ```
-/dev/sda1       /boot/EFI   vfat    rw,relatime,[...]       0 0
+/dev/sda1       /boot/efi   vfat    rw,relatime,[...]       0 0
 /dev/sda2       /           ext4    rw,relatime             0 0
 ```
 
 The information from `blkid` results in the following `/etc/fstab`:
 
 ```
-UUID=6914[...]  /boot/EFI   vfat    rw,relatime,[...]       0 2
+UUID=6914[...]  /boot/efi   vfat    rw,relatime,[...]       0 2
 UUID=dc1b[...]  /           ext4    rw,relatime             0 1
 ```
 

src/installation/musl.md

@@ -19,9 +19,13 @@ software to need modification to compile and/or function properly. Void
 developers work to patch such software and hopefully get portability/correctness
 changes accepted into the upstream projects.
 
-Proprietary software rarely supports non-glibc libc implementations, although
-sometimes these applications are available as [flatpaks](https://flatpak.org/),
-which provide their own libc in the image.
+Proprietary software usually supports only glibc systems, though sometimes such
+applications are available as
+[flatpaks](../config/external-applications.md#flatpak) and can be run on a musl
+system. In particular, the [proprietary NVIDIA
+drivers](../config/graphical-session/graphics-drivers/nvidia.md#nvidia-proprietary-driver)
+do not support musl, which should be taken into account when evaluating hardware
+compatibility.
 
 ### glibc chroot
 

src/xbps/repositories/mirrors/index.md

@@ -38,9 +38,11 @@ sub-repository.
 | <https://mirror.aarnet.edu.au/pub/voidlinux/>      | AU: Canberra      |
 | <https://ftp.swin.edu.au/voidlinux/>               | AU: Melbourne     |
 | <https://void.cijber.net/>                         | EU: Amsterdam, NL |
+| <https://mirror.easylee.nl/voidlinux/>             | EU: Amsterdam, NL |
 | <http://ftp.dk.xemacs.org/voidlinux/>              | EU: Denmark       |
 | <https://mirrors.dotsrc.org/voidlinux/>            | EU: Denmark       |
 | <https://quantum-mirror.hu/mirrors/pub/voidlinux/> | EU: Hungary       |
+| <https://voidlinux.qontinuum.space:4443/>          | EU: Monaco        |
 | <http://ftp.debian.ru/mirrors/voidlinux/>          | EU: Russia        |
 | <https://mirror.yandex.ru/mirrors/voidlinux/>      | EU: Russia        |
 | <https://cdimage.debian.org/mirror/voidlinux/>     | EU: Sweden        |

src/xbps/repositories/mirrors/tor.md

@@ -9,6 +9,7 @@ The following Void Linux Mirrors are available on the Tor Network:
 | Repository                                                                             | Location   |
 |----------------------------------------------------------------------------------------|------------|
 | <http://lysator7eknrfl47rlyxvgeamrv7ucefgrrlhk7rouv3sna25asetwid.onion/pub/voidlinux/> | EU: Sweden |
+| <http://aafeeff2jty6me2boflxjbz4nqnm6ww5tcylc5u2fdprzbqg6gz5p2id.onion>                |            |
 
 ## Using XBPS with Tor