Latest upstream release: 1.2.0.2 Current version/release in Fedora Rawhide: 1.2.0.1-2.fc20 URL: http://hackage.haskell.org/package/yesod-routes Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 1.2.0.3 Current version/release in Fedora Rawhide: 1.2.0.1-2.fc20 URL: http://hackage.haskell.org/package/yesod-routes Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 1.2.0.4 Current version/release in Fedora Rawhide: 1.2.0.1-2.fc20 URL: http://hackage.haskell.org/package/yesod-routes Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 1.2.0.5 Current version/release in Fedora Rawhide: 1.2.0.1-2.fc20 URL: http://hackage.haskell.org/package/yesod-routes Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 1.2.0.6 Current version/release in Fedora Rawhide: 1.2.0.1-2.fc20 URL: http://hackage.haskell.org/package/yesod-routes Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
*** This bug has been marked as a duplicate of bug 1124149 ***