You are not logged in.
Yeah, such stuff exists. But one wants to install Artix via console tools, and that's also the only officially supported way. And also the only reasonable one ;-)
Hi all,
can I exclude a mirror from being used? I have the problem that apt always queries 2001:4ca0:4300::1:22, which leads to http://debian.bio.lmu.de/debian/pool/main/ being used. This mirror apparently has problems, as I often – not always – get errors about files not being found.
When I set the nameserver to e.g. 8.8.8.8 in /etc/resov.conf, another mirror is used, and installation of packages or updating works.
So: Can I exclude a specific mirror from being used?
Thanks for all help!
Artix is a really great distribution imo. Almost feels like Gentoo with binary packages ;-) For a desktop computer, I think this is currently the best you can do (if you don't want Systemd, but this is why we're here after all I think). At least my wife and my parents are happy with it, and I also use it on my notebook. The maintaining is very easy and it "just works". There's no installer though, you set it up just like Gentoo with console tools and you have to know what you're doing – at least a bit.
However, I do of course appreciate Devuan a lot for still supporting 32 bit machines, the Raspberry Pi 1 and so on. And by now, I'm about to migrate a server from Gentoo to Devuan (that's why I found this Radicale issue).
At the moment, I'm using Devuan, Artix and Gentoo – on different machines with different purposes. And I'm really happy that there are still reasonable people out there who don't use that Systemd spawn of the devil!
Well, let's hope they fix it. For now, I'm happy that I could get it to work "the Devuan way", but of course, it would be nice if everybody else would benefit of this. After all, it's actually a bug, although it possibly only appeared because Debian is sadly only focussing on systemd where they use some unit or whatever to start Radicale, and thus nobody takes care of the init script.
Btw I really like the way Artix handles this (the other non-systemd and non-Gentoo distro I am using as of recently): There, you have a package without any init scripts, and multiple packages including them, specifically for the init system in use. In case of Radciale, this would be the "radicale" package, and if you want the OpenRC init script, the "radicale-openrc" package.
Apparently, this doesn't fit the way Devuan does it, but fixing such a bug like the one here would be no problem, and would not depend on others … however, I hope the Debian guys will fix this.
Okay, I replied to that very bug report (here it is: https://bugs.debian.org/cgi-bin/bugrepo … 1017433#10 – btw. it surely sucks that the email addresses are displayed as plain text and are not obfuscated in any way. As well as it sucks that this is no real Bugzilla but some strange email driven system. But whatever, maybe I'm too used to how Gentoo handles this stuff ;-).
Won't Devuan provide a fixed package if it's broken on Devuan and Debian doesn't fix it? The bug report dates back to August …
EDIT: Oh, I just saw we were cross-posting ;-)
Thanks for this info, I could get it to work with this hint. But the patch doesn't make it work respectively is not applicable.
There are more fixes to do. The /etc/default/radicale file contains a non-existant command line option that has to be removed:
--- /etc/default/radicale.orig 2022-11-16 18:47:47.350441509 +0100
+++ /etc/default/radicale 2022-11-16 18:48:07.849614303 +0100
@@ -5,7 +5,7 @@
# Options for radicale on startup
# Note that most options can be specified in /etc/radicale/config
-RADICALE_OPTS="--daemon"
+RADICALE_OPTS=""
# Make initscript verbose, override system default
# (Note: This is ONLY about the initscript!)
Also, the Devuan init script misses a --background option when starting the daemon. But also when having fixed this, stopping and/or restarting the daemon is broken and also has to be fixed.
The patch that makes it work would be:
--- /etc/init.d/radicale.orig 2022-11-16 19:06:50.714274017 +0100
+++ /etc/init.d/radicale 2022-11-16 19:33:49.998867023 +0100
@@ -68,10 +68,10 @@
fi
start-stop-daemon --start --quiet --startas $DAEMON \
- --name $NAME --test > /dev/null \
+ --exec $DAEMON --test > /dev/null \
|| return 1
- start-stop-daemon --start --quiet --startas $DAEMON \
- --name $NAME --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
+ start-stop-daemon --start --quiet --startas $DAEMON --background \
+ --exec $DAEMON --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
$RADICALE_OPTS \
|| return 2
}
@@ -86,7 +86,7 @@
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
- start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
+ start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --user $DAEMON_UID
}
case "$1" in
What are the chances this will be officially fixed (soonish) in Devuan's repositories? Can I do anything to help?
Hi all :-)
OpenRC provides a nice method of configuring the network, which is esp. very convenient for wired setups, through the netifrc module. One can setup all kinds of network connections (including bridges etc.) – no need for any daemon to run. Just add few lines to in /etc/conf.d/net, create a symlink from /etc/init.d/net.lo to e.g. eth0, add it to the default runlevel and you're done.
But: On Devuan, there's neither /etc/conf.d, nor /etc/init.d/net.lo. So: Is this supported and/or intended to be used on Devuan?
Thanks for all information about this!
I don't know if this is important, but this happens on a Raspberry Pi 1 using the respective image of Devuan.
Simply via
/etc/init.d/radicale start
I didn't change anything … I just took the /etc/radicale directory from my Gentoo machine. I didn't touch /etc/default/radicale or anything else.
EDIT:
I just removed (and purged) Radicale and started over again from scratch. Here's what happens when I try to start it:
# /etc/init.d/radicale start
Starting Radicale CalDAV server : radicale.
# ps -ef | grep radicale
root 23055 22552 0 08:38 pts/0 00:00:00 grep radicale
As said: Nothing happens. The Radicale process is not started …
This is what happens when using the adapted Gentoo init script, with the Gentoo etc:
# /etc/init.d/radicale start
* Caching service dependencies ...
Error: radicale is the name of a real and virtual service. [ ok ]
* Starting radicale ... [ ok ]
# ps -ef | grep radicale
root 23298 1 94 08:42 ? 00:00:06 /usr/bin/python3 /usr/bin/radicale
root 23307 22552 0 08:42 pts/0 00:00:00 grep radicale
And after restarting it, the error is gone:
# /etc/init.d/radicale restart
* Stopping radicale ... [ ok ]
* Starting radicale ... [ ok ]
And after doing so, the original init script interestingly reports an error:
# /etc/init.d/radicale_default start
Starting Radicale CalDAV server : radicaleusage: radicale [OPTIONS]
radicale: error: unrecognized arguments: --daemon
failed!
Hi All :-)
I'm about to migrate a server from Gentoo to Devuan. As a Gentoo user, I of course want to use OpenRC :-)
However, I couldn't start Radicale using the shipped init script /etc/init.d/radicale. Nothing happened. No error, no syslog entry, nothing.
I thus tried to use Gentoo's init script:
#!/sbin/openrc-run
# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
PIDFILE=/run/radicale.pid
depend() {
need localmount
}
start() {
ebegin "Starting radicale"
start-stop-daemon --start --quiet --background \
--user radicale \
--umask 0027 \
--stderr-logger /usr/bin/logger \
--pidfile ${PIDFILE} --make-pidfile \
--exec /usr/bin/radicale
eend $?
}
stop() {
ebegin "Stopping radicale"
start-stop-daemon --stop --quiet \
--pidfile ${PIDFILE}
eend $?
}
Which also didn't work out of the box – but after having removed the "depend" function and the "--stderr-log" argument, I actually did start Radicale. On the first start, I got "Error: radicale is the name of a real and virtual service.", but it did start. After restarting it, that error was also gone.
I tried to reproduce what the original init script did before writing this, but interestingly, I now get an error using it:
Starting Radicale CalDAV server : radicaleusage: radicale [OPTIONS]
radicale: error: unrecognized arguments: --daemon
failed!
I'm pretty sure this wasn't there before I tried to use the Gentoo init script …
All this is a bit strange. Is this the "handwork" that would be necessary when using OpenRC, as the installer told me? I never used anything else than OpenRC, so I am not used to sysvinit init scripts …
Thanks for all info!
Ah okay, I only used "apt remove" until now. I dodn't know there also was some "more complete" removal. Thanks for the hint!
Hi forum :-)
I'm about to set up some machines previously run by Gentoo using Devuan. I was very happy to see that, in the Debian universe, there are also some sane people not using systemd ;-)
Obviously, I chose OpenRC as the init system. But now, I have a few questions about it, esp. as the installer states that there was some manual configuration to do using OpenRC. This is definitely not a problem for a Gentoo user though.
First I cleaned up some stuff I don't need, e.g. the brltty, saned, ofono etc. But their init scripts remained in the respective runlevel after the packages were removed, interestingly, the symlinks still pointed to existing scripts. So I ran rc-update del ... to also remove the init scripts.
Is this the "manual configuration" I have to do when using OpenRC on Devuan? And why are the packages not removed completely? (Sorry if this is some normal behavior on Debian based systems; for almost 20 years now I have been using nothing else than Gentoo)
The other thing is: What about OpenRC's network configuration capabilities? Through OpenRC's netifrc module, one can setup all kinds of network connections, and this is especially useful for wired connections. No need for any daemon to run, just a setup in /etc/conf.d/net, a symlink to /etc/init.d/net.lo, and adding it to the default runlevel and you're done.
But there's neither /etc/conf.d, nor /etc/init.d/net.lo.
So: Is this supported and/or intended to be used on Devuan?
Thanks for all clarification!