One or more of the specfile's Sources is not a valid URL so we cannot automatically build the new version for you. Please use a URL in your Source declarations if possible.

Please also bring this release to EPEL-7 since it contains a major new feature (next generation onion services)

I am still investigating, whether it is possible with regard to the policy of EPEL and breaking version changes. Mainly, I need to know what depends on Tor and what we are breaking by moving to the newer version.

Also note that the torproject still recommends the current version in EPEL for stable long term supported releases: https://blog.torproject.org/tor-0329-released-we-have-new-stable-series

"Per our stable release policy, we plan to support each stable release series for at least the next nine months, or for three months after the first stable release of the next series: whichever is longer. If you need a release with long-term support, we recommend that you stay with the 0.2.9 series."

However, I have recent builds of the latest versions in my copr @ https://copr.fedorainfracloud.org/coprs/maha/tor-latest/ that can be used, testing and feedback are welcome.

Thanks for these copr builds! I gave it a short try on CentOS 7 and it worked just fine.
Soon there will be a tor 0.3.3.1-alpha out with some new significant anti-DoS mitigations, are you planing to follow 0.3.3.1-alpha closely? If you aim to provide alpha releases for the future I'm considering to use your copr builds to add tor_alpha support to 
https://github.com/nusenu/ansible-relayor
for CentOS and Fedora.

So I'm trying to keep Tor up2date within Fedora at least within Tor's major relases and Fedora's major releases, so that it stays up2date but won't break.

For EPEL I still need to try to understand how the policy affects tor.

Nevertheless, I have two coprs:

* tor-latest: Have the latest stable release for all recent platforms, this should give you the latest stable tor release
* tor-alpha: Builds of released alpha versions. I plan to put alpha releases here, but I might not be as quick as with stable releases.

Would be nice if you would give the ansible role an option to enable one of these repositories. So ther would be: default (== no additional repo), copr-latest or copr-alpha.

That is a bit off-topic here, but yes if you find it useful I will add tor-alpha support once 0.3.3.1-alpha is released and available in your copr.

Are you planing to bring 0.3.2.9 to Fedora?
(So they can access v3 onion services as well)

I didn't see anything on bodhi
https://bodhi.fedoraproject.org/updates/?packages=tor

Latest upstream release: 0.3.2.10
Current version/release in rawhide: 0.3.2.9-3.fc28
URL: https://www.torproject.org/

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/4991/

tor-0.3.1.10-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8b33bd7abf

tor-0.3.1.10-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.