From 1a188b04f91116beb201eadeb14fe65470e23123 Mon Sep 17 00:00:00 2001 From: Vitor Baptista Date: Mon, 11 Nov 2013 17:19:35 -0300 Subject: [PATCH] [#1155] Explain how to pin the latest uncompatible version in requirements.in --- doc/upgrading-dependencies.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/upgrading-dependencies.rst b/doc/upgrading-dependencies.rst index 7fa698cdb68..d6c65ca317b 100644 --- a/doc/upgrading-dependencies.rst +++ b/doc/upgrading-dependencies.rst @@ -50,7 +50,9 @@ Steps to upgrade - If not, try to fix the problem. If it's too complicated, pinpoint which dependency's version broke our tests, find an older version that still - works, and add it to ``requirements.in``. Go back to step 1. + works, and add it to ``requirements.in`` (i.e., if ``python-dateutil`` + 2.0.0 broke CKAN, you'd add ``python-dateutil>=1.5.0,<2.0.0``). Go back to + step 1. #. Navigate a bit on CKAN to make sure the tests didn't miss anything. Review the dependencies changes and their changelogs. If everything seems fine, go