[Vmdebootstrap-devel] Bug#822452: Bug#822452: Bug#822452: vmdebootstrap: can't produce a working wheezy image

[Antonio Terceiro]

On Mon, Apr 25, 2016 at 03:43:48PM +0100, Neil Williams wrote:
> On Mon, 25 Apr 2016 10:56:07 -0300
> Antonio Terceiro <terceiro at debian.org> wrote:
> 
> > On Sun, Apr 24, 2016 at 07:27:41PM +0100, Neil Williams wrote:
> > > On Sun, 24 Apr 2016 13:49:35 -0300
> > > Antonio Terceiro <terceiro at debian.org> wrote:
> > > > $ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap
> > > > --enable-dhcp --image test-grub.img --serial-console
> > > > --distribution wheezy --verbose --log test-grub.log && echo
> > > > booting image && kvm -snapshot -nographic test-grub.img Creating
> > > > disk image Creating partitions Installing MBR Creating filesystem
> > > > ext4  
> > > 
> > > Can you test with --roottype ext2 ? ext3 works for me too.  
> > 
> > yes, it works with --roottype ext3
> > > 
> > > All of the wheezy test images I've used were using ext2 and it may
> > > be that a change in the default has resulted in syslinux not coping
> > > in wheezy.
> > > 
> > > I can update the docs and the default for wheezy.  
> 
> OK, I'll update the docs, add a yarn test and a check on the options
> that ext4 isn't going to work if wheezy is specified. (i.e. --roottype
> becomes required if distribution is mapped to wheezy using
> distro_info and the roottype must not be ext4.)

please make ext3 the default for wheezy instead of requiring an explicit
--roottype. otherwise one cannot have generic build recipes using
vmdebootstrap that take the target distribution as a parameter (case in
point: I'm building vagrant-libvirt images using vmdebootstrap)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/vmdebootstrap-devel/attachments/20160425/5e27a01a/attachment-0003.sig>