I just upgraded my laptop from Silverblue 28 to 29. In the process, it removed Docker. And I can't install it now - there's some kind of conflict with GNOME shell:
$ rpm-ostree install docker Checking out tree 8781ad5... done Enabled rpm-md repositories: updates-testing updates fedora updates-modular updates-testing-modular fedora-modular rpm-md repo 'updates-testing' (cached); generated: 2018-09-08 16:07:40 rpm-md repo 'updates' (cached); generated: 2018-02-20 19:18:14 rpm-md repo 'fedora' (cached); generated: 2018-09-09 10:00:58 rpm-md repo 'updates-modular' (cached); generated: 2018-02-20 19:18:14 rpm-md repo 'updates-testing-modular' (cached); generated: 2018-02-20 19:18:14 rpm-md repo 'fedora-modular' (cached); generated: 2018-09-07 10:07:41 Importing metadata [=============] 100% Resolving dependencies... Forbidden base package replacements: gnome-shell-extension-launch-new-instance 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell-extension-window-list 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell-extension-alternate-tab 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell-extension-common 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell-extension-places-menu 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) git-core 2.19.0-0.0.rc0.fc29 -> 2.19.0-0.2.rc1.fc29 (updates-testing) mutter 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-shell-extension-apps-menu 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) gnome-classic-session 3.29.91-1.fc29 -> 3.30.0-1.fc29 (updates-testing) failed error: Some base packages would be replaced
Looks like there's an easy work-around - disable the updates-testing repository. I assume this is all going to get sorted out in the GNOME 3.30 testing / integration.
updates-testing
yeah the updates-testing repo stays enabled until after beta I think. This issue will resolve itself when they switch it to disabled by default.
alternatively you can rebase to the testing ref and then you should be able to install all packages from that repo: rpm-ostree rebase :fedora/29/x86_64/testing/silverblue
rpm-ostree rebase :fedora/29/x86_64/testing/silverblue
I'll go with the rebase - I want as much GNOME 3.30 as I ca get. ;-)
On Mon, Sep 10, 2018 at 6:24 AM Dusty Mabe pagure@pagure.io wrote:
dustymabe added a new comment to an issue you are following: ` yeah theupdates-testing` repo stays enabled until after beta I think. This issue will resolve itself when they switch it to disabled by default. alternatively you can rebase to the testing ref and then you should be able to install all packages from that repo: rpm-ostree rebase :fedora/29/x86_64/testing/silverblue `` To reply, visit the link below or just reply to this email https://pagure.io/teamsilverblue/issue/36 -- How many people can stand on the shoulders of a giant before the giant collapses?
dustymabe added a new comment to an issue you are following: ` yeah theupdates-testing` repo stays enabled until after beta I think. This issue will resolve itself when they switch it to disabled by default.
` yeah the
alternatively you can rebase to the testing ref and then you should be able to install all packages from that repo: rpm-ostree rebase :fedora/29/x86_64/testing/silverblue ``
To reply, visit the link below or just reply to this email https://pagure.io/teamsilverblue/issue/36
-- How many people can stand on the shoulders of a giant before the giant collapses?
ok, closing this as just another symptom of https://github.com/projectatomic/rpm-ostree/issues/415
Metadata Update from @mclasen: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.