Description of problem: Installing incus-agent installs the entire incus stack. Per https://manpages.debian.org/unstable/incus-agent/incus-agent.1.en.html, incus-agent is a "daemon to be run inside virtual machines managed by Incus." Installing the agent on the VM guest should not install the entire incus platform. Version-Release number of selected component (if applicable): 6.19.1 How reproducible: Every time Steps to Reproduce: 1. Install incus-agent using dnf: `dnf -y install incus-agent` Actual results: The entire incus stack is installed: ``` Transaction Summary: Installing: 95 packages ``` Compare to package installation on Debian 13: ``` apt-get install incus-agent Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: liblockfile-bin liblockfile1 Use 'apt autoremove' to remove them. The following NEW packages will be installed: incus-agent 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 4,413 kB of archives. After this operation, 15.1 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian-security trixie-security/main amd64 incus-agent amd64 6.0.4-2+deb13u5 [4,413 kB] Fetched 4,413 kB in 1s (3,653 kB/s) Selecting previously unselected package incus-agent. (Reading database ... 64311 files and directories currently installed.) Preparing to unpack .../incus-agent_6.0.4-2+deb13u5_amd64.deb ... Unpacking incus-agent (6.0.4-2+deb13u5) ... Setting up incus-agent (6.0.4-2+deb13u5) ... Processing triggers for man-db (2.13.1-1) ... ``` Expected results: Only the incus agent is installed Additional info:
I'm not the maintainer, but I took a look at this and I see that incus-agent has an explicit dependency on incus, which I would guess is incorrect. Here's a PR to change that. https://src.fedoraproject.org/rpms/incus/pull-request/11 That will reduce the dependencies somewhat, but I'll note that incus-agent still has nine recommends weak dependencies, which are installed by default and pull in a good number of other things. You can trim that down even further with the flag `--setopt install_weak_deps=0` on a case by case basis.
FEDORA-2026-9e8227d6dd (incus-6.23-3.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-9e8227d6dd
FEDORA-2026-9e8227d6dd (incus-6.23-3.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-094b7621cf (incus-6.23-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-094b7621cf
FEDORA-2026-4481307278 (incus-6.23-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4481307278
FEDORA-2026-22feefa810 (incus-6.23-3.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-22feefa810
Sorry for my late reply. Somehow my Web browsers are not very fond of the RHBZ authentication mechanisms so I'm rarely around here but as your PR was merged yesterday in rawhide I quickly wanted to express my concern. This bug is a duplicate of #2421161. I don't understand why the agent package must be installable on its own. In my opinion (I'm the original packager of Incus) it's clearly an extension to the incus base package. See e.g. how Gentoo is doing it [1]. No matter which approach will be chosen now the `recommends` on the agent subpackage is definitely wrong as qemu is likely not recommended if the agent should be installed standalone. I recommend against stabilizing the package at it is now. [1]: https://github.com/gentoo/gentoo/commit/aaa2da0f623783d98a6298da5798fa82e0d1f3fc#diff-f574a9a937f92b6dc4c8777a436f1182071b03a65b6b6ce13782746faaf6348bR215-R221
FEDORA-2026-4481307278 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4481307278` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4481307278 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-22feefa810 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-22feefa810` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-22feefa810 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-094b7621cf has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-094b7621cf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-094b7621cf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I replied in https://bugzilla.redhat.com/show_bug.cgi?id=2421161#c4. If you don't want this update to go to stable (and I agree that it's incomplete, a full fix would be what I described in https://bugzilla.redhat.com/show_bug.cgi?id=2421161), then you should vote -1 on the update in bodhi.
FEDORA-2026-094b7621cf (incus-6.23-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-4481307278 (incus-6.23-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-22feefa810 (incus-6.23-3.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.