Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-13 Thread Torsten Landschoff
Hi Ferenc, On Wed, May 11, 2005 at 11:26:44AM +0200, Ferenc Engard wrote: I suggest that the frontend should explicitly indicate if it cannot handle default values, although the there is one, e.g. like this: Default value: /var/backups/slapd-VERSION *** WARNING! You have to type the

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-13 Thread Joey Hess
Torsten Landschoff wrote: a) It does neither present the default nor the current value. b) It is /not/ clear that hitting enter means the empty value. With alone this information (the above one line) that's what I would have expected. But I was used to debconf using the default value when

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-11 Thread Ferenc Engard
Hi all, The technical details of why debconf is not able to present a default value with the readline frontend, when the recommended literm-readline-gnu-perl is not installed, or with the teletype frontend, are already explained in bug #183970. I know of no better Just a silly question: why

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-11 Thread Ferenc Engard
Hi, If you really think we should not mention the default value there that's okay but on the other side I request that the behaviour of the readline frontend is changed to at least present the user the current/default value if the libterm-readline-gnu-perl package is not installed. And make

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-10 Thread Christian Perrier
The bug is in slapd for including this text in its debconf template: The default is /var/backups/slapd-VERSION This comes under the heading of not referring to debconf UI in a template. Just as you don't know how debconf will choose to present a yes/no question and thus say yes

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-10 Thread Torsten Landschoff
Hi Joey, On Mon, May 09, 2005 at 09:11:50PM -0400, Joey Hess wrote: I really think this is a bug that needs to be dealt with from the debconf side of things. Torsten, if you want to add a workaround to slapd, that should be ok, but the real bug appears to be that the readline frontend is

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-10 Thread Steve Langasek
On Mon, May 09, 2005 at 09:11:50PM -0400, Joey Hess wrote: I really think this is a bug that needs to be dealt with from the debconf side of things. Torsten, if you want to add a workaround to slapd, that should be ok, but the real bug appears to be that the readline frontend is somehow

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-10 Thread Joey Hess
Torsten Landschoff wrote: The bug is in slapd for including this text in its debconf template: The default is /var/backups/slapd-VERSION How is that a bug? In fact this can be helpful in case you changed the value and later wonder what is was originally. Apart from that it is an

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-09 Thread Torsten Landschoff
Hi Ferenc, On Mon, May 09, 2005 at 12:21:32AM +0200, Ferenc Engard wrote: While I have upgraded my system, slapd upgrade asked some questions, including directory to dump databases. The text said the default is /var/backups/slapd-VERSION. Reading that, I simply pushed enter. After that,

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-09 Thread Ferenc Engard
Hi Torsten, On Mon, 9 May 2005, Torsten Landschoff wrote: including directory to dump databases. The text said the default is /var/backups/slapd-VERSION. Reading that, I simply pushed enter. After that, the preinst script have failed, rendering slapd unconfigured. Meanwhile, apt has upgraded

Processed: Re: Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-09 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 308234 debconf Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir Bug reassigned from package `slapd' to `debconf'. thanks Stopping processing here. Please contact me if you need assistance. Debian

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-09 Thread Steve Langasek
reassign 308234 debconf thanks Hi guys, On Mon, May 09, 2005 at 08:20:23AM +0200, Torsten Landschoff wrote: On Mon, May 09, 2005 at 12:21:32AM +0200, Ferenc Engard wrote: While I have upgraded my system, slapd upgrade asked some questions, including directory to dump databases. The text

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-09 Thread Joey Hess
Steve Langasek wrote: reassign 308234 debconf thanks Hi guys, On Mon, May 09, 2005 at 08:20:23AM +0200, Torsten Landschoff wrote: On Mon, May 09, 2005 at 12:21:32AM +0200, Ferenc Engard wrote: While I have upgraded my system, slapd upgrade asked some questions, including

Bug#308234: upgrading from 2.1.23 failed because of not setting slapd/dump_database_destdir

2005-05-08 Thread Ferenc Engard
Package: slapd Version: 2.2.23-5 Severity: grave Justification: renders package unusable While I have upgraded my system, slapd upgrade asked some questions, including directory to dump databases. The text said the default is /var/backups/slapd-VERSION. Reading that, I simply pushed enter.