Me no understand :D I guess this will be up for @kparal to tackle...

Please update description and summary for all packages to reflect the new state.

The Requires and BuildRequires lines used to be sorted by alphabet (except for if-else-endif blocks where it made sense to group some of those together) for easier searching. Please make them sorted again.

Let's say "runtask and taskotron_result" here to make it clearer that the intention is to keep both, thanks.

Edit: Thinking more about this, why is it even needed? All old libtaskotron packages are obsoleted by taskotron_runner. So people will end up with taskotron_runner anyway, which already requires python2-libtaskotron. Why do we need this reverse dependency?

That doesn't seem right. The package has been replaced. Was something else supposed to be here?

I guess readme and license should be part of all subpackages. Previously it was just in libtaskotron-core, but that was a basic requirement of everything else, so it was also always installed. You can check some guidelines for this, I'd simply include it everywhere.

Could you make the directories and files definitions less scattered around? Some of them are at the top, some of them are down here. Put them into one place and make them sorted, please.

You can be more specific, like "Build the library for both python2 and python3, rename the subpackages. Put runtask into taskotron-runner and succeed libtaskotron-disposable with it. ..." or something like that.

Okay, I've force pushed the update.

All your feedback should be addressed, thanks!
I've left some Requires/BuildRequires unsorted - the ones that are inside if fedora > xy .

Also, I've found out and fixed an issue with Python 3 tests - running just:

%{__python3} setup.py test

is not enough to actually run it with Python 3 (it runs with Python 2). I've made changes to setup.py, let me know if you like the way I've worked around the issue.

If it's okay, I'll apply the same fix to all our Py2/3 projects (I've looked into testcloud and it's affected the same way).

ACK. Let's hope for the best.

Commit 3db27547 fixes this pull-request