Describe the issue
The fedora-coreos-pinger module has been added, and does not have a default stream set. I'd like to set the default module stream to rolling, for both F30 and Rawhide.
rolling
When do you need this? (YYYY/MM/DD)
ASAP (2019/07/22).
When is this no longer needed or useful? (YYYY/MM/DD)
The default stream will always be set to rolling, as only the latest upstream release of fedora-coreos-pinger will be used (https://github.com/coreos/fedora-coreos-pinger).
fedora-coreos-pinger
If we cannot complete your request, what is the impact?
The default stream for the module will not be set in Rawhide and F30, meaning it can't be installed without specifying a stream. This does not impact Fedora CoreOS but may impact users wanting to test installation of the package in Rawhide or F30.
Related pull requests: Rawhide: https://pagure.io/releng/fedora-module-defaults/pull-request/138 F30: https://pagure.io/releng/fedora-module-defaults/pull-request/139
Are the packages form that module included in non modular Fedora or not?
Are the packages from the module intended to ever be used as dependencies of things that are not part of this module?
The rust-fedora-coreos-pinger package in this module is included in Rawhide only.
rust-fedora-coreos-pinger
No. Other packages outside of this module should not depend on packages in this module.
This package should only be used in Fedora CoreOS, and will be a standalone service.
This package should only be used in Fedora CoreOS.
How will that work? Do we plan not to have it installable in normal Fedora? Will there be users who manually install this package? If not, why does it need a default stream?
This one should not be filled to FESCo, but to releng. Rust apps have exception from FESCo.
Metadata Update from @ignatenkobrain: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
https://pagure.io/fesco/issue/2122 for the record.
I'm still curios why this needs a default stream.
Is there reason not to? The default stream is set up so that people can do dnf install … like it would be normal non-modular RPM.
dnf install …
I'm still curios why this needs a default stream. Is there reason not to? The default stream is set up so that people can do dnf install … like it would be normal non-modular RPM.
Well, the reason not to would be that it wouldn't get into trouble if the default needs to change later (since we don't have that resolved yet). But given that this is a rolling stream, I don't think it's likely to be a problem. I'll merge the defaults.
This package should only be used in Fedora CoreOS. How will that work? Do we plan not to have it installable in normal Fedora? Will there be users who manually install this package? If not, why does it need a default stream?
The package will be included in the base manifest for Fedora CoreOS, and will not need manually installing in FCOS. The package doesn't need to be installable in normal Fedora, so it doesn't necessarily need the default stream. I just thought it's something that is generally expected for modules (https://bugzilla.redhat.com/show_bug.cgi?id=1729168).
I just thought it's something that is generally expected for modules
See https://pagure.io/fesco/issue/2178#comment-582537
In this very case, i think not having the default stream makes sense, we don't want the users to dnf install fedora-coreos-pinger.
dnf install fedora-coreos-pinger
Login to comment on this ticket.