Seem to be getting a file conflict here:
$ sudo dnf update
Last metadata expiration check: 0:39:27 ago on Thu 20 Apr 2023 17:26:45 BST.
Dependencies resolved.
==============================================================================================================================================================================================
Package Architecture Version Repository Size
==============================================================================================================================================================================================
Upgrading:
python3-nbclassic noarch 0.5.5-2.fc38 updates-testing 4.4 M
Transaction Summary
==============================================================================================================================================================================================
Upgrade 1 Package
Total download size: 4.4 M
Is this ok [y/N]: y
Downloading Packages:
python3-nbclassic-0.5.5-2.fc38.noarch.rpm 7.0 MB/s | 4.4 MB 00:00
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 3.7 MB/s | 4.4 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
file /usr/lib/python3.11/site-packages/nbclassic/static/components/font-awesome/css from install of python3-nbclassic-0.5.5-2.fc38.noarch conflicts with file from package python3-nbclassic-0.5.1-1.fc38.noarch
Sorry about that! I'll do that now.
This update has been unpushed.
This update has been unpushed.
Gah, sorry, about that. I'll file an issue with releng to remove the escape char I guess.
Works fine in normal usage
Seems to work fine, no regressions noted.
Seems to work fine, no regressions noted.
Thanks, I'll push another build+update later today
This update has been unpushed.
This update has been unpushed.
Thanks for that, upstream changed some stuff around and I thought we'd worked around it.
I'm seeing this:
Problem 2: package python3-botocore-1.24.8-1.fc36.noarch requires (python3.10dist(jmespath) < 1~~ with python3.10dist(jmespath) >= 0.7.
1), but none of the providers can be installed
- cannot install both python3-jmespath-1.0.0-1.fc36.noarch and python3-jmespath-0.10.0-5.fc36.noarch
- cannot install the best update candidate for package python3-jmespath-0.10.0-5.fc36.noarch
- cannot install the best update candidate for package python3-botocore-1.24.8-1.fc36.noarch
so looks like botocore needs to be bumped to a version that's happy with 1.0.0 here too?
Seems to work fine in normal usage, no regressions noted
Seems to work fine in normal usage, no regressions noted
Seems to work fine in normal usage, no regressions noted
Seems to work fine in normal usage, no regressions noted
Seems to work fine in normal usage, no regressions noted
Fixes the conflict