Silverblue; rpm-ostree; can not upgrade; cannot install both ... from fedora and ... from @System

Ask Fedora
1

Hello all.

I can not upgrade my Silverblue.

> rpm-ostree status

State: idle
Deployments:
● fedora:fedora/41/x86_64/testing/silverblue
                  Version: 41.20241209.0 (2024-12-09T01:01:16Z)
               BaseCommit: ad19cbb80e3bf76a60acc63f528bb276a828eb025376a9c960d6b81ab879c1de
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
          LayeredPackages: alsamixergui android-tools arm-image-installer bibata-cursor-themes borgbackup candy-icon-theme.noarch clamav clamav-freshclam clamd clamtk clang cmake corectrl cpu-x ctags dconf-editor devscripts-checkbashisms
                           duf fuse-sshfs geany geany-plugins-addons geany-plugins-autoclose geany-plugins-automark geany-plugins-codenav geany-plugins-commander geany-plugins-common geany-plugins-debugger geany-plugins-defineformat
                           geany-plugins-geanyctags geany-plugins-geanydoc geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanymacro geany-plugins-geanyminiscript
                           geany-plugins-geanynumberedbookmarks geany-plugins-geanypg geany-plugins-geanyprj geany-plugins-geanyvc geany-plugins-geniuspaste geany-plugins-git-changebar geany-plugins-keyrecord geany-plugins-latex
                           geany-plugins-lineoperations geany-plugins-lipsum geany-plugins-markdown geany-plugins-overview geany-plugins-pairtaghighlighter geany-plugins-pohelper geany-plugins-pretty-printer
                           geany-plugins-projectorganizer geany-plugins-scope geany-plugins-sendmail geany-plugins-shiftcolumn geany-plugins-spellcheck geany-plugins-tableconvert geany-plugins-treebrowser geany-plugins-updatechecker
                           geany-plugins-vimode geany-plugins-webhelper geany-plugins-workbench geany-plugins-xmlsnippets geany-themes gnome-themes-extra gnome-tweaks gparted grub2-tools-extra gtk3-devel gtkd-geany-tags hwinfo info inxi
                           iperf3 java-latest-openjdk-devel joystick-support lshw lshw-gui mingw64-gcc neovim ninja-build nvme-cli piper.noarch policycoreutils-gui pv shellcheck smartmontools stow stress subversion subversion-tools
                           sysstat tmux wayvnc WoeUSB

> rpm-ostree upgrade
...
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package gtk3-devel-3.24.43-2.fc41.x86_64 from fedora requires pkgconfig(pango) >= 1.41.0, but none of the providers can be installed
  - package gtk3-devel-3.24.43-2.fc41.x86_64 from fedora requires pkgconfig(pangocairo) >= 1.41.0, but none of the providers can be installed
  - package gtk3-devel-3.24.43-2.fc41.x86_64 from fedora requires pkgconfig(pangoft2), but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.x86_64 from fedora requires pkgconfig(xrender), but none of the providers can be installed
  - package gtk3-devel-3.24.43-2.fc41.i686 from fedora requires libpango-1.0.so.0, but none of the providers can be installed
  - package gtk3-devel-3.24.43-2.fc41.i686 from fedora requires libpangocairo-1.0.so.0, but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.i686 from fedora requires pango(x86-32) = 1.54.0-2.fc41, but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.i686 from fedora requires libpango-1.0.so.0, but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.i686 from fedora requires libpangocairo-1.0.so.0, but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.i686 from fedora requires libpangoft2-1.0.so.0, but none of the providers can be installed
  - package pango-devel-1.54.0-2.fc41.i686 from fedora requires libpangoxft-1.0.so.0, but none of the providers can be installed
  - package libXrender-devel-0.9.11-7.fc41.i686 from fedora requires libXrender.so.1, but none of the providers can be installed
  - package libXrender-devel-0.9.11-7.fc41.x86_64 from fedora requires libXrender = 0.9.11-7.fc41, but none of the providers can be installed
  - package pango-1.54.0-2.fc41.i686 from fedora requires libXrender.so.1, but none of the providers can be installed
  - libXrender-0.9.11-7.fc41.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both libXrender-0.9.11-7.fc41.x86_64 from fedora and libXrender-0.9.12-1.fc41.x86_64 from @System

Hope You can help.

P.S.
What is this @System repo ???

> dnf4 repolist all

does not show that repo.

2

rpm-ostree status please

3 
> rpm-ostree status

State: idle
Deployments:
● fedora:fedora/41/x86_64/testing/silverblue
                  Version: 41.20241209.0 (2024-12-09T01:01:16Z)
               BaseCommit: ad19cbb80e3bf76a60acc63f528bb276a828eb025376a9c960d6b81ab879c1de
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
          LayeredPackages: alsamixergui android-tools arm-image-installer bibata-cursor-themes borgbackup candy-icon-theme.noarch clamav clamav-freshclam clamd clamtk clang cmake corectrl cpu-x ctags dconf-editor devscripts-checkbashisms
                           duf fuse-sshfs geany geany-plugins-addons geany-plugins-autoclose geany-plugins-automark geany-plugins-codenav geany-plugins-commander geany-plugins-common geany-plugins-debugger geany-plugins-defineformat
                           geany-plugins-geanyctags geany-plugins-geanydoc geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanymacro geany-plugins-geanyminiscript
                           geany-plugins-geanynumberedbookmarks geany-plugins-geanypg geany-plugins-geanyprj geany-plugins-geanyvc geany-plugins-geniuspaste geany-plugins-git-changebar geany-plugins-keyrecord geany-plugins-latex
                           geany-plugins-lineoperations geany-plugins-lipsum geany-plugins-markdown geany-plugins-overview geany-plugins-pairtaghighlighter geany-plugins-pohelper geany-plugins-pretty-printer
                           geany-plugins-projectorganizer geany-plugins-scope geany-plugins-sendmail geany-plugins-shiftcolumn geany-plugins-spellcheck geany-plugins-tableconvert geany-plugins-treebrowser geany-plugins-updatechecker
                           geany-plugins-vimode geany-plugins-webhelper geany-plugins-workbench geany-plugins-xmlsnippets geany-themes gnome-themes-extra gnome-tweaks gparted grub2-tools-extra gtk3-devel gtkd-geany-tags hwinfo info inxi
                           iperf3 java-latest-openjdk-devel joystick-support lshw lshw-gui mingw64-gcc neovim ninja-build nvme-cli piper.noarch policycoreutils-gui pv shellcheck smartmontools stow stress subversion subversion-tools
                           sysstat tmux wayvnc WoeUSB

  fedora:fedora/40/x86_64/silverblue
                  Version: 40.20241202.0 (2024-12-02T05:35:56Z)
               BaseCommit: 3ad1f7839b5f0da0d5a588cc72cecef4b5b5d0f5801cddbb245e7be8d1f4c318
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
          LayeredPackages: alsamixergui android-tools arm-image-installer bibata-cursor-themes borgbackup candy-icon-theme.noarch clamav clamav-freshclam clamd clamtk clang cmake corectrl cpu-x ctags dconf-editor devscripts-checkbashisms
                           duf fuse-sshfs geany geany-plugins-addons geany-plugins-autoclose geany-plugins-automark geany-plugins-codenav geany-plugins-commander geany-plugins-common geany-plugins-debugger geany-plugins-defineformat
                           geany-plugins-geanyctags geany-plugins-geanydoc geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanymacro geany-plugins-geanyminiscript
                           geany-plugins-geanynumberedbookmarks geany-plugins-geanypg geany-plugins-geanyprj geany-plugins-geanyvc geany-plugins-geniuspaste geany-plugins-git-changebar geany-plugins-keyrecord geany-plugins-latex
                           geany-plugins-lineoperations geany-plugins-lipsum geany-plugins-markdown geany-plugins-overview geany-plugins-pairtaghighlighter geany-plugins-pohelper geany-plugins-pretty-printer
                           geany-plugins-projectorganizer geany-plugins-scope geany-plugins-sendmail geany-plugins-shiftcolumn geany-plugins-spellcheck geany-plugins-tableconvert geany-plugins-treebrowser geany-plugins-updatechecker
                           geany-plugins-vimode geany-plugins-webhelper geany-plugins-workbench geany-plugins-xmlsnippets geany-themes gnome-themes-extra gnome-tweaks gparted grub2-tools-extra gtk3-devel gtkd-geany-tags hdparm hwinfo
                           info inxi iperf3 java-latest-openjdk-devel joystick-support lshw lshw-gui mingw64-gcc neovim ninja-build nvme-cli piper.noarch policycoreutils-gui pv shellcheck smartmontools stow stress subversion
                           subversion-tools sysstat tmux wayvnc WoeUSB

  fedora:fedora/40/x86_64/silverblue
                  Version: 40.20241104.0 (2024-11-04T01:02:55Z)
               BaseCommit: fd6925c62080a54f9f494df2c84dd3bbfe578c77b9762f3ca4bdb4a4b28088b0
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
          LayeredPackages: alsamixergui android-tools arm-image-installer bibata-cursor-themes borgbackup candy-icon-theme.noarch celestia clamav clamav-freshclam clamd clamtk clang cmake corectrl cpu-x ctags dconf-editor
                           devscripts-checkbashisms duf fuse-sshfs geany geany-plugins-addons geany-plugins-autoclose geany-plugins-automark geany-plugins-codenav geany-plugins-commander geany-plugins-common geany-plugins-debugger
                           geany-plugins-defineformat geany-plugins-geanyctags geany-plugins-geanydoc geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanymacro
                           geany-plugins-geanyminiscript geany-plugins-geanynumberedbookmarks geany-plugins-geanypg geany-plugins-geanyprj geany-plugins-geanyvc geany-plugins-geniuspaste geany-plugins-git-changebar
                           geany-plugins-keyrecord geany-plugins-latex geany-plugins-lineoperations geany-plugins-lipsum geany-plugins-markdown geany-plugins-overview geany-plugins-pairtaghighlighter geany-plugins-pohelper
                           geany-plugins-pretty-printer geany-plugins-projectorganizer geany-plugins-scope geany-plugins-sendmail geany-plugins-shiftcolumn geany-plugins-spellcheck geany-plugins-tableconvert geany-plugins-treebrowser
                           geany-plugins-updatechecker geany-plugins-vimode geany-plugins-webhelper geany-plugins-workbench geany-plugins-xmlsnippets geany-themes gnome-themes-extra gnome-tweaks gparted grub2-tools-extra gtk3-devel
                           gtkd-geany-tags hdparm hwinfo info inxi iperf3 java-latest-openjdk-devel joystick-support lshw lshw-gui mingw64-gcc neovim ninja-build nvme-cli piper.noarch policycoreutils-gui pv shellcheck smartmontools stow
                           stress subversion subversion-tools sysstat tmux wayvnc WoeUSB
                   Pinned: yes
4

Silverblue and Fedora atomic desktops in general are thought to be used with container-focused workflows whenever possible. While there’s nothing wrong in layering packages on top of OSTree deployments, this opens up the chances of depsolve issues, just as in traditional (non-atomic) desktops, and the chances increase with the number of packages layered.

I would go and try to figure out why is it that a newer version of libXrender is installed on the system than the one available in the repos (0.9.12-1 vs 0.9.11-7).

Given that libXrender-devel probably got installed as a dependency of the layered gtk3-devel package, uninstalling the latter (if acceptable) might solve the issue.

You might find it easier to install gtk3-devel later in a container, if this is an acceptable workflow for your development work.

5

Today this problem is gone :slight_smile:
It look like someone was listening to me and fixed it :slight_smile:

But today another problem arises:

Resolving dependencies... done                                                                                        │Available Packages
error: Could not depsolve transaction; 1 problem detected:                                                            │Name         : gtk3-devel
 Problem: conflicting requests                                                                                        │Version      : 3.24.43
  - package policycoreutils-gui-3.7-5.fc41.noarch from updates requires python3-policycoreutils = 3.7-5.fc41, but none│Release      : 2.fc41
 of the providers can be installed                                                                                    │Architecture : i686
  - package policycoreutils-gui-3.7-5.fc41.noarch from updates-archive requires python3-policycoreutils = 3.7-5.fc41, │Size         : 4.3 M
but none of the providers can be installed                                                                            │Source       : gtk3-3.24.43-2.fc41.src.rpm
  - package policycoreutils-gui-3.7-3.fc41.noarch from fedora requires python3-policycoreutils = 3.7-3.fc41, but none │Repository   : fedora
of the providers can be installed                                                                                     │Summary      : Development files for GTK+
  - cannot install both python3-policycoreutils-3.7-5.fc41.noarch from updates and python3-policycoreutils-3.7-6.fc41.│URL          : https://gtk.org
noarch from @System                                                                                                   │License      : LGPL-2.0-or-later
  - cannot install both python3-policycoreutils-3.7-3.fc41.noarch from fedora and python3-policycoreutils-3.7-6.fc41.n│Description  : This package contains the libraries and header files that are needed
oarch from @System                                                                                                    │             : for writing applications with version 3 of the GTK+ widget toolkit. If
  - cannot install both python3-policycoreutils-3.7-5.fc41.noarch from updates-archive and python3-policycoreutils-3.7│             : you plan to develop applications with GTK+, consider installing the
-6.fc41.noarch from @System

So I am just going to wait.

Because I have seen such problems from time to time in past but it was always few days and they were gone.
But this problem with libXrender was lasting about month so I got confused and asked how to fix it.

I can uninstall gtk3-devel anyway - actually just did it.

I also wish to present my point of view about Silverblue approach.
Please understand this is a view of just a simple basic regular OS user which enjoy simplicity os using this OS.

With Silverblue:

  • system upgrades are blessing,
  • they are Holy Grail of OS upgrades
  • something that every OS wish to have.
  • OS upgrades are super easy,
  • you can not brake things,
    but if you try and break it somehow you can just switch back.

I remember how miserable I felt when I had to install never version of Fedora and all things along it, or upgrade it manually hoping nothing gets break, before Silverblue came.
But with Silverblue this aspect of upgrading OS is a sunny breeze on my face.

I have installed Silverblue in 2018 or 2019 so it was version 29 or 31 and all I did since then was rpm-ostee rebase and I am on a newest version.
It feels even simpler then upgrading my phone OS.
This feature is something truly amazing, something that should be loudly advertised.
You can simply install your OS once and then just upgrade it forever.
No need to reinstall OS from scratch,
no need to backup, wipe out, install again, restore all the software or data that you have.

So in summary Silverblue for me is a system which I can install just once, install things I need to use, simply upgrade stuff forever and not be able to broke it by myself.

(Containers - had no need no reasons to use it as I do not thinker with OS development itself).

It is just my personal point of view I wish to share with You hoping you can understand why I like It so much that I wish Silverblue to be continued forever :slight_smile:

6

I also consider that the concept of atomic desktops is really appealing. I am using Silverblue myself.

Regarding your last (and previous) issue, it looks as if packages from updates testing are available in your deployments. And this is confirmed fro your output of rpm-ostree status, as it looks like you have rebased your system to F41 testing, instead of F41 stable. That is, your deployment branch reads fedora:fedora/41/x86_64/testing/silverblue instead of fedora:fedora/41/x86_64/silverblue.

And I assume that the upgrades-testing repo for package layering is disabled, which brings the issues you have experienced. You can check it with cat /etc/yum.repos.d/fedora-updates-testing.repo.

It the above is true, then you should either rebase to the stable branch, or, if you’d prefer to stay on the testing branch, then enabled the updates-testing repos as well.

7

Yes I was on testing - my mistake - rebased to release and all is fine.

I also want to ask some more questions.

“Clean” Silverblue installation does not have dnf.
But mine has.

Because rpm-ostree misses few options I find it useful to have dnf4 and use it not to install or upgrade but for the options rpm-ostree misses, like for example:

repolist

> dnf4 repolist all

or
whatprovides

> dnf4 whatprovides dnf4

Fedora 41 - x86_64 - Updates                                                                                                                                                                                 9.6 MB/s |  23 MB     00:02    
Fedora 41 - x86_64 - Updates Archive                                                                                                                                                                          11 MB/s |  32 MB     00:02    
Last metadata expiration check: 0:00:13 ago on Wed 08 Jan 2025 11:12:18 AM CET.
python3-dnf-4.21.1-1.fc41.noarch : Python 3 interface to DNF
Repo        : fedora
Matched from:
Filename    : /usr/bin/dnf4

python3-dnf-4.21.1-2.fc41.noarch : Python 3 interface to DNF
Repo        : updates-archive
Matched from:
Filename    : /usr/bin/dnf4

python3-dnf-4.22.0-1.fc41.noarch : Python 3 interface to DNF
Repo        : @System
Matched from:
Filename    : /usr/bin/dnf4

python3-dnf-4.22.0-1.fc41.noarch : Python 3 interface to DNF
Repo        : updates
Matched from:
Filename    : /usr/bin/dnf4

python3-dnf-4.22.0-1.fc41.noarch : Python 3 interface to DNF
Repo        : updates-archive
Matched from:
Filename    : /usr/bin/dnf4

or
list

> dnf4 list python3-dnf
Fedora 41 - x86_64                                                                                                                                                                                            34 kB/s |  27 kB     00:00    
Fedora 41 openh264 (From Cisco) - x86_64                                                                                                                                                                     1.6 kB/s | 989  B     00:00    
History database cannot be created, using in-memory database instead: SQLite error on "/var/lib/dnf/history.sqlite": Open failed: unable to open database file
Installed Packages
python3-dnf.noarch                                                                                                   4.22.0-1.fc41                                                                                                    @System

(although here I know I can use rpm-ostre search but dnf4 list output is neater for me and I can use regexp for it).

1) Is it ok to have dnf in silverblue and use it in a manner like I described or is it bad idea after all ?

2) What this @System exactly stands for ?

3) I did not rpm-ostree install python3-dnf
so it has to come as a dependency of another package ?
Is there a way to track why it was installed, what other package dependency it is ?

8

Note; to rebase to stable, run this:

rpm-ostree rebase fedora:fedora/41/x86_64/silverblue

You do have a lot of overlays too. The more you have, the more likely you might hit a dependency resolution problem like this, especially in the testing branch of Silverblue or any other testing Atomic build. (You shouldn’t really hit these in stable, but sometimes it happens.) The more overlays you have, the longer it takes to update too. (Which isn’t a huge issue, as you can update in the background and reboot when done.)

Many of your overlays would probably be better to use from within a toolbox or via flatpak, depending on the package. (Development tools are generally better within toolbox (or distrobox) containers, graphical apps are generally better from flatpaks.)

This all said, all your packages cleanly install on stable, except for bibata-cursor-themes which isn’t packaged in Fedora. (I spun up a VM in the background with the latest Silverblue stable and told it to install your packages. It took like 2 minutes, aside from having it do some stuff in the background.)

If you can’t rebase with the simple line, you can try removing the package first and then rebasing. But the simple methods probably won’t work as you have a dependency issue, so you will first have to do a reset, then rebase, then overlay all your files, like this:

  1. save what you currently have with sudo ostree pin 0 (and if 0 doesn’t work, if you tried doing something with rpm-ostree already, then use 1 instead)
  2. rpm-ostree reset -ol
  3. reboot
  4. rpm-ostree rebase fedora:fedora/41/x86_64/silverblue
  5. reboot
  6. rpm-ostree install alsamixergui android-tools arm-image-installer borgbackup candy-icon-theme.noarch clamav clamav-freshclam clamd clamtk clang cmake corectrl cpu-x ctags dconf-editor devscripts-checkbashisms duf fuse-sshfs geany geany-plugins-addons geany-plugins-autoclose geany-plugins-automark geany-plugins-codenav geany-plugins-commander geany-plugins-common geany-plugins-debugger geany-plugins-defineformat geany-plugins-geanyctags geany-plugins-geanydoc geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanymacro geany-plugins-geanyminiscript geany-plugins-geanynumberedbookmarks geany-plugins-geanypg geany-plugins-geanyprj geany-plugins-geanyvc geany-plugins-geniuspaste geany-plugins-git-changebar geany-plugins-keyrecord geany-plugins-latex geany-plugins-lineoperations geany-plugins-lipsum geany-plugins-markdown geany-plugins-overview geany-plugins-pairtaghighlighter geany-plugins-pohelper geany-plugins-pretty-printer geany-plugins-projectorganizer geany-plugins-scope geany-plugins-sendmail geany-plugins-shiftcolumn geany-plugins-spellcheck geany-plugins-tableconvert geany-plugins-treebrowser geany-plugins-updatechecker geany-plugins-vimode geany-plugins-webhelper geany-plugins-workbench geany-plugins-xmlsnippets geany-themes gnome-themes-extra gnome-tweaks gparted grub2-tools-extra gtk3-devel gtkd-geany-tags hwinfo info inxi iperf3 java-latest-openjdk-devel joystick-support lshw lshw-gui mingw64-gcc neovim ninja-build nvme-cli piper.noarch policycoreutils-gui pv shellcheck smartmontools stow stress subversion subversion-tools sysstat tmux wayvnc WoeUSB
  7. reboot

(The reboots in step 2 and 4 might not be needed, but you might hit an issue when dependency resolving otherwise.)

You’re basically hitting this issue because you are overlaying a lot of things and using testing. If you’re overlaying a lot of things, stick to stable. And ideally (although not completely necessary), try to use containers and flatpaks when you can. For what it’s worth, I do have a good number of overlays too, but I also try to stick to Flatpaks for apps and containers for development work.

9

As a general opinion, I recommend installing packages as follows:

  • GUI apps as flatpaks;
  • other apps, tools, themes etc layered as packages on top of OSTree deployments only when there is a real need to have it “system-wide”;
  • other CLI tools in a Toolbx container, using the default image for the given release.

Note that it is quite easy to create containers with Toolbx, and the new ptyxis terminal is also featured to integrate them (e.g. instead of running toolbox enter, you just open a new tab with the given container).

I didn’t layer dnf on top of my deployments, given that it would rather have limited functionality. For querying packages I’m using:

  • rpm -qa, for packages in the base tree image or for layered packages (takes many similar options as dnf)
  • dnf (dnf5 being the new version) inside the default container for other queries, such as not installed packages etc.

@<packageSource> would show on traditional systems the repo where it was installed from. IIRC, @System would mean the package is from the base install, which would also make sense in OSTree-based editions.

I confirm having this package installed as well. I don’t know why it is provided with the OSTree image, but you can run queries with rpm -q --whatrequires <capability>, or dnf rq --whatrequires <capability> to query all the packages in the repos, not only the installed ones.

10

Apparently the package python3-dnf provides dnf4:

$ rpm -q --list  python3-dnf | grep bin
/usr/bin/dnf-3
/usr/bin/dnf4

Probably there for the query and list commands (given that rpm-ostree search is more limited in functionality, as you have noticed). I don’t know why dnf4 is provided but not dnf5 though.

11 
# 0)
> rpm -q --whatprovides /usr/bin/dnf4
python3-dnf-4.22.0-1.fc41.noarch

> rpm -q --whatrequires python3-dnf
policycoreutils-devel-3.7-5.fc41.x86_64
python3-dnf-plugins-core-4.10.0-1.fc41.noarch

# 1a)
> rpm -q --whatrequires python3-dnf-plugins-core
dnf-plugins-core-4.10.0-1.fc41.noarch

> rpm -q --whatrequires dnf-plugins-core
no package requires dnf-plugins-core

> rpm -qa | grep dnf-plugins
python3-dnf-plugins-core-4.10.0-1.fc41.noarch
dnf-plugins-core-4.10.0-1.fc41.noarch

# 1b)
> rpm -q --whatrequires policycoreutils-devel
policycoreutils-gui-3.7-5.fc41.noarch

> rpm -qa | grep policycoreutils-gui
policycoreutils-gui-3.7-5.fc41.noarch

It looks like dnf4 comes with “clean” deploy with python3-dnf that is required by python3-dnf-plugins-core that is required by dnf-plugins-core.

Also why policycoreutils-gui requires policycoreutils-devel ?

I do like that:

  • If gui application installed with Flatpak works ok I use it
    (although one of biggest disadvantage is it huge size).
    For example: Remmina, Syncthing.
  • But sometimes I have different problem to make Flatpak applications work ok, like for example
    • Steam that did not handled steam controller when playing “Unravel 2” one player on keyboard and second player on controller,
    • or Geany for which there are no Geany Plugins in Flatpak version and I gave up manually downloading and installing them each time Geany is updated.
    • I am not sure if installing “hardware related” apps like for example Gparted or Corectl with Flatpaks is good idea ?
    • I also had to take care of Librewolf and Keepassxc to make them cooperate: Librewolf - Firefox - KeePassXC - Flatpak
  • For non gui tools - having toolbox is an extra step for me which I want to avoid at all cost - because I have to upgrade it alongside my Silverblue what “takes me back in my personal OS usage experience feeling” to “harsh” preSilverblue era.
  • So I just overlay some rpm-packages and it works so much perfectly for all these years for me :slight_smile:
1 Like