Description of problem:
When going from one stream of nodejs to another (especially going up 10 -> 12, but ideally also when going down), the user experience should be nice. This is a specific requirement from PM (Brian), so we should make sure it works fine and that it is also tested.
So far, this looks quite good to me, so this bug might turn into testing only one, but leave developers and QE to re-consider whether we can do something more.
Steps I used to upgrade from stream 10 to 12:
1. yum -y install node\*
2. yum -y module reset nodejs
3. yum -y module enable nodejs:12
4. yum -y update
Steps I used to downgrade from stream 12 to 10:
1. yum -y module reset nodejs
2. yum -y module enable nodejs:10
3. yum -y distro-sync
After upgrade, all packages were updated.
After downgrade (distro-sync), nodejs-libs was left, which is probably not a problem (at least I don't see a problem with that, if the package only includes a dynamic library).
So far it looks expected, but we should make sure it is the best UX we can offer to users with the current tooling (i.e. what yum provides).
It looks like the following two commands do pretty good job as well, although it is not clear to me whether they do everything we need when switching the streams, but they are very simple:
# dnf install @nodejs:10
# dnf install @nodejs:12
(In reply to Honza Horak from comment #1)
> # dnf install @nodejs:10
> # dnf install @nodejs:12
I meant `yum` ^^^ of course...
Anyway, one issue I spotted is that when going 12 -> 10 using just `yum install @nodejs:10`, then `nodejs-packaging` is not downgraded and I had to run `yum distro-sync` to get nodejs-packaging from nodejs:10 module. This is probably not a big issue, it should just be documented maybe..
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.