apt/test/integration/test-apt-update-releaseinfo-changes, branch 2.9.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.12020-08-10T13:39:33ZDefault Acquire::AllowReleaseInfoChange::Suite to "true"2020-08-10T13:39:33ZJulian Andres Klodejulian.klode@canonical.com2020-08-10T13:39:33Zurn:sha1:64b45e294f0c6931a9b57ae6cc99ecded8f6a2d3
Closes: #931566
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.