<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration, branch 1.5_beta1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.5_beta1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.5_beta1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2017-07-01T19:46:22Z</updated>
<entry>
<title>Ignore download order in test-apt-update-failure-propagation</title>
<updated>2017-07-01T19:46:22Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-07-01T19:45:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c72cc1c1ce2251a7809233d6791141bc777cb899'/>
<id>urn:sha1:c72cc1c1ce2251a7809233d6791141bc777cb899</id>
<content type='text'>
This caused spurious test failures.
</content>
</entry>
<entry>
<title>Switch to 'http' as the default https method</title>
<updated>2017-06-30T14:33:09Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-30T14:33:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c6a428e4d17b408c2701def5daa46ca950948980'/>
<id>urn:sha1:c6a428e4d17b408c2701def5daa46ca950948980</id>
<content type='text'>
The old curl based method is still available as 'curl',
'curl+http', and 'curl+https'.
</content>
</entry>
<entry>
<title>Reset failure reason when connection was successful</title>
<updated>2017-06-30T09:05:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-30T09:02:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d3a70c3e5ae68a0e5a3d4667dd1d0fc0887e6263'/>
<id>urn:sha1:d3a70c3e5ae68a0e5a3d4667dd1d0fc0887e6263</id>
<content type='text'>
When APT was trying multiple addresses, any later error
somewhere else would be reported with ConnectionRefused
or ConnectionTimedOut as the FailReason because that
was set by early connect attempts. This causes APT to
handle the failures differently, leading to some weirdly
breaking test cases (like the changed one).

Add debugging to the previously failing test case so
we can find out when something goes wrong there again.
</content>
</entry>
<entry>
<title>support tor+https being handled by http</title>
<updated>2017-06-28T20:26:56Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-06-28T20:20:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=579f8f1008eceecd3da9ac53923c6a8d08244cb7'/>
<id>urn:sha1:579f8f1008eceecd3da9ac53923c6a8d08244cb7</id>
<content type='text'>
The apt-transport-tor package operates via simple symlinks which can
result in 'http' being called as 'tor+https', so it must pick up the
right configuration pieces and trigger https support also in plus names.
</content>
</entry>
<entry>
<title>Strip 0: epochs from the version hash</title>
<updated>2017-06-28T17:50:26Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-26T16:44:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6edfda8b45dee7e1202f723b98fa962c38554c51'/>
<id>urn:sha1:6edfda8b45dee7e1202f723b98fa962c38554c51</id>
<content type='text'>
This should fix some issues with dpkg normalizing such
values. Suprisingly enough apt treats the Version: field
the same, even with epoch vs without, but not when searching,
and does not strip the 0: from the output.
</content>
</entry>
<entry>
<title>show a Release-Notes URI if infos were changed</title>
<updated>2017-06-28T17:18:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-05-28T11:24:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=96ebab48c25fcd1ee83729cdba4be8a6343a8766'/>
<id>urn:sha1:96ebab48c25fcd1ee83729cdba4be8a6343a8766</id>
<content type='text'>
This gives the repository owner a chance to explain why this change was
needed – e.g. explaining the organisational changes or simply detailing
the changes in the new release made. Note that this URI is also shown
if the change is accepted, so it also draws attention to release notes
of minor updates (if users watch apt output closely).
</content>
</entry>
<entry>
<title>error in update on Release information changes</title>
<updated>2017-06-28T17:18:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-04-12T15:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=081fbea14d12f79c8d91ce4fe1f1004c7bc08656'/>
<id>urn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656</id>
<content type='text'>
The value of Origin, Label, Codename and co can be used in user
configuration from apts own pinning to unattended upgrades.
A repository changing this values can therefore have serious effects on
the behaviour of apt and other tools using these values.

In a first step we will generate error messages for these changes now
explaining the need for explicit confirmation and provide config options
and commandline flags to accept them.
</content>
</entry>
<entry>
<title>fail instead of warn on insecure repositories in apt-get</title>
<updated>2017-06-28T17:17:57Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-06-28T10:57:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cbaf353ead58aa9eefe51542b6ad91e69b6289ce'/>
<id>urn:sha1:cbaf353ead58aa9eefe51542b6ad91e69b6289ce</id>
<content type='text'>
The exception was made to give (script) users a one-release grace period
to adapt their setup to deal with apt enforcing signing of repositories.
As we are now at the start of a new release cycle its as good a time as
any to lift it now.

Removes-Exception: 952ee63b0af14a534c0aca00c11d1a99be6b22b2
</content>
</entry>
<entry>
<title>Merge branch 'feature/http-https'</title>
<updated>2017-06-28T17:15:41Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T17:15:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=11c3624ce3575076ca52350f66d4bd2e63db5d73'/>
<id>urn:sha1:11c3624ce3575076ca52350f66d4bd2e63db5d73</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Skip test-apt-download-progress</title>
<updated>2017-06-28T16:11:53Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T16:11:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=930e2df52dc637039c1845905d79ce525faeb8ca'/>
<id>urn:sha1:930e2df52dc637039c1845905d79ce525faeb8ca</id>
<content type='text'>
The test keeps failing continously on Ubuntu, so let's
fix it for now.
</content>
</entry>
</feed>
