Bug#931402: could not leave editor on examining a config file conflict

2022-10-13 Thread Guillem Jover
Control: reassign -1 apt [ Adding some context. ] On Thu, 2019-07-04 at 10:05:31 +0200, Harald Dunkel wrote: > Package: dpkg > Version: 1.18.25 > On the upgrade from Stretch to Buster there was a config > file conflict (with /etc/issue, but that doesn't matter). > dpkg allowed me to examine the

Bug#931402: could not leave editor on examining a config file conflict

2021-05-30 Thread Thorsten Glaser
Package: dpkg Version: 1.19.7 Followup-For: Bug #931402 Control: severity -1 important Control: retitle -1 dpkg: improperly sets up conffile examine shell session; breaks Emacs totally I just noticed the same, ^C gets eaten; thankfully, my editor can do without, but this is probably severe for

Bug#931402: could not leave editor on examining a config file conflict

2021-02-28 Thread Norman Rasmussen
Package: dpkg Version: 1.20.7.1 Followup-For: Bug #931402 I can reproduce this in just the shell that's started. Ctrl-C doesn't seem to have any immediate effect. However once the shell is exited, the Ctrl-C causes dpkg to terminate early. I suspect that dpkg isn't creating a new foreground

Bug#931402: could not leave editor on examining a config file conflict

2019-07-04 Thread Harald Dunkel
Package: dpkg Version: 1.18.25 On the upgrade from Stretch to Buster there was a config file conflict (with /etc/issue, but that doesn't matter). dpkg allowed me to examine the conflict ("Z"). I could adjust the old file using the mg editor, I could save the config file using Ctrl-X Ctrl-S, but