apt, branch 1.5_alpha1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.5_alpha12017-06-28T17:53:45ZUpload 1.5~alpha1 to experimental2017-06-28T17:53:45ZJulian Andres Klodejak@debian.org2017-06-28T17:53:45Zurn:sha1:c9390165718d4cf0ec43a0af01f06d6628717905Strip 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.
Merge branch 'feature/releaseinfochange'2017-06-28T17:20:09ZDavid Kalnischkiesdavid@kalnischkies.de2017-06-28T17:20:09Zurn:sha1:dfe0e754a808aabd55f9cd68201a7f1432070836ask for releaseinfo change interactively in apt2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-28T15:44:11Zurn:sha1:24b5bc4e41ed527799a9fa01dec9c29294d0a3f2
If we have a user sitting around we can let 'apt' ask the user for a
confirmation rather than print errors at the end and require the user to
figure out which commandline flags are needed to confirm the changes
non-interactively.
allow frontends to override releaseinfo change behaviour2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-28T14:55:45Zurn:sha1:ca8da1bf83ecc90ba882520b79c1cda03ee7485d
Having messages being printed on the error stack and confirm them by
commandline flags is an okayish first step, but some frontends will
probably want to have a more interactive feeling here with a proper
question the user can just press yes/no for as for some frontends a
commandline flag makes no sense…
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.