This is a surprise to me. If setting the date & time is not already mandatory, it should be.
Are you sure the invalid certificates that you mention are due to wrong date?

Summary: Set date & time zone should be a regular mandatory step => Set date & time zone should be a regular mandatory step; some certificates fail if it is not sensible
CC: (none) => lewyssmith
Assignee: bugsquad => pkg-bugs

(In reply to Lewis Smith from comment #1)
> This is a surprise to me. If setting the date & time is not already
> mandatory, it should be.
> Are you sure the invalid certificates that you mention are due to wrong date?

Quite sure in one or my test, I just install without add repositories.
Then add the repositories in the installed system, perform an update and see the complaints related
Then I remember see and ask for that before and check the date, it was wrong.

Late I do just other installation without add repositories, and in the summary step set timezone -> date, and select to make update and things goes better

Currently, this setup is optional and is in the summary step, my proposal is move as part of the installation/updates/upgrade process.

Fascinating. It is in the docs:
https://doc.mageia.org/installer/9/en/content/locale.html#selectCountry

Quote:

Select your country or region. This is important for all kinds of settings, like the currency and wireless regulatory domain. Setting the wrong country can lead to being unable to use a Wireless network.

(In reply to sturmvogel from comment #3)
> Fascinating. It is in the docs:
> https://doc.mageia.org/installer/9/en/content/locale.html#selectCountry
(In reply to sturmvogel from comment #4)
> Quote:
> 
> Select your country or region. This is important for all kinds of settings,
> like the currency and wireless regulatory domain. Setting the wrong country
> can lead to being unable to use a Wireless network.

That make that not being a mandatory step in the installation/update workflow, even worst, in the part that is located right is not useful with the new crypto-policies-script, if you select add repositories in https://doc.mageia.org/installer/9/en/content/software.html you will find that some packages will not install and let you with no other choose to back to select not use additional repositories, and this is with just "few days" after the alpha 1 round 2 ISOs, I don't want to think if you try to install Mageia 10 after N months of his release(when be released).

(In reply to sturmvogel from comment #3)
> Fascinating. It is in the docs:
> https://doc.mageia.org/installer/9/en/content/locale.html#selectCountry
Indeed. But it is true that you have to specifically choose to configure the timezone etc. In that sense it is optional: you can easily overlook it:
"DrakX presents a proposal for the configuration of your system depending on the choices you made so far...You can check the settings here and change them if you want by pressing Configure".

I think what José is getting at is that this step should be in-line unavoidable, like our own and other distribuion Lives.

I just tried an upgrade from the Round 2 CI, but when I attempted to add supplemental network media before proceeding it failed with one of these bad signature messages. At no time before that was there any option for the user to set date and/or time.

There was language, EULA, install or upgrade, keyboard layout, then do you have a supplementary medium. And when I select HTTP or FTP on the network, it fails when trying to install the basic software to access the network.

Upgrades will never work properly unless this is fixed. Upgrading the bug to release blocker.

CC: (none) => andrewsfarm
Priority: Normal => release_blocker
Severity: normal => major

Created attachment 15260 [details]
Fail installing packages

Created attachment 15261 [details]
Bug information

(In reply to katnatek from comment #8)
> Created attachment 15260 [details]
> Fail installing packages

(In reply to katnatek from comment #9)
> Created attachment 15261 [details]
> Bug information

I fake the date in my system and here are the results
This is a clean installation

As I guess 

change to a terminal Ctrl+Alt+F2
set the right date/time date --set="<day> <month abbreviation in english> <year> <hour>"

The bad thing is you have to pass utc hour or include information after <hour> like CST in my case

So the recommendation have to be "Check your internal clock is right before try an installation/upgrade with additional repositories" if this feature can't be implemented in mageia 10

For errata if not solved
In retrospect, should probably have been in earlier erratas too.

CC: (none) => fri
Keywords: (none) => FOR_ERRATA10
Target Milestone: --- => Mageia 10

(In reply to Morgan Leijström from comment #12)
> For errata if not solved
> In retrospect, should probably have been in earlier erratas too.

I add a note in release notes where is more useful than in erratas, feel free of create the errata or remove the for_errata keyword

Keywords: (none) => IN_RELEASENOTES10

Great, thanks.
And thank you for editing release notes and errata, usually I have been doing most of errata last years but I like to step back :-)

Keywords: FOR_ERRATA10 => (none)

We seem to agree that setting date/time is an essential step. It is currently offered only by the 'summary' screen, which clearly most users heed.
Many other distributions - and I think our own Live ISOs - make it one of the initial installation steps.
This bug is really an enhancement request for the Classic installer. It is not a release blocker. The fact is noted in ERRATA for the moment. For us, it basically means inserting an extra step early in the installation, copying (not moving) the code from its current placement; but leaving the relevant Summary screen & processes UNchanged.

Assigning to tools for the Installer.

CC: lewyssmith => (none)
Priority: release_blocker => High
Assignee: pkg-bugs => mageiatools