| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Default Acquire::AllowReleaseInfoChange::Suite to "true" | Julian Andres Klode | 2020-08-10 | 1 | -0/+14 |
| | | | | | Closes: #931566 | ||||
| * | show a Release-Notes URI if infos were changed | David Kalnischkies | 2017-06-28 | 1 | -2/+5 |
| | | | | | | | | | 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 changes | David Kalnischkies | 2017-06-28 | 1 | -0/+77 |
| 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. | |||||
 |
index : apt | |
| Debians commandline package manager |
| summaryrefslogtreecommitdiff |