#154 Changing a behavior of "dnf module install $name:$stream" in case of there is no default module profile
Opened a month ago by jaruga. Modified a month ago

I have suggestion about a behavior of "dnf module install ruby:$profile".

Right now dnf module install ruby:$profile command returns exit status: 0 (success code) only enabling the stream, even when the default profile is not found, and the RPMs in the module are not installed.

Shall we change the behavior not to enable the module stream, and just to return an exist code non-zero?
Because it's hard to find the issue in a script like https://travis-ci.org/junaruga/switch-module-stream/jobs/587097018#L254 .
As I noticed it today, I sent PR to set the default profile to the ruby module on f30 branch. https://pagure.io/releng/fedora-module-defaults/pull-request/163 .
But ideally I wanted to find the issue on earlier phase.

$ podman run --rm -it fedora:30 bash

# dnf module install ruby:2.5
Last metadata expiration check: 0:01:43 ago on Fri Sep 20 13:02:54 2019.
No default profiles for module ruby:2.5
Dependencies resolved.
==============================================================================================
 Package               Architecture         Version               Repository             Size
==============================================================================================
Enabling module streams:
 ruby                                       2.5

Transaction Summary
==============================================================================================

Is this ok [y/N]: y
Complete!

[root@b5ea5f2c8791 /]# echo $?
0

That feels very much like a bug, yes. A DNF bug, to be specific.

@jaruga Can you please open this as a bug in Bugzilla against DNF?

Sure, I will open the ticket in Bugzilla against DNF.

Sure, I will open the ticket in Bugzilla against DNF.

I opened the ticket here.
https://bugzilla.redhat.com/show_bug.cgi?id=1755028

Login to comment on this ticket.

Metadata