[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: emsandbox and packages.conf

On Fri, 07 Aug 2009 15:54:48 +0300
deb <theedge456@free.fr> wrote:

> > I tried this method to build my rootfs:
> > 
> > 1) I edited the file packages.conf to update the following variables:
> >  INCLUDE=locales,openssh-server,screen,udev,wpasupplicant,wireless-tools
> > 
> > # MIRROR overrides the default emsandbox mirror. This repository will
> > # will be set in /etc/apt/sources.list and will also be used by
> > # debootstrap to obtain all packages for the tarball unless
> > # PROXY is also set.
> > # DEFAULT: http://www.emdebian.org/crush/
> > MIRROR=http://www.emdebian.org/grip/
> I replaced MIRROR by PROXY and it was better. But emsandbox complained 
> about one missing package:

You're using Grip instead of Crush - one of the package replacements in
Crush is that debconf (which is perl) is replaced by a shell package
that fills a gap in cdebconf support. This debconf-shell package does
not exist in Grip because Grip has ordinary perl and ordinary debconf,
Grip does not use cdebconf.


No crush packages exist for armel, so you have to build them all and
put them into a repository so that you can set that for emsandbox.

> Building armel chroot on i386 to install armel packages.

Impossible with Crush and therefore not working with emsandbox.

> --include=debconf-shell --verbose --foreign --arch armel unstable 
> /home/fabien/emdebian/pbuilder/build http://www.emdebian.org/grip/ 

Impossible command.

> I: Checking component main on http://www.emdebian.org/grip...
> E: Couldn't find these debs: debconf-shell
> Any hint ?

To use Grip, use multistrap and live with having full sized perl and
full size coreutils.

To use Crush, address all the problems described in the previous
announcement about Crush, build all the packages for armel as none
already exist and create your own mirror of Crush packages.

There is no shortcut here.


Neil Williams

Attachment: pgphNzij9QJcD.pgp
Description: PGP signature

Reply to: