Patching or scratch build for unison240 and version 2.40.128 FAILED.
See for details

Created attachment 1138019 [details]
Rebase-helper rebase-helper-debug.log log file.
 See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

2.48.4 is the latest stable release (which is what I'd assume we'd want anyway). I updated the spec file, and successfully built both source and binary packages. A copy of the spec file can be found at 'https://au2pb.org/srpms/unison248.spec'.

Latest upstream release: 2.51.2
Current version/release in rawhide: 2.40.128-9.fc27
URL: http://www.seas.upenn.edu/~bcpierce/unison/download/releases/

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/5047/

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.

Unfortunately this bug report doesn't relate to unison240.
We do however need to package a newer upstream unison, which
would require making a new Fedora package.

(In reply to Richard W.M. Jones from comment #7)
> Unfortunately this bug report doesn't relate to unison240.
> We do however need to package a newer upstream unison, which
> would require making a new Fedora package.

In comment #4 I'd supplied an updated spec file for 2.48 (the then current version) that compiled cleanly. I'd be glad to update (if I still have, or recreate) a spec file for the latest stable version.

The difficulty isn't making a spec file, it's shepherding the
thing through the new package process.

https://fedoraproject.org/wiki/New_package_process_for_existing_contributors

But especially for Unison we really need to think harder about
how it is packaged.  Packaging each version in separate packages
(unison213, unison227, unison240) is not really necessary - it
should be possible to combine them into a single package just
called unison, which would allow us to more easily add new
upstream major versions without going through the new package
process every time.

However someone's got to do the work.

Here's a link to the last few times this was discussed:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KQ523Z3S3VUATKU6V2NASAPGBKR5EJWC/

Note that I tried to make a unified package there, but I
got it wrong about version numbers.  It is possible to have
a unified package that has different version numbers for
each subpackage.  As far as I'm aware there is no technical
barrier to creating a unified package.

Let's continue this discussion on the Fedora devel mailing list:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RBOQEJY4QHNPDUTUU7GCNVJLNEH6JYKN/

This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement