apt/test, branch 1.5_alpha1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.5_alpha12017-06-28T17:50:26ZStrip 0: epochs from the version hash2017-06-28T17:50:26ZJulian Andres Klodejak@debian.org2017-06-26T16:44:56Zurn:sha1:6edfda8b45dee7e1202f723b98fa962c38554c51
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.
show a Release-Notes URI if infos were changed2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-28T11:24:33Zurn:sha1:96ebab48c25fcd1ee83729cdba4be8a6343a8766
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).
error in update on Release information changes2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-04-12T15:39:06Zurn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656
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.
fail instead of warn on insecure repositories in apt-get2017-06-28T17:17:57ZDavid Kalnischkiesdavid@kalnischkies.de2017-06-28T10:57:51Zurn:sha1:cbaf353ead58aa9eefe51542b6ad91e69b6289ce
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
Merge branch 'feature/http-https'2017-06-28T17:15:41ZJulian Andres Klodejak@debian.org2017-06-28T17:15:41Zurn:sha1:11c3624ce3575076ca52350f66d4bd2e63db5d73Skip test-apt-download-progress2017-06-28T16:11:53ZJulian Andres Klodejak@debian.org2017-06-28T16:11:53Zurn:sha1:930e2df52dc637039c1845905d79ce525faeb8ca
The test keeps failing continously on Ubuntu, so let's
fix it for now.
Fix test suite and enable non-curl testing on travis, shippable2017-06-28T14:13:47ZJulian Andres Klodejak@debian.org2017-06-28T13:29:13Zurn:sha1:c81b83864b7da79250a210ea7c49b5b03a4b2b16
Gbp-Dch: ignore
Fix https->http redirect issues2017-06-28T13:52:38ZDavid Kalnischkiesdavid@kalnischkies.de2017-06-28T13:52:00Zurn:sha1:29a08d8ab0c4d82f26c2712c456508784040cdbb
Gbp-Dch: ignore
travis: ignore profiling warning in progress lines2017-06-27T15:46:29ZDavid Kalnischkiesdavid@kalnischkies.de2017-06-27T13:54:10Zurn:sha1:fc251c8c9e2a76ab5c350900e9e032830c81e2b3
On Travis CI running tests with code coverage enabled sometimes
generates profiling lines, which we filter out for a while now,
but that misses lines generated showing progress still causing test
failures, so more sed logic is added in the hopes to ignore them.
Extends: 58608941e6b58a46109b7cd875716b3d8054c4bf
Gbp-Dch: Ignore
deal with 3xx httpcodes as required by HTTP/1.1 spec2017-06-26T21:31:15ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-29T11:28:01Zurn:sha1:42654d08c2ca1bee18b6947a39228a35c2409deb
An unknown code should be handled the same as the x00 code of this
group, but for redirections we used to treat 300 (and a few others)
as an error while unknown codes were considered redirections.
Instead we check now explicitly for the redirection codes we support for
redirecting (and add the 308 defined in RFC 7538) to avoid future
problems if new 3xx codes are added expecting certain behaviours.
Potentially strange would have been e.g. "305 Use Proxy" sending a
Location for the proxy to use – which wouldn't have worked and resulted
in an error anyhow, but probably confused users in the process.