Your message dated Mon, 19 Dec 2022 22:12:18 +0000 with message-id <[email protected]> and subject line Bug#1017764: fixed in radicale 3.1.8-2 has caused the Debian Bug report #1017764, regarding radicale: enable apache2/nginx integration using debconf to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1017764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017764 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: radicale Version: 3.1.8-1 Severity: minor Dear Maintainer, I rant into issues following /usr/share/doc/radicale/README.Debian following issues. I hope my comments can reduce the number of support requests. I dumped README.Debian below with feedback that I hope is helpful. I'm happy to polish up the text and submit a formal patch if you fundamentally agree with my comments. Additionally, the other README files, which are pulled from github, should probably reference README.Debian or be replaced with README.Debian. README.md is meant as a github landing page and might confuse new users who should be reading README.Debian. README.Debian: > # Radicale usage on a Debian system > > Radicale can be started either in a user session or system-wide, > handling authentication itself or off-loading to a front-end service. > > Radicale in Debian by default uses authentication scheme "remote_user", > i.e. expects a front-end service to resolve ${REMOTE_USER}. This can probably be improved by rewording to 'i.e. expects a WSGI server to resolve ${REMOTE_USER}'. auth/remote_user.py states that this mode only supports an 'external WSGI server.' A new user might be fooled into thinking that they can graft their own bash script to handle this variable, for example. > ## Apache via uWSGI with PAM authentication > > Recommended setup for production use is to serve system-wide > by Apache via uWSGI with Apache-based authenticating. > > Edit /etc/radicale/config to adapt as needed. This line should be removed and (possibly) replaced with something to the effect of "Radicale's default settings work. If you need to customise the configuration, see DOCUMENTATION.html for instructions." In my first attempt with Radicale, this line confused me because I didn't know what I 'needed' to 'adapt', and the official documentation gave me instructions that conflict with the WSGI setup. > Install needed packages: > > apt install uwsgi uwsgi-plugin-python3 apache2 libapache2-mod-authnz- external > > Enable and activate back-end uWSGI service: > > ln -st /etc/uwsgi/apps-enabled/ ../apps-available/radicale.ini > service uwsgi restart Can't this be automated in debconf with a "set up and enable radicale for (1) apache; (2) nginx'? Furthermore, on almost every configuration, this will have to be run as a superuser and might want to be indicated, unless it's not standard Debian practice to do so and make the user figure it out from "permission denied". > Setup, enable, and activate front-end service: > > a2enmod proxy_uwsgi Apache (at least my installation) doesn't enable ssl out of the box. `a2enmod ssl; a2ensite default-ssl` (or graft default-ssl into apache2-vhost.conf) to reduce new user frustration. > cp /usr/share/doc/radicale/examples/apache2-vhost.conf >/etc/apache2/sites-available/events.example.org.conf > a2ensite events.example.org.conf For simplicity, consider changing _DOMAIN to 'localhost' for a local set-up. 'example.org' confused me into thinking that Radicale and/or SSL won't work without a domain name, so changing _DOMAIN to 'localhost' may be easier. Although, in general, /etc/apache2/.../000-default.conf should probably set a _DOMAIN variable for this configuration to reference. > service apache2 restart And perhaps add something to the effect of "Go to https://events.example.org <http://events.example.org> (or https://events.localhost/ <http://events.localhost/>" to test Radicale (since the default installation and documentation points users to localhost:5232, which may be confusing) and something to the effect of 'log in with the same credentials you use to log into your computer' or something to that effect. > > ## Simple daemon I didn't test the sysV setup, but I don't see any reference to the systemd enabling here. I'm happy to work on the phrasing to improve this for new users like me and reduce bug reports. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages radicale depends on: ii adduser 3.123 ii init-system-helpers 1.64 ii lsb-base 11.2 ii python3 3.10.5-3 ii python3-radicale 3.1.8-1 Versions of packages radicale recommends: ii ssl-cert 1.1.2 Versions of packages radicale suggests: ii apache2 2.4.54-2 ii apache2-utils 2.4.54-2 ii libapache2-mod-proxy-uwsgi 2.4.54-2 ii python3-bcrypt 3.2.0-1+b1 ii python3-passlib 1.7.4-1 ii uwsgi 2.0.20-4+b2 ii uwsgi-plugin-python3 2.0.20-4+b2 -- no debconf information
--- End Message ---
--- Begin Message ---Source: radicale Source-Version: 3.1.8-2 Done: Jonas Smedegaard <[email protected]> We believe that the bug you reported is fixed in the latest version of radicale, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard <[email protected]> (supplier of updated radicale package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 19 Dec 2022 14:33:41 +0100 Source: radicale Architecture: source Version: 3.1.8-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard <[email protected]> Changed-By: Jonas Smedegaard <[email protected]> Closes: 1017433 1017764 Changes: radicale (3.1.8-2) unstable; urgency=medium . * improve README.Debian; closes: bug#1017764, thanks to Borden * fix init script and default configuration; closes: bug#1017433, thanks to Joril and Tobias Leupold * declare compliance with Debian Policy 4.6.2 Checksums-Sha1: 0ac00ef319530e2241e69b0618f304dde5332c5a 2484 radicale_3.1.8-2.dsc f73cb31caff07fecffa849f80cf1ca546a417d9e 24340 radicale_3.1.8-2.debian.tar.xz a3fd60daf1438e62644f2a71631c6fcfd2d587dd 8316 radicale_3.1.8-2_amd64.buildinfo Checksums-Sha256: c8b8cffa614b1f066405ca39300fbfe92fb1ffc577ae505bcdfa0a11ba19a621 2484 radicale_3.1.8-2.dsc 0a917f4e0562ce832041449cea4050987169ff8493db672dfa78c4fd80495354 24340 radicale_3.1.8-2.debian.tar.xz 08a46f4b09de0a5926462c07f18af0ef24be19ab53450efe040073e7a8ad1943 8316 radicale_3.1.8-2_amd64.buildinfo Files: 319c860d393c88e5787a5a1fa3b083a2 2484 net optional radicale_3.1.8-2.dsc 28b1e58b4d691d9caa70826f0154143a 24340 net optional radicale_3.1.8-2.debian.tar.xz 1408089e6379563b949dd6b2e3cb89a6 8316 net optional radicale_3.1.8-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOgaXYACgkQLHwxRsGg ASFOORAAnm4sd0VzEf/Uequ3JpKbSPS9aUTyuVLfVqOkcC6E0aGXbqLcSGW8kipB K7RjTI8l4VR41e4UukkFtLF0/v8T3exKD0gxzmUS6q79Rg1rmD03qpmVL2AoNlVT QzNe9YjBXLB1P0IsgPiyEEiiFmYa4gElfYHnU6ANylNyFvqHf5PNs99DIZ35zCU5 RnWYjRxT9PbucvAKPNllVag40n2snGqfgiEVGKLIHTUq/fFctv6Pq3VUen0ab2cp pRpGdx0WkdpzrWHImOYLNO0olZiAh9tKhJQ3seVg2oeFemONWbyrlS4VlOff5EBU 5D+dILvY9Si7tRlLzK4Z8vOFt2vCMEoQ6kNVJsP3MdMRAxSEsur/VFQ4Xij/4taU 0y7gGzECJ9BKmrIdjjrtPGNr30R+H9W9WODnxzeyUBIYlq+uOcSnew7+D3Xzc8U/ lzVWYYmtMxwBNl5v7KThCT1naVLcyGaauMP/KFZavLgF2q3V91fhQG7FhHA97JgN gNZZLUXCyIlHhWBZwZ1zalGTou5OCN3SCyw5KjbfGJFvER8tP3woSENAYRJ59kgu YYk4Kz+5PQUexgPbya7E8L1GvEpwGwR2QsBcPUS9SbAhd8o0Sx7KLmSxXaiApsF8 FYC2lu3TAqJ9QO2z+HJBL/1yiHR7Fk+6g8rmJsh7cemUE6t+CCA= =1f4U -----END PGP SIGNATURE-----
--- End Message ---
