Bug 1497572

pytz-2016.6.1-1 contains tests that check assertions for the data contained in this specific version.  Fedora however patches pytz to read timezone data from /usr/share/zoneinfo.  If the latter has been updated (as part of package tzdata) and thus diverged from the data shipped with pytz, pytz cannot be built; example failures from https://kojipkgs.fedoraproject.org//work/tasks/4885/22194885/build.log:

| […]
| =================================== FAILURES ===================================
| ___________________ NoumeaHistoryStartTestCase.testDayAfter ____________________
| self = <test_tzinfo.NoumeaHistoryStartTestCase testMethod=testDayAfter>
|     def testDayAfter(self):
|         self._test_all(
| >               self.transition_time + timedelta(days=1), self.after
|                 )
| pytz/tests/test_tzinfo.py:337:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
| pytz/tests/test_tzinfo.py:292: in _test_all
|     self._test_tzname(utc_dt, wanted)
| pytz/tests/test_tzinfo.py:241: in _test_tzname
|     tzname, str(utc_dt), dt.tzname()
| E   AssertionError: Expected NCT as tzname for 1912-01-13 12:54:12+00:00. Got +11
| ___________________ NoumeaHistoryStartTestCase.testHourAfter ___________________
| self = <test_tzinfo.NoumeaHistoryStartTestCase testMethod=testHourAfter>
|     def testHourAfter(self):
|         self._test_all(
| >               self.transition_time + timedelta(hours=1), self.after
|                 )
| pytz/tests/test_tzinfo.py:327:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
| pytz/tests/test_tzinfo.py:292: in _test_all
|     self._test_tzname(utc_dt, wanted)
| pytz/tests/test_tzinfo.py:241: in _test_tzname
|     tzname, str(utc_dt), dt.tzname()
| E   AssertionError: Expected NCT as tzname for 1912-01-12 13:54:12+00:00. Got +11
| _________________ NoumeaHistoryStartTestCase.testInstantAfter __________________
| self = <test_tzinfo.NoumeaHistoryStartTestCase testMethod=testInstantAfter>
|     def testInstantAfter(self):
|         self._test_all(
| >               self.transition_time + self.instant, self.after
|                 )
| pytz/tests/test_tzinfo.py:322:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
| […]

AFAICT there are three ways to approach this:

1. Backport the updated tests from the pytz version corresponding to tzdata's version.  This would let it remain a moving target, keeping it non-obvious if a package build will succeed or not.
2. Add a versioned (build-)requirement on tzdata, i. e. pytz-2016.6.1 would (build-)require tzdata = 2016f (untested if those match up).  IMHO this is optimal because it does what it says it does, but it also adds the necessity to update the pytz package every time tzdata gets updated.
3. Remove by patch all tests in pytz/tests/test_tzinfo.py that depend on (dynamically read) timezone data (does that leave any?).  This will work, but it also removes a layer of protection against regressions.