FS#58344 - [radicale] Needs python-dateutil==2.6.1, but the version in the repos is 2.7.2
Attached to Project:
Community Packages
Opened by Koz Ross (koz) - Tuesday, 24 April 2018, 22:13 GMT
Last edited by David Runge (dvzrv) - Tuesday, 24 April 2018, 23:35 GMT
Opened by Koz Ross (koz) - Tuesday, 24 April 2018, 22:13 GMT
Last edited by David Runge (dvzrv) - Tuesday, 24 April 2018, 23:35 GMT
|
Details
Description:
Because Radicale expects exactly version 2.6.1, but the repo version of python-dateutil is 2.7.2, the Radicale daemon fails to start at all. Additional info: * Radicale version: 2.1.9-1 * Relevant Python backtrace: Apr 25 10:04:51 banana systemd[1]: Started radicale - A simple CalDAV (calendar) and CardDAV (contact) server. Apr 25 10:04:58 banana radicale[3721]: Traceback (most recent call last): Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 574, in _build_master Apr 25 10:04:58 banana radicale[3721]: ws.require(__requires__) Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 892, in require Apr 25 10:04:58 banana radicale[3721]: needed = self.resolve(parse_requirements(requirements)) Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 783, in resolve Apr 25 10:04:58 banana radicale[3721]: raise VersionConflict(dist, req).with_context(dependent_req) Apr 25 10:04:58 banana radicale[3721]: pkg_resources.ContextualVersionConflict: (python-dateutil 2.7.2 (/usr/lib/python3.6/site-packages), Requirement.parse('python-dateutil==2.6.1'), {'Radicale'}) Apr 25 10:04:58 banana radicale[3721]: During handling of the above exception, another exception occurred: Apr 25 10:04:58 banana radicale[3721]: Traceback (most recent call last): Apr 25 10:04:58 banana radicale[3721]: File "/usr/bin/radicale", line 6, in <module> Apr 25 10:04:58 banana radicale[3721]: from pkg_resources import load_entry_point Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3088, in <module> Apr 25 10:04:58 banana radicale[3721]: @_call_aside Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3072, in _call_aside Apr 25 10:04:58 banana radicale[3721]: f(*args, **kwargs) Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set Apr 25 10:04:58 banana radicale[3721]: working_set = WorkingSet._build_master() Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 576, in _build_master Apr 25 10:04:58 banana radicale[3721]: return cls._build_from_requirements(__requires__) Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 589, in _build_from_requirements Apr 25 10:04:58 banana radicale[3721]: dists = ws.resolve(reqs, Environment()) Apr 25 10:04:58 banana radicale[3721]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 778, in resolve Apr 25 10:04:58 banana radicale[3721]: raise DistributionNotFound(req, requirers) Apr 25 10:04:58 banana radicale[3721]: pkg_resources.DistributionNotFound: The 'python-dateutil==2.6.1' distribution was not found and is required by Radicale Apr 25 10:04:58 banana systemd[1]: radicale.service: Main process exited, code=exited, status=1/FAILURE Apr 25 10:04:58 banana systemd[1]: radicale.service: Failed with result 'exit-code'. Steps to reproduce: - Install Radicale - Try running the server process, either via systemd or manually - Watch the backtrace spew |
This task depends upon
Closed by David Runge (dvzrv)
Tuesday, 24 April 2018, 23:35 GMT
Reason for closing: Fixed
Additional comments about closing: Ugly fixed in 2.1.9-2
Tuesday, 24 April 2018, 23:35 GMT
Reason for closing: Fixed
Additional comments about closing: Ugly fixed in 2.1.9-2
How exceedingly odd. This doesn't even have an explanation as to why they switched to some gross python antipattern.
However, i removed the version pinning (for now). This will probably lead to hitting a bunch of the above mentioned bugs.
In any case we can most likely only wait for a new version of dateutil/vobject to fix the issues.