Created attachment 1253673 [details]
build.log

Created attachment 1253674 [details]
root.log

Created attachment 1253675 [details]
state.log

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

ping? Any news here?

The problem seems to come from a change in Kombu >= 4.0.

Unfortunately, upstream development has stopped and there is quite some work to be done there (AMQP 1.x, Python 3.x, etc).

Since this package does not seem to be used, the best solution is to remove it from F26 and later.

(In reply to lionel.cons from comment #6)
> The problem seems to come from a change in Kombu >= 4.0.

Hmm. Maybe we can create a compatibility package named python-kombu3? Are there significant but incompatible API/ABI changes¹ in Kombu 4.0?

> Unfortunately, upstream development has stopped and there is quite some work
> to be done there (AMQP 1.x, Python 3.x, etc).

What upstream do you mean, python-amqpclt or kombu? The last commit² and release at upstream of pythn-amqpclt is around half a year old: 27 Sep 2016. I wouldn't say upstream has stopped. Please try to open some issues for AMQP 1.x, Python 3.x, etc. Are you an upstream developer as well?

> Since this package does not seem to be used, the best solution is to remove
> it from F26 and later.

You can announce³ your intention to orphan the package on the devel mailing list. Maybe someone can pick it up and care about patches for the mentioned issues. As F26 is already in alpha state, I doubt the package can be removed, though that doesn't change the option to orphan it for F26+.

¹ https://fedoraproject.org/wiki/Package_maintainer_responsibilities?rd=PackageMaintainers/MaintainerResponsibility#Notify_others_of_changes_that_may_affect_their_packages 
² https://github.com/cern-mig/python-amqpclt/commit/3b6a3c96b19d6f9badeed9a408c1f64c8002099d
³ https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Orphaning_Procedure

Temporarily reassigning to maintainers of python-kombu to let them know about this bug and get into CC.

Dropping seems fine to me; the effort for a compat package is way too high, you'd also need compat packages for celery, and multiprocessing; using such a compat package is a pain anyways. I wouldn't go that route for a leaf package.

Well, this package is still in the repository and made it so into the new F27 branch. Koschei just fails again and again for all branches.

Could you orphan this package and let us know on the devel mailing list about the reasons noted in comment #6? I'm not sure if we should give a chance to other people with orphaning to animate this package, or directly retire it?

https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_do_I_orphan_a_package.3F
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

IMHO, the solution is not to orphan the package since the failures do not come from the packaging itself but from the unmaintained upstream sources.

I still think that the best solution is to remove this package from Fedora.

I will follow the recipe at https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

I ran "fedpkg retire" but got errors like:
remote: FATAL: W refs/heads/el5 rpms/python-amqpclt lcons DENIED by refs/heads/el[0-9]

However, the files are now gone (replaced by "dead.package") in Git.

Thanks! I'll close here.