Bug 1776755

Jamie, is this still needed? I noticed python3-requests-mock is built in December.

python-testtools has not been released since 2017 and I'd rather not support it on a long-lived release unless it's absolutely required (and if so I'm happy to make you the maintainer for that branch)

I built requests-mock by disabling the unit tests in epel8/python3. So not needed by that bug any more, but it would be nice to have.

It's not valuable enough to me to maintain it (I got down to just maintaining packages for my own projects), however the entire openstack unit testing frameworks are built on testtools so I would have expected them to want it?

If I'm the only requestor you can close it out and I'll have a look if I need to migrate upstream.

It would be great if we could get an EPEL8 build for the package. I'm trying to build python-fixtures there, and it's failing due to this.

*** Bug 1815831 has been marked as a duplicate of this bug. ***

EPEL8 branch requested
https://pagure.io/releng/fedora-scm-requests/issue/24085
https://pagure.io/releng/fedora-scm-requests/issue/24086

Also, would anyone be interested in co-maintaining this? I don't really use it anymore and it seems better to have the maintainers who need it be unblocked if they need the package updated.

Michel, if you add the python-sig group myself and others in the SIG would be happy to assist.

(In reply to Carl George from comment #6)
> Michel, if you add the python-sig group myself and others in the SIG would
> be happy to assist.

Thanks Carl. python-sig added to the ACL.

Looks like python-extras will be stable tomorrow, and python-mimeparse in 4 days, so we should finally be able to build this package!

I figured this out, we had a build loop to overcome.  I've added comments directly in the spec file to make it more clear for future maintainers.

https://src.fedoraproject.org/rpms/python-testtools/c/f0ca163033077e93b309ec07953dbb6e0496fa6f?branch=master

I've got step 1 of that in an override, and I'm working through the other steps.

FYI Michel, when branching a package for EPEL it is discouraged to wipe out the changelog.  I reverted that commit to restore it.  I also did a merge with master so future master commits can be applied to the epel8 branch with a fast-forward.

Carl: good to know! I have another package I'm bringing to EPEL and I'll make sure the changelog is preserved for it. Also thanks for working on this.

FEDORA-EPEL-2020-4c8aca531a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4c8aca531a

Nice work, guys! Thank you.

FEDORA-EPEL-2020-4c8aca531a has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4c8aca531a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

(In reply to Carl George from comment #8)
> I figured this out, we had a build loop to overcome.  I've added comments
> directly in the spec file to make it more clear for future maintainers.
> 
> https://src.fedoraproject.org/rpms/python-testtools/c/
> f0ca163033077e93b309ec07953dbb6e0496fa6f?branch=master
> 
> I've got step 1 of that in an override, and I'm working through the other
> steps.
> 
> FYI Michel, when branching a package for EPEL it is discouraged to wipe out
> the changelog.  I reverted that commit to restore it.  I also did a merge
> with master so future master commits can be applied to the epel8 branch with
> a fast-forward.

Carl, looks like python-testscenarios (which you also branch and build for bootstrapping python-testtools) somehow never has the epel8-playground branch created, and also appears to share all its commits with its master branch -- not sure how that happens?

And with package.cfg missing from python-testtools, the epel8-playground packages never got bootstrapped. If it's alright with you I'll try and recover them.

That branch wasn't created because I submitted the request with `--no-git-branch`, which authorizes the branch to be created but doesn't create it for you.  This also avoids creating the pacakge.cfg file.  This was intentional, as not every packager wants to deal with epel8-playground.  If you want to do it, you can create an epel8-playground locally and push it.

    git checkout epel8
    git pull
    git checkout -b epel8-playground
    git push -u origin epel8-playground

FEDORA-EPEL-2020-4c8aca531a has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.