<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-apt-update-hooks, branch 1.3_exp2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_exp2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_exp2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-05-10T18:14:02Z</updated>
<entry>
<title>update: Run Post-Invoke-Success if not all sources failed</title>
<updated>2016-05-10T18:14:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-10T17:15:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=35664152e47a1d4d712fd52e0f0a2dc8ed359d32'/>
<id>urn:sha1:35664152e47a1d4d712fd52e0f0a2dc8ed359d32</id>
<content type='text'>
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.
</content>
</entry>
</feed>
