Re: stop dhcp configuration and several issues

2007-08-13 Thread Deephay
On 8/12/07, Justin Pryzby [EMAIL PROTECTED] wrote: On Sun, Aug 12, 2007 at 11:28:11PM +0800, Deephay wrote: Greetings, I also experienced a serious issue: during the stage of lh_binary, the helper will try to find /usr/share/live-helper/casper/casper/parameters.txt but the file does

Re: stop dhcp configuration and several issues

2007-08-13 Thread Daniel Baumann
Deephay wrote: but if I want to build an etch LiveCD, it will still retrive casper automatically during lh_chroot. ...unless you set LH_INITRAMFS manually to live-initramfs in config/common and include /usr/share/live-helper/examples/sources/live-backports -- Address:Daniel Baumann,

Re: Re: no binary.iso

2007-08-13 Thread Jean-Louis Louër
On Sun, Aug 12, 2007 at 08:52:09AM +0200, Daniel Baumann wrote: Jean-Louis Louër wrote: I would like to make an image with Debian-live. The version of live-helper is 1.0~a20~2596. first of all, you're using an outdated svn snapshot. please upgrade to 1.0~a21-1 (from sid/lenny). I get

Re: stop dhcp configuration and several issues

2007-08-13 Thread Juergen Fiedler
On Mon, Aug 13, 2007 at 11:03:29PM +0800, Deephay wrote: [...] thanks very much for the help, can I change the default hostname also? [...] If I understand your question correctly, LH_HOSTNAME (typically set in config/binary) should do that. Hope that helps -Juergen signature.asc

Re: stop dhcp configuration and several issues

2007-08-13 Thread Deephay
On 8/13/07, Daniel Baumann [EMAIL PROTECTED] wrote: Deephay wrote: but if I want to build an etch LiveCD, it will still retrive casper automatically during lh_chroot. ...unless you set LH_INITRAMFS manually to live-initramfs in config/common and include

Bug#436731: marked as done (lh_binary_yaboot fails with: sed: -e expression #1, char 13: unterminated `s' command)

2007-08-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Aug 2007 17:30:26 +0200 with message-id [EMAIL PROTECTED] and subject line (no subject) 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 not the case it is now your responsibility to