View this report as an mbox folder.
raspberrypi-sys-mods. Full text available.
Gregory Nowak <email@example.com>:
Your message specified a Severity: in the pseudo-header, but the severity value important was not recognised. The default severity normal is being used instead. The recognised values are: critical, grave, normal, minor, wishlist.
Full text available.
From: Gregory Nowak <firstname.lastname@example.org> To: Devuan Bug Tracking System <email@example.com> Subject: raspberrypi-sys-mods is missing from devuan Date: Wed, 24 May 2017 17:59:44 -0700 Package: raspberrypi-sys-mods Version: 20170313 Severity: important Dear Maintainer, this report is related to: <https://git.devuan.org/sdk/arm-sdk/issues/4> and: <https://git.devuan.org/sdk/arm-sdk/issues/14> Please make the raspberrypi-sys-mods package from: <http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-sys-mods/> available on devuan's armhf and arm64 architectures; specifically /etc/udev/rules.d/99com.rules from this package. On the raspberry pi 2 and 3, these rules create /dev/serial0 and /dev/serial1 links. The serial0 will always point to the serial console, and serial1 will always point at the bluetooth modem if running on a rpi3. This is still true even if the overlay putting the bluetooth on the mini uart is being used as far as I can tell. These udev rules would also help in resolving: <https://bugs.devuan.org/db/85/85.html> -- System Information: Architecture: aarch64 Kernel: Linux 4.10.0-rc5-v8+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)