summaryrefslogtreecommitdiff
path: root/test/integration/test-prevent-markinstall-multiarch-same-versionscrew
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2017-03-19 15:08:08 +0100
committerDavid Kalnischkies <david@kalnischkies.de>2017-03-19 15:08:08 +0100
commitc89b22c285d6c4a3cb64689ff26e84af4d1477f2 (patch)
tree08b8da2d9c780db750dab8d50889d249b241c757 /test/integration/test-prevent-markinstall-multiarch-same-versionscrew
parent2ce15bdeac6ee93faefd4b42b57f035bef80c567 (diff)
Ignore AutomaticRemove conffile option in upgrade
We are in a dilemma here: The regression of sorts was introduced in 2013 with commit d8a8f9d7f0 allowing pkg modifiers for the upgrade commands. That calls the autoremover as a sideeffect through and with it comes the option to remove the garbage packages in these commands (similar to aptitude). Having the option on the commandline is no problem – people aren't going to request what they don't want (or so I hope), but the documentation explicitly states that this option only effects install/remove and mentions a config knob users might use and expect to not suddenly apply (especially without documentation) to more commands. Just reverting the commit is out of question, completely ignoring the option breaks the workflow of every user who happened to use --autoremove on the commandline for upgrade and expects that to work given that it was accepted and worked in a stable release. Changing the documentation to reflect reality while perhaps the simplest and cleanest option contradicts freeze and is a surprising change we tend to avoid like the plague while just leaving it be confuses all users who end up believing the documentation even if was different in the last 3 years. So what we do is a tricky compromise: The configuration option if read from a file does apply only for install/remove as documented, while if the option is encountered on the commandline it is accepted and applies to the upgrade which should make 99% of the users happy. The rest has to wait for us to figure out for buster how to get that documented and implemented in a saner way. Closes: #855891
Diffstat (limited to 'test/integration/test-prevent-markinstall-multiarch-same-versionscrew')
0 files changed, 0 insertions, 0 deletions