Bug 2317438 - dnf5 module: Unknown argument for command install/switch-to/remove
Summary: dnf5 module: Unknown argument for command install/switch-to/remove
Keywords:
Status: CLOSED DUPLICATE of bug 2221184
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf5
Version: 41
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: rpm-software-management
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-08 22:12 UTC by Kevin Mittman
Modified: 2024-10-17 17:12 UTC (History)
10 users (show)

Fixed In Version:
Clone Of: 2177767
Environment:
Last Closed: 2024-10-17 17:12:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rpm-software-management dnf5 issues 146 0 None open Implement module command 2024-10-15 11:07:49 UTC

Description Kevin Mittman 2024-10-08 22:12:26 UTC
+++ This bug was initially created as a clone of Bug #2177767 +++

Description of problem:
dnf5 module [install|switch-to|remove] not working

Version-Release number of selected component (if applicable):
dnf5 version 5.2.6.2
dnf5 plugin API version 2.0
libdnf5 version 5.2.6.2
libdnf5 plugin API version 2.0

How reproducible:
100%

Steps to Reproduce:
1. podman run -it fedora:41 /bin/bash
2. dnf module install $moduleName

Actual results:
Unknown argument "install" for command "module". Add "--help" for more information about the arguments.

Expected results:
dnf module install $moduleName:$stream/$profile
Installing group/module packages:
 $packageName     $arch      $version      $repoName     $size   
Installing module profiles:
 $moduleName/default                                                                                                             
Enabling module streams:
 $moduleName                                            $stream                                                                


Additional info:
In Fedora 41 (set to release next week) dnf5 is now enabled by default. However, module install, switch-to, etc. sub-commands have not been implemented yet: https://github.com/rpm-software-management/dnf5/issues/146

This will prevent installation of NVIDIA Driver module streams and profiles: https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/index.html#nvidia-driver-installation-instructions-for-fedora
which is needed for functionality such as
* precompiled kmod streams: https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/index.html#precompiled-streams-support-matrix
* other use cases: https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/index.html#modularity-profiles

Previously during Fedora 38 time-frame filed https://bugzilla.redhat.com/show_bug.cgi?id=2177767 

$ dnf module --help
Usage:
  dnf5 [GLOBAL OPTIONS] module <COMMAND> ...
                                
Query Commands:                 
  list                          List module streams
  info                          List module streams
                                
Stream Management Commands:     
  enable                        Enable module streams and make their packages available.
  reset                         Reset module state so it's no longer enabled or disabled.
  disable                       Disable modules including all their streams.

Comment 1 Kevin Mittman 2024-10-14 15:50:16 UTC
Ping, looking for some explanation and next steps

Comment 2 Petr Pisar 2024-10-15 10:58:45 UTC
Yes. DNF5 does not implement these commands <https://github.com/rpm-software-management/dnf5/issues/146>. Modularity is not a priority for Fedora as Fedora stopped using it. If you need these commands, you can implement them yourself and offer the code as as pull request in DNF5 upstream. The linked ticket also offers a workaround for missing "dnf5 module install" command.

Comment 3 Philipp Stanner 2024-10-17 13:39:24 UTC
Hello Kevin,

from our side, as of right now, Modularity is planned for inclusion within DNF5. This is subject to change, but as of right now that is the overall plan. Implementation would likely happen mid-term rather than short term.

Overall, we discourage using modularity and encourage to use named packages instead.

Hope this helps

Comment 4 Petr Pisar 2024-10-17 17:12:13 UTC

*** This bug has been marked as a duplicate of bug 2221184 ***


Note You need to log in before you can comment on or make changes to this bug.