summaryrefslogtreecommitdiff
path: root/test/integration/test-cve-2013-1051-InRelease-parsing
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2015-06-15 13:36:11 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2015-06-15 23:35:54 +0200
commitff86d7df6a53ff6283de4b9a858c1dad98ed887f (patch)
treea9161396f07dfc4020967f2e51447872584db22f /test/integration/test-cve-2013-1051-InRelease-parsing
parent08ea7806458de0995414eaae852e0a5985875642 (diff)
call URIStart in cdrom and file method
All other methods call it, so they should follow along even if the work they do afterwards is hardly breathtaking and usually results in a URIDone pretty soon, but the acquire system tells the individual item about this via a virtual method call, so even through none of our existing items contains any critical code in these, maybe one day they might. Consistency at least onceā€¦ Which is also why this has a good sideeffect: file: and cdrom: requests appear now in the 'apt-get update' output. Finally - it never made sense to hide them for me. Okay, I guess it made before the new hit behavior, but now that you can actually see the difference in an update it makes sense to see if a file: repository changed or not as well.
Diffstat (limited to 'test/integration/test-cve-2013-1051-InRelease-parsing')
0 files changed, 0 insertions, 0 deletions