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

[Antonio Terceiro]

On Mon, Apr 25, 2016 at 07:11:55PM +0100, Neil Williams wrote:
> On Mon, 25 Apr 2016 12:35:29 -0300
> Antonio Terceiro <terceiro at debian.org> wrote:
> 
> > 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:
> > > 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)
> 
> OK, I'll make it so that explicit ext4 on wheezy gives an error and
> output a message that ext3 is being used on wheezy if roottype not
> specified.

cool, thanks.

> I can't guarantee that generic recipes for all current suites will
> always exist though, especially unstable and after point releases. (I'm
> hoping that lava.debian.net will help with point release testing.)

I guess at some point we might need to keep a set of sane defaults for
each supported distribution ... so that `vmdebootstrap --distribution
$foo` always works regardless of the value of $foo(?)
-------------- 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/6d7f91e7/attachment-0001.sig>