This is a conflict between python-nest-asyncio and python-nest_asyncio components. Apparently, we have introduced a package that already exited with a different name.

Miro,

Thank you for your excellent analysis of this situation.... It's APPRECIATED.

I would like to add a step to the process of submitting (if that's the right word) a package upgrade. I see this kind of error more than I would choose. It seems to me that some sort of "check  the dependencies" (is that the right word?) process would be greatly beneficial. Do you agree?

Thanks,

George...

I am afraid it is not really that simple. This kind of error only happens when you have a certain package set installed :/

Ccing here the maintainer of python-nest_asyncio.

We can keep only one of those packages. Currently, it seems that it'd be better to keep python-nest-asyncio because it's newer and python3-jupyter-client requires python3.10dist(nest-asyncio) >= 1.5 which only the newer one satisfies.

Andy, what do you think?

This is caused by me because when I was working on python-nest-asyncio - new dependency of python-jupyter-client - I did not check the version with an underscore in the name. However, the two packages' provides partially overlaps so I believe we can find a way how to check this in fedora-review and prevent this from happening in the future.

BTW I did the review on python-nest-asyncio and I was sure fedora-review would find such conflict. Checking for that manually is tedious, but I'll try to do that next time.

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

I've found out that I've CC'ed the wrong person, the python-nest_asyncio has a different maintainer now.

BTW The best course of action I see is to:

- Retire python-nest_asyncio on rawhide only.
- Obsolete python3-nest_asyncio < 1.4.3-100 from python3-nest-asyncio
- (optional, but safer) Provide python3-nest_asyncio = %{?epoch:%{epoch}:}%{version}-%{release} from python3-nest-asyncio

(In reply to Miro Hrončok from comment #8)
> BTW The best course of action I see is to:
> 
> - Retire python-nest_asyncio on rawhide only.
> - Obsolete python3-nest_asyncio < 1.4.3-100 from python3-nest-asyncio
> - (optional, but safer) Provide python3-nest_asyncio =
> %{?epoch:%{epoch}:}%{version}-%{release} from python3-nest-asyncio

I am happy with this course of action. I can retire python-nest_asyncio.

Any objections?

$ dnf repoquery --releasever=rawhide --repo=fedora{,-source} --whatrequires python3-nest_asyncio

python-nbclient-0:0.5.4-1.fc36.src
python3-nbclient-0:0.5.4-1.fc36.noarch


Can we update nbclient with the new package as dep as well?

nbclient should be fine:

dnf repoquery --releasever=rawhide --repo=fedora{,-source} --requires python3-nbclient    
python(abi) = 3.10
python3.10dist(jupyter-client) >= 6.1.5
python3.10dist(nbformat) >= 5
python3.10dist(nest-asyncio)
python3.10dist(traitlets) >= 4.2
python3dist(async-generator)
python3dist(jupyter-client) >= 5.3.4
python3dist(nbformat) >= 5
python3dist(nest-asyncio)
python3dist(traitlets) >= 4.2

dnf repoquery --releasever=rawhide --repo=fedora{,-source} --provides python3-nest-asyncio
python-nest-asyncio = 1.5.1-1.fc36
python3-nest-asyncio = 1.5.1-1.fc36
python3.10-nest-asyncio = 1.5.1-1.fc36
python3.10dist(nest-asyncio) = 1.5.1
python3dist(nest-asyncio) = 1.5.1

Mukundan, please retire your package in rawhide and I'm gonna prepare a PR for the one we keep. Thank you.

PR for review: https://src.fedoraproject.org/rpms/python-nest-asyncio/pull-request/1

Thank you.

By the way, that's also how I overcame the problem. I also removed the package python-nest-asyncio.
I did notice cutter-re depends on it somehow, but I removed it anyways.

FEDORA-2021-0f6ae64afe has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-0f6ae64afe

FEDORA-2021-0f6ae64afe has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.