Installed package if tried installing again proceeds with deprecated message


#1

This is why I got on Silverblue 29

$ rpm-ostree install podman
warning: deprecated: “podman” is already provided by: podman-1:0.8.4-1.git9f9b8cf.fc29.x86_64. Use --allow-inactive to squash this warning. A future release will make this a requirement. See rpm-ostree(1) for details.
Checking out tree d5b6089… done
Inactive requests:
podman (already provided by podman-1:0.8.4-1.git9f9b8cf.fc29.x86_64)
Enabled rpm-md repositories: fedora updates updates-testing
rpm-md repo ‘fedora’ (cached); generated: 2018-09-18 10:02:34
rpm-md repo ‘updates’ (cached); generated: 2018-02-20 19:18:14
rpm-md repo ‘updates-testing’ (cached); generated: 2018-09-18 06:12:38
Importing metadata [=============] 100%
Resolving dependencies… done
Checking out packages (13/13) [=============] 100%
Running pre scripts… 0 done
Running post scripts… 16 done
Writing rpmdb… done
Writing OSTree commit… done
Copying /etc changes: 11 modified, 0 removed, 31 added
Transaction complete; bootconfig swap: no; deployment count change: 0
Freed: 48.5 kB (pkgcache branches: 0)
Run “systemctl reboot” to start a reboot

I want to know why this command proceed and not abort or errors out? What is that deprecated message mean?


#2

As the warning mentions, rpm-ostree(1) has more details: https://github.com/projectatomic/rpm-ostree/blob/ea5bec612708fd41bde55e922d4e7071885321dc/man/rpm-ostree.xml#L237 (except the text mentions it’s now a hard error, which it is in the latest release, but on the release you’re running on, it’s still set to a warning for now.

If you want more gory details, check out:

And the patch that introduces --allow-inactive: