Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

2018-01-25 Thread Ryan Tandy
On Thu, Jan 25, 2018 at 06:05:44PM +0100, Floris Bos wrote: If you can guarantee us that the name of the folder we would need to delete is always /var/backups/unknown-2.4.44+dfsg-5+deb9u1.ldapdb -even in future package updates- that is a possibility. However would prefer not to make

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

2018-01-25 Thread Ryan Tandy
On Thu, Jan 25, 2018 at 06:47:22PM +0100, Floris Bos wrote: That's pretty confusing as well. Yeah :/ You are right, in this case it only seems to have copied configuration to dump_database_destdir While the documentation suggests that directory is meant to dump the whole database to on

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

2018-01-25 Thread Floris Bos
On 01/25/2018 05:54 PM, Ryan Tandy wrote: Nor an option to simply not move the thing, but delete it. We already have a dump of it, right? Not sure. We have a dump of the config, but I don't think it dumps the data, does it? That's pretty confusing as well. You are right, in this case it

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

2018-01-25 Thread Floris Bos
Hi, On 01/25/2018 05:54 PM, Ryan Tandy wrote: On Thu, Jan 25, 2018 at 05:05:27PM +0100, Floris Bos wrote: I am not seeing any easy option to prevent this from happening. Removing the existing backup first isn't easy enough? If you can guarantee us that the name of the folder we would need

Bug#888440: [Pkg-openldap-devel] Bug#888440: "dpkg-reconfigure slapd" fails if backup directory already exists

2018-01-25 Thread Ryan Tandy
Control: forcemerge 757550 -1 Hello Floris, Thank you for the report. I'm merging it with an existing ticket that tracks the same issue. On Thu, Jan 25, 2018 at 05:05:27PM +0100, Floris Bos wrote: I am not seeing any easy option to prevent this from happening. Removing the existing backup