Hi Lee,
can you still reproduce this bug? AFAICS this was fixed in the 2.13.3 upload.
I couldn't find the original requirements.yml that produced the error, but I tested a similar file with Ansible 2.13.4, and it worked fine.
Additionally, I'll tighten the package dependencies so this issue will be more apparent in the future.
Thanks, I appreciate it! Hopefully there will be a more stable resolvelib soon that doesn't cause these problems any more.
By the way, what's the reason for the disparate versioning in Ansible and the ansible package? Why is Ansible 2.13.4 packaged as 6.4.0+dfsg-1?
Regards, Gregor
