New submission from Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>:
gpgconf currently creates a backup file each time a conf file is changed.
Of course, this is superfluous, although it is convenient while debugging and
testing.
Eventually, the superfluous backup files should be removed. However, it is not
clear if it is good enough to keep only the last backup file, or several.
----------
messages: 747
nosy: marcus
priority: minor bug
status: deferred
title: gpgconf should not keep too many backup files
topic: gpg
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue158>
______________________________________________________
gpgconf currently creates a backup file each time a conf file is changed.
Of course, this is superfluous, although it is convenient while debugging and
testing.
Eventually, the superfluous backup files should be removed. However, it is not
clear if it is good enough to keep only the last backup file, or several.
----------
messages: 747
nosy: marcus
priority: minor bug
status: deferred
title: gpgconf should not keep too many backup files
topic: gpg
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue158>
______________________________________________________