]>
Commit | Line | Data |
---|---|---|
d397adc8 ER |
1 | disable fetching sources. |
2 | annoying if you just want to get .spec structure! | |
3 | ||
4 | it could be parameter to s.parseSpec(), but as prevous code hardcoded, i'll | |
5 | just "hardcode" different value here. | |
6 | ||
7 | http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2015-November/024529.html | |
8 | ||
9 | one could play with '__urlgetfile' macro, and just tell it 'OK': | |
10 | %__urlgetfile OK | |
11 | ||
12 | but then ugly "Fetching" messages are still displayed, which maybe even more confusing. | |
13 | ||
14 | http://comments.gmane.org/gmane.comp.package-management.rpm.user/159 | |
15 | ||
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 = ""; | |
20 | char *cookie = NULL; | |
21 | int anyarch = 1; | |
22 | - int verify = 1; | |
23 | + int verify; | |
24 | int force = 1; | |
25 | char * kwlist[] = {"specfile", NULL}; | |
26 | ||
27 | if (!PyArg_ParseTupleAndKeywords(args, kwds, "s:Parse", kwlist, &specfile)) | |
28 | return NULL; | |
29 | ||
30 | + verify = rpmExpandNumeric("%{?_py_parsespec_verify}%{?!_py_parsespec_verify:0}"); | |
31 | + | |
32 | if (parseSpec(s->ts, specfile,"/", recursing, passPhrase, | |
33 | cookie, anyarch, force, verify)!=0) { | |
34 | PyErr_SetString(pyrpmError, "can't parse specfile\n"); |