Bug#978101: radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini

2020-12-26 Thread Flo
I have three suggestions: 1) the suggested way is to run Radicale with Apache and UWSGI. Therefore, libapache2-mod-proxy-uwsgi is necessary and not to be marked as suggested. Using Radicale with uWSGI is _suggested_ and therefore the package _suggests_ libapache2-mod-proxy-uwsgi. if instead

Bug#978101: radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini

2020-12-25 Thread Jonas Smedegaard
Hi Debian Flo, Quoting Debian Flo (2020-12-25 23:41:16) >* What led up to the situation? > > Installing radicale. On buster, I found out that this doesn't change in > testing or unstable. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I did

Bug#978101: radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini

2020-12-25 Thread Debian Flo
Package: radicale Version: 2.1.11-6 Severity: important Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing radicale. On buster, I found out that this doesn't change in testing or