Bug#382889: marked as done (debian-installer: non-optimal order of operations)

2007-04-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Apr 2007 16:16:40 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#382889: closed by Christian Perrier <[EMAIL PROTECTED]> (Closing bug as we don't intend to change the order of questions) has caused the attached Bug report to be marked as done. This means

Bug#382889: marked as done (debian-installer: non-optimal order of operations)

2007-04-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Apr 2007 08:14:56 +0200 with message-id <[EMAIL PROTECTED]> and subject line Closing bug as we don't intend to change the order of questions has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#382889: marked as done (debian-installer: non-optimal order of operations)

2006-08-14 Thread Frans Pop
On Monday 14 August 2006 23:30, Joey Hess wrote: > That said, I don't actually see any benefit from running user-setup > before partman, as opposed to before apt-setup. In either case it's > running as part of a block of questions that all happen quite close > together with minimal wait time for th

Bug#382889: marked as done (debian-installer: non-optimal order of operations)

2006-08-14 Thread Joey Hess
> As far as I know there is absolutely no way to have user-setup being > run before partman in the current way the installer is working. Is that actually true anymore? user-setup only touches /target in user-setup-apply; user-setup-ask seems to not need /target at all, and user-setup-udeb doesn't

Bug#382889: marked as done (debian-installer: non-optimal order of operations)

2006-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2006 22:03:27 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#382889: debian-installer: non-optimal order of operations has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is