Description of problem:
I had to activate network during build (see https://copr-be.cloud.fedoraproject.org/results/duck/osas-infra-team-rpm-repo/epel-7-x86_64/00581806-postsrsd/builder-live.log). I can activate this permanently and I'll have my packages built, but I think from a security point of view this is not a bright idea. My packages do not need network during the build phase, so I think the SRPM preparation should be decorrelated. At the very least it should at least be documented because this is a change from previous behavior (where the source could be downloaded without this option).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. prepare a package SPEC using a source as URL in git
2. configure you package with SCM 2 method and your previously created repo
3. build without network access

Actual results:
Build fails because the source firl could not be downloaded:
---------------------------------------------
Start: buildsrpm
Start: rpmbuild -bs
warning: Downloading https://github.com/roehling/postsrsd/archive/a77bf9940c19aca602faa41bbf987e43e51a5305.tar.gz#/postsrsd-a77bf9940c19aca602faa41bbf987e43e51a5305.tar.gz to /builddir/build/SOURCES/postsrsd-a77bf9940c19aca602faa41bbf987e43e51a5305.tar.gz
curl: (6) Could not resolve host: github.com; Unknown error
error: Couldn't download https://github.com/roehling/postsrsd/archive/a77bf9940c19aca602faa41bbf987e43e51a5305.tar.gz#/postsrsd-a77bf9940c19aca602faa41bbf987e43e51a5305.tar.gz
---------------------------------------------

Expected results:
Better would be to create the SRPM _with_ network always, and use the current " Enable internet access during this build" only for the real build phase.

Additional info:
The new SCM 2 build was introduced in ticket #1471066.