[Voyage-linux] problem building voyage from scratch

[Punky Tse]

debootstrap is still be used for voyage-base.etch.tar.gz creation, but 
it is used in a very early stage. 

The reason for using voyage-custom is that I would like to decouple 
debootstrap from the custom config files and the trim-down scripts.

With voyage-base created separately, I use voyage-custom scripts to 
customize it.  To create the voyage-current, two customization profiles 
(I call it stage1 and stage2) are used. Hence, theoretically, 
voyage-base could be replaced by ubuntu's edgy and hence edgy-based 
voyage could be created.

Punky.

n schembr wrote:
> What was wrong with the debootstrap method? I just ran debootstrap  on the Ubuntu archive.  It's 198M but looks like it will clean up nicely.  I personly like the idea of debbootstrap + custom config files.   This type of build will help others make Flash based desktop systems and more.
>
> Why the move to Voyage-custom?  Is the base system going to remain Debian? What about Ubuntu as a base? (Flame Shield ON:) )
>
> Nicholas A. Schembri
> State College, PA USA
>
> ----- Original Message ----
> From: Kim-man 'Punky' TSE <punkytse at punknix.com>
> To: Thorsten von Eicken <tve at voneicken.com>
> Cc: voyage-linux at voyage.hk
> Sent: Monday, September 18, 2006 9:17:09 PM
> Subject: Re: [Voyage-linux] problem building voyage from scratch
>
> Hi Thorsten ,
>
> voyage-current no longer be built by debootstrap.  debootstrap.voyage.sh 
> will still stay in CVS repository, but no longer updated.
>
> But you could still build by debootstrap.voyage.sh.  I didn' t run 
> debootstrap.voyage.sh anymore so I don't know the current status.  I 
> recalled that the similar error will occur if you run 
> debootstrap.voyage.sh under etch.
>
> FYI, voyage-current is built by customization framework.  
> (http://wiki.voyage.hk/dokuwiki/doku.php?id=customization)
>
> Punky
>
> Thorsten von Eicken wrote:
>   
>> I'm trying to build voyage from scratch and am having problems in 
>> debootstrap.voyage.sh with the debconf package. What I see (with some 
>> debugging turned on is):
>>
>> Selecting previously deselected package debconf.
>> Unpacking debconf (from .../debconf_1.4.30.13_all.deb) ...
>> dpkg: debconf: dependency problems, but configuring anyway as you 
>> request:
>> debconf depends on debconf-i18n | debconf-english; however:
>>  Package debconf-i18n is not installed.
>>  Package debconf-english is not installed.
>> Setting up debconf (1.4.30.13) ...
>> Preparing to replace debconf 1.4.30.13 (using 
>> .../debconf_1.4.30.13_all.deb) ...
>> Unpacking replacement debconf ...
>> Selecting previously deselected package debconf-i18n.
>> Unpacking debconf-i18n (from .../debconf-i18n_1.4.30.13_all.deb) ...
>> Setting up debconf-i18n (1.4.30.13) ...
>>
>> So it installs debconf-i18n even though that's in the EXCLUDE list. 
>> Then when it gets to debconf-english (which is in the INCLUDE list) I 
>> naturally get:
>>
>> dpkg: regarding .../debconf-english_1.4.30.13_all.deb containing 
>> debconf-english:
>> debconf-english conflicts with debconf-i18n
>>  debconf-i18n (version 1.4.30.13) is installed.
>> dpkg: error processing 
>> var/cache/apt/archives/debconf-english_1.4.30.13_all.deb (--unpack):
>> conflicting packages - not installing debconf-english
>> var/cache/apt/archives/debconf-english_1.4.30.13_all.deb
>>
>> I added debconf to the EXCLUDE, but that doesn't help. Some other 
>> package must be pulling it in... I finally gave up and removed 
>> debconf-english from the INCLUDE list and that worked fine, albeit 
>> with the i18n version...
>>
>> Thorsten
>>
>>
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>     
>
>
>