At a glance, it looks like fairly routine usage of dateutil.parser.parse() followed by dateutil.tz(); neither of these interfaces have changed. Please verify, but I think we're good here.

Thanks Pete, I'm about to push an update with a dependency for python-dateutil less than 2.0. (Sticking to upstream's release notes to avoid issues).

Worksforme.  I did see upstream's notes; the newer version of dateutil does work with py3 so you might want to send some signal their way.

For now, you'll probably want to explicitly Require: python-dateutil15, and do something like this to get that version of the modules:

import sys
sys.path.insert(0, '/usr/lib/python2.7/site-packages/python_dateutil-1.5-py2.7.egg/')
from dateutil import foo

...and probably inject the python version string instead of just using "py2.7". I plan to scratch up some notes and update these bugs with them soon.

(In reply to Dale Macartney from comment #2)
> Thanks Pete, I'm about to push an update with a dependency for
> python-dateutil less than 2.0. (Sticking to upstream's release notes to
> avoid issues).

Please test barman with the python-dateutil15 package as suggested comment #0, instead of using "python-dateutil < 2.0".

barman-1.3.3-5.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/barman-1.3.3-5.el6

barman-1.3.3-5.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/barman-1.3.3-5.el7

barman-1.3.3-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/barman-1.3.3-5.fc20

barman-1.3.3-5.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/barman-1.3.3-5.fc21

Package barman-1.3.3-5.el7:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing barman-1.3.3-5.el7'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0611/barman-1.3.3-5.el7
then log in and leave karma (feedback).

I really don't think you wanted to do that.  This is an F22+ change only, and should not affect your EPEL packages or older Fedora branches.  There is no python-dateutil15 for EPEL7, anyway.  

Additionally, if you want to ensure barman will use python-dateutil15, you will need to add patches as outlined in comment #3.  Any system with python-dateutil installed will almost certainly pull in the 2.4 modules rather than the 1.5 egg.

Package barman-1.3.3-5.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing barman-1.3.3-5.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-1614/barman-1.3.3-5.fc21
then log in and leave karma (feedback).

https://groups.google.com/forum/#!topic/pgbarman/R_NeTyRMWDI - barman upstream is saying python-dateutil-2.4 should be good, and they're going to include some unit tests to back it up so it is easier to see if future updates will affect the way they use it.

barman-1.3.3-6.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/barman-1.3.3-6.fc21

barman-1.3.3-6.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/barman-1.3.3-6.fc20

barman-1.3.3-6.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/barman-1.3.3-6.el7

barman-1.3.3-6.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/barman-1.3.3-6.el6

I pushed an update which undoes the Requires change, since it was not necessary and actually harmful on epel. Since no additional requirement on dateutil is necessary, closing this bug.