1 disable fetching sources.
2 annoying if you just want to get .spec structure!
4 it could be parameter to s.parseSpec(), but as prevous code hardcoded, i'll
5 just "hardcode" different value here.
7 http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2015-November/024529.html
9 one could play with '__urlgetfile' macro, and just tell it 'OK':
12 but then ugly "Fetching" messages are still displayed, which maybe even more confusing.
14 http://comments.gmane.org/gmane.comp.package-management.rpm.user/159
16 --- rpm-5.4.15/python/rpmts-py.c~ 2014-07-28 00:52:21.000000000 +0300
17 +++ rpm-5.4.15/python/rpmts-py.c 2015-11-04 22:00:33.989058412 +0200
18 @@ -1333,13 +1333,15 @@
19 char * passPhrase = "";
25 char * kwlist[] = {"specfile", NULL};
27 if (!PyArg_ParseTupleAndKeywords(args, kwds, "s:Parse", kwlist, &specfile))
30 + verify = rpmExpandNumeric("%{?_py_parsespec_verify}%{?!_py_parsespec_verify:0}");
32 if (parseSpec(s->ts, specfile,"/", recursing, passPhrase,
33 cookie, anyarch, force, verify)!=0) {
34 PyErr_SetString(pyrpmError, "can't parse specfile\n");