There is no python3-dask+diagnostics in the Fedora 35 repository. Hence, users who have python3-dask+diagnostics installed on Fedora 33/34 will experience a broken upgrade to Fedora 35 if the package name is not obsoleted. Once the recent commits in python-dask actually build, the package will show up and we will remove it from fedora-obsolete-packages. If this happens before final freeze, no further action is needed. If it happens after GA, the dasks's release number needs to be bumped to at least 2.
This update has been submitted for testing by churchyard.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Eyeballed the spec diff (since this is a special package), it looks good.
This update has been submitted for stable by bodhi.
actually, I do see one question...this adds:
but that subpackage appears to be a part of the most recent dask package builds:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1822035 https://koji.fedoraproject.org/koji/buildinfo?buildID=1822033
the same versioned builds for F35 and F36 failed, but it's still not clear this obsolete makes sense?
There is no python3-dask+diagnostics in the Fedora 35 repository. Hence, users who have python3-dask+diagnostics installed on Fedora 33/34 will experience a broken upgrade to Fedora 35 if the package name is not obsoleted. Once the recent commits in python-dask actually build, the package will show up and we will remove it from fedora-obsolete-packages. If this happens before final freeze, no further action is needed. If it happens after GA, the dasks's release number needs to be bumped to at least 2.
This update has been pushed to stable.