However, I would support the idea that Anaconda could have an easy way to
enable testing repositories by clicking on a checkbox, similarly to "Don't
install the latest available software updates ..."
On Wed, Oct 31, 2018 at 3:36 PM Lukas Ruzicka <lruzicka(a)redhat.com> wrote:
Oh, so I did not get it.
I agree that anaconda only should install from stable repos unless told
On Wed, Oct 31, 2018 at 3:24 PM Julen Landa Alustiza <julen(a)zokormazo.info>
> that will allow us to install a working enviroment if there is something
> broken on u-t or if there is something broken on the compose and fixed on
> u-t since we will be able to add the repo during install process.
> Would be great to have a disabled by default checkbox on additional repos
> windows so we don't have to add manually u-t repo when the broken package
> is on the compose
> El mié., 31 oct. 2018 15:09, Stephen Gallagher <sgallagh(a)redhat.com>
>> On Wed, Oct 31, 2018 at 10:01 AM Kamil Paral <kparal(a)redhat.com> wrote:
>> > On Wed, Oct 31, 2018 at 2:48 PM Lukas Ruzicka <lruzicka(a)redhat.com>
>> >> Hello,
>> >> I have been assigned to organize a discussion about this issue
>> >> I have thought about some possibilities (see lower or the issue) how
>> the behaviour should be defined. I would like you to comment on it and add
>> your ideas to the material. I hope this discussion will result in one
>> transparent, documented and testable scenario in the end.
>> >> Thanks a lot.
>> >> Lukas
>> > I agree with Stephen at
, this might be a
>> misunderstanding. I don't think we need to change when updates-testing is
>> enabled/disabled in the installed system. That seems to be working quite
>> fine. But we want to define how anaconda should behave when installing from
>> online repos, whether it should use updates-testing for installation or
>> not, or when.
>> > So the possible options probably are:
>> > * always disabled during installation
>> > * always enabled during installation up to the final RC
>> > * respect the default values in fedora-repos (enabled only as long as
>> it is enabled in the installed system). Note that this is likely decided at
>> compose time.
>> > And then we need to define what happens when the user enables/disables
>> additional updates using the checkbox in "installation source" spoke.
>> in case we keep updates-testing enabled at least sometime, whether the GUI
>> should change somehow to reflect that.
>> I want to cast a vote that anaconda should never enable the
>> updates-testing repository absent an explicit user request (such as
>> adding them as supplementary install sources). The advantage here is
>> that we are far more likely to succeed with installations and then
>> testing will take place once they have a viable starting point.
>> test mailing list -- test(a)lists.fedoraproject.org
>> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
> test mailing list -- test(a)lists.fedoraproject.org
> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
FEDORA QE, RHCE
612 45 Brno - Královo Pole
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
612 45 Brno - Královo Pole
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <