summaryrefslogtreecommitdiff
path: root/test/integration/test-apt-update-hooks
Commit message (Collapse)AuthorAgeFilesLines
* run update post-invokes even on (partial) failuresDavid Kalnischkies2016-06-221-3/+9
| | | | | | | Unsecure repositories result in error messages by default which causes the acquire run to fail hard, but non-failing repositories are still updated just like in the slightly less hard-failures which got this behaviour in 35664152e47a1d4d712fd52e0f0a2dc8ed359d32.
* update: Run Post-Invoke-Success if not all sources failedJulian Andres Klode2016-05-101-0/+43
Failures can happen and APT regardless will do a partial cache update anyway. Because APT ensures that the list directory is in a sane state, it makes sense to also call success hooks if success was only partial - otherwise it loses sync with APT. Most importantly, this causes the appstream cache to be empty, see launchpad bug #1562733. This is somewhat overly optimistic though: As soon as any repository has nonexisting optional files, the missing optional files are also treated as success, which means a single broken repository without an InRelease file still runs Success hooks, even though it really should not.