rugk
(rugk)
April 30, 2020, 1:39pm
1
If I run rpm-ostree -v
in Fedora Silverblue 32, I get one line, before the “LayeredPackages” another line:
InactiveRequests: nano
This maybe only happens after the upgrade to Fedora 32. And IIRC I’ve previously installed, i.e. layered “nano” via rpm-ostree install nano
. Also, nano is actually usable and I cannot layer it again, which results in an error saying that ‘“nano” is already provided by: nano-[package name]’.
So what does this “InactiveRequests” line mean in rpm-ostree?
3 Likes
I think you might have overridden in the past the nano package with a specific version, the version you had overridden is now superseded ny the new nano package provided in Silverblue 32. You should now be able to rpm-ostree override reset <nano package name>
to clear the override and clear that message.
rugk
(rugk)
April 30, 2020, 4:05pm
3
Not that I am aware of, no.
Executing your command I just get:
error: No overrides for package ‘nano’
Can you paste full output of rpm-ostree status
?
rugk
(rugk)
April 30, 2020, 5:17pm
5
I guess you meant the -v
command, because otherwise that is not even shown:
$ rpm-ostree status -v
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 5h 45min ago
Deployments:
ostree://fedora:fedora/32/x86_64/silverblue
Version: 32.20200430.0 (2020-04-30T01:11:17Z)
BaseCommit: 53eecca4a4d163c6d081c5497b324ea3374a6b29708f866081f22e4690127591
├─ repo-0 ((invalid timestamp))
├─ repo-1 ((invalid timestamp))
└─ repo-2 ((invalid timestamp))
Commit: 519f7fe00a6ea27d18486453fc63ceea387fdc61c4f3df1f57919d465aa055ad
├─ updates (2020-04-30T01:55:47Z)
├─ fedora-cisco-openh264 (2020-03-17T20:10:45Z)
└─ fedora (2020-04-24T11:00:23Z)
Staged: yes
StateRoot: fedora
GPGSignature: 1 signature
Signature made Do 30 Apr 2020 03:11:29 CEST using RSA key ID 6C13026D12C944D0
Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"
SecAdvisories: FEDORA-2020-30c45be10c Low libslirp-4.2.0-2.fc32.x86_64
Upgraded: crun 0.13-1.fc32 -> 0.13-2.fc32
fedora-release-common 32-1 -> 32-2
fedora-release-silverblue 32-1 -> 32-2
glib2 2.64.2-1.fc32 -> 2.64.2-2.fc32
libslirp 4.2.0-1.fc32 -> 4.2.0-2.fc32
openssh 8.2p1-2.fc32 -> 8.2p1-3.fc32
openssh-clients 8.2p1-2.fc32 -> 8.2p1-3.fc32
openssh-server 8.2p1-2.fc32 -> 8.2p1-3.fc32
openssl-pkcs11 0.4.10-5.fc32 -> 0.4.10-6.fc32
ostree 2020.3-2.fc32 -> 2020.3-3.fc32
ostree-grub2 2020.3-2.fc32 -> 2020.3-3.fc32
ostree-libs 2020.3-2.fc32 -> 2020.3-3.fc32
qt5-qtwayland 5.13.2-3.fc32 -> 5.13.2-4.fc32
vulkan-loader 1.2.131.1-1.fc32 -> 1.2.135.0-1.fc32
Removed: fipscheck-1.5.0-8.fc32.x86_64
fipscheck-lib-1.5.0-8.fc32.x86_64
InactiveRequests: nano
LayeredPackages: adb […]
● ostree://fedora:fedora/32/x86_64/silverblue
Version: 32.20200429.0 (2020-04-29T01:07:05Z)
BaseCommit: 563658b0ee90c737d5248832a097b7ed3f7dee05e1594ea8bd352a2c6f7bb04d
├─ repo-0 ((invalid timestamp))
├─ repo-1 ((invalid timestamp))
└─ repo-2 ((invalid timestamp))
Commit: 1c04b70548062d8885652ba86cff115d466741a1b3153295e7ef4bc42a515ab6
├─ updates (2020-04-30T01:55:47Z)
├─ fedora-cisco-openh264 (2020-03-17T20:10:45Z)
└─ fedora (2020-04-24T11:00:23Z)
StateRoot: fedora
GPGSignature: 1 signature
Signature made Mi 29 Apr 2020 03:07:13 CEST using RSA key ID 6C13026D12C944D0
Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"
InactiveRequests: nano
LayeredPackages: adb […]
ostree://fedora:fedora/32/x86_64/silverblue
Version: 32.20200429.0 (2020-04-29T01:07:05Z)
BaseCommit: 563658b0ee90c737d5248832a097b7ed3f7dee05e1594ea8bd352a2c6f7bb04d
├─ repo-0 ((invalid timestamp))
├─ repo-1 ((invalid timestamp))
└─ repo-2 ((invalid timestamp))
Commit: 9c8bc9aaea1ac6c4ae9a4459883ac805430900220946bcf34f747fded091508c
├─ updates (2020-04-29T01:45:11Z)
├─ fedora-cisco-openh264 (2020-03-17T20:10:45Z)
└─ fedora (2020-04-24T11:00:23Z)
StateRoot: fedora
GPGSignature: 1 signature
Signature made Mi 29 Apr 2020 03:07:13 CEST using RSA key ID 6C13026D12C944D0
Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"
InactiveRequests: nano
LayeredPackages: adb […]
$ rpm-ostree install nano
error: "nano" is already provided by: nano-4.9.1-1.fc32.x86_64. Use --allow-inactive to explicitly require it.
$ rpm-ostree override reset nano
error: No overrides for package 'nano'
Try rpm-ostree override reset nano-4.9.1-1.fc32.x86_64.rpm
then restart and see if the message is cleared.
rugk
(rugk)
April 30, 2020, 7:11pm
7
Nope, get the same messages:
$ rpm-ostree override reset nano-4.9.1-1.fc32.x86_64
error: No overrides for package 'nano-4.9.1-1.fc32.x86_64'
$ rpm-ostree override reset nano-4.9.1-1.fc32.x86_64.rpm
error: No overrides for package 'nano-4.9.1-1.fc32.x86_64.rpm'
As said, I also don’t remember doing any kind of overwrite with nano.
rugk
(rugk)
April 30, 2020, 7:17pm
8
FYI the only information I could find online about “InactiveRequests” is that:
In my case, this messages was always related to overrides being superseded. Can you share output of rpm-ostree upgrade
?
rugk
(rugk)
April 30, 2020, 10:55pm
10
The same, basically:
rpm-ostree upgrade
note: automatic updates (stage) are enabled
1 metadata, 0 content objects fetched; 569 B transferred in 5 seconds
Inactive requests:
nano (already provided by nano-4.9.1-1.fc32.x86_64)
Checking out tree 53eecca... done
Enabled rpm-md repositories: updates fedora-cisco-openh264 fedora
rpm-md repo 'updates' (cached); generated: 2020-04-30T01:55:47Z
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2020-03-17T20:10:45Z
rpm-md repo 'fedora' (cached); generated: 2020-04-24T11:00:23Z
Importing rpm-md... done
Resolving dependencies... done
No upgrade available.
Ok I think I know what has happened. nano
used NOT to be part of the base layer, therefore at some point, you might have installed it manually via rpm-ostree install nano
. Since the package is now part of the base layer, you are getting that message.
You can now remove nano
layer with rpm-ostree uninstall nano
, this will remove that extra layer but keep nano
in the base layer, therefore you will still be able to use nano
.
7 Likes
rugk
(rugk)
May 2, 2020, 2:52pm
12
Exactly, that’s it! Thanks.
1 Like
system
(system)
Closed
May 30, 2020, 2:52pm
13
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.