summaryrefslogtreecommitdiff
path: root/test/integration/test-bug-675449-essential-are-protected
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2015-07-09 21:10:53 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2015-08-10 17:27:17 +0200
commit0d5b9da9f597fecae9b912d37d4e58bc903bdd4f (patch)
tree091475cd19cb6530e6f7ec2a941fd6e69d3ca3e1 /test/integration/test-bug-675449-essential-are-protected
parenta4b8112b19763cbd2c12b81d55bc7d43a591d610 (diff)
disable locking even for root in --simulate
Six years ago in 55a5a46c235a30bf024fb2301066553953701cc5 apt-get learned to disable locking if run as normal user and show a message. Helmut Grohne rightly suggests on IRC now that there isn't much point in getting the locks for root either as the output isn't in any way more authoritive than without locking given that after this call the lock is freed and any action can sneak in before we make the next call. So we exchange no benefit for the disavantage of blocking real calls. This can be especially confusing with the aliases --no-act and --just-print. We do not print the message we print for users through as the non-root users can be confronted with a lot more difference via unreadable files.
Diffstat (limited to 'test/integration/test-bug-675449-essential-are-protected')
0 files changed, 0 insertions, 0 deletions