apt/test/integration/test-apt-update-hooks, branch 2.7.10 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.10 2016-06-22T12:05:01Z run update post-invokes even on (partial) failures 2016-06-22T12:05:01Z David Kalnischkies david@kalnischkies.de 2016-06-16T21:13:26Z urn:sha1:57f7fb6511fcc7c55ee7a88475d15385093c048e 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 failed 2016-05-10T18:14:02Z Julian Andres Klode jak@debian.org 2016-05-10T17:15:17Z urn:sha1:35664152e47a1d4d712fd52e0f0a2dc8ed359d32 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.