On 17.03.2024 20:24, Jonas Smedegaard wrote:
It would be helful if you could double-check using newest package and
with*only* the init script change, leaving all other settings at their
defaults and with no prior Radicale-related files created on the system
- and then check if the logging wor
Quoting Frank Lienhard (2024-03-17 19:10:43)
> On 17.03.2024 00:55, Jonas Smedegaard wrote:
> > Thanks for the proposed patch.
> > Unfortunately it does not apply to the Debian package.
> First: apologies.
> I seem to have made a mistake during my dist-upgrade and ended up with
> the old init-scri
On 17.03.2024 00:55, Jonas Smedegaard wrote:
Thanks for the proposed patch.
Unfortunately it does not apply to the Debian package.
First: apologies.
I seem to have made a mistake during my dist-upgrade and ended up with
the old init-script, which makes my provided "patch" logically totally
w
Hi Frank,
Quoting Frank Lienhard (2024-03-13 19:06:31)
> Package: radicale
> Version: 3.1.8-2
> [..]
> Filename: pool/DEBIAN/main/r/radicale/radicale_3.1.8-2_all.deb
>
> My System
> Devuan Daedalus (radicale package the debian bookworm packge)
> 6.1.0-18-amd64
>
> So applied changes from #103893
Package: radicale
Version: 3.1.8-2
[..]
Filename: pool/DEBIAN/main/r/radicale/radicale_3.1.8-2_all.deb
My System
Devuan Daedalus (radicale package the debian bookworm packge)
6.1.0-18-amd64
So applied changes from #1038930 and #1055771
I'm not a 100% sure that I had the unmodified original, so
Package: radicale
Version: 3.1.8-2
Radicale 3 which is installed from python3-radicale 3.1.8-2 is using
different base directory than previous versions and different way of
logging (STDERR istead of a file).
As a consequence /etc/init.d/radicale script requires modifications:
1. It is necessary t
6 matches
Mail list logo
