cf. bug 1183886
I wish to NET install a system to be used with systemd-networkd. In TW20240607
detailed package selection I managed to taboo wicked-service, wicked and
networkmanager before selecting network on summary screen to disable network
"services" (use neither wicked nor NM). In network, settings from cmdline were
maintained, so I was able to proceed with installation, or so it lead me to
believe. Apparently, network had been broken by the particular sequence of
events, including clicking back button multiple times to redo network or
detailed package selection, so fetch attempts all produced 404s, retries always
produced 404, leaving only one other option - abort. I clicked abort before
recovering exact language on software screen's network setup, upon which the
installer exited and halted the system without rebooting. Thus, capturing logs
was impossible. 

I started afresh, this time, with TW20240610, selecting to disable network
before doing anything else at first visit to summary screen, and not bothering
in detailed package selection to taboo already deselected NM and Wicked. This
succeeded to a full installation. y2logs saved from first boot are available on
request.

The NET installer ought to be able to proceed using valid network settings from
cmdline even after multiple trips between detailed package selection and
network.