even though official docs say to report bugs to bugs.devuan.org, i've seen bug reports all over the devuan ecosystem (= bugs.d.o, git.d.o, this forum, dng list, irc maybe(?).), and noticed some debian bugs also originating from devuan.

so, what's the correct way to report bugs?  and what's the deal with bugs reported in those other community channels?

been kind of confused about this, would be nice if that was clarified if possible.

thanks,
d.

@rolfie, use a live cd , download older versions (=3.2.7-3) of eudev & libeudev1 from https://pkgmaster.devuan.org/devuan/pool/main/e/eudev/ to devuan partition/usb stick,
reboot to devuan recovery mode, and install (dpkg -i $package) the downloaded debs.
that's just one way to do it. (couldn't get network from recovery mode as #111 mentioned, so had to use live cd)

also my 2c :
mate w/ slim+consolekit is buggy in beowulf. works fine in ascii.
mate w/ lightdm+elogind is a better more stable choice with newer versions of policykit, elogind, etc.

there's a bug with mate-power-manager and upower 0.99.9-3 in beowulf. there's no progress in battery (dis)charging. stuck in charged 100%, or "charging xx% time remaining xx:xx" without ever changing these values.
when upgraded to upower 1:0.9.23-2+devuan1.3 from ceres, this was fixed.
using mate-power-manager 1.20.0-1+hezeh1 from hezeh.org.

try something like this maybe, added in the same preferences file :

Package: firefox
Pin: release a=ceres
Pin-Priority: 950

Package: firefox-l10n-hr
Pin: release a=ceres
Pin-Priority: 950

everything's working fine here with newer policykit (no ascii repos anymore).
just saw your post about upower, and will be trying that also soon.

maybe this is relevant : https://github.com/gentoo/eudev/issues/160 (?)

never had such an issue with eudev in beowulf. dist-upgraded fresh bare ascii, then installed DE, etc, including qemu-kvm & libvirt, groups were created ok it seems :
kvm:x:111:
libvirt:x:112:
no such udevd message..

Bob Dylan - One More Cup Of Coffee
https://vimeo.com/107923995

@golinux, Trinity is based on KDE3, not KDE4.

@alupoj i don't think there's a way to keep KDE4, other than using an old distro with KDE4 for as long you can get descent support (LTS), or pinning packages.. but these solutions are good for a short while, unless someone works on a KDE4 fork like Trinity for KDE3.

reading at the headers, i think there might be something wrong with outgoing (SMTP) settings. can you double check (outgoing server/port/auth) ?

(or ask hosting provider for correct settings..)

i used the web ui.
let me know if this rss -> torrent thing works, i'm interested

i was running transmission-daemon 2.94 on a devuan beowulf server for a short while (about a month) without any problems. apache2 (no php) running there also, https enabled using certbot from official repos. it was just for evaluation, so it's down at the moment.. but everything was working smoothly, no issues. let me know if i can help with any configs there

p.s. i had issues with transmission-daemon 2.92 on ascii, taking too much ram and initiating oom-killer at some point to kill daemon completely, just after a few hours running, with ~200 torrents. found an upstream bug fixed in version 2.94, so moved to beowulf cause of that.. (dist-upgraded ascii -> beowulf). and issue was gone...

antofox thanks for the notice.

moved back to previous "stable" MATE setup for devuan beowulf:
mate packages from official devuan beowulf/testing, except for mate-power-manager[-common] that are pinned to 1.20.0-1+hezeh1 from hezeh.org/ascii.