[arch-releng] automated iso builds

[Dieter Plaetinck]

On Wed, 10 Feb 2010 18:56:58 -0300
Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote:

> > On Wed, 10 Feb 2010 17:29:15 -0300
> > Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar>  wrote:
> >> Done: http://bugs.archlinux.org/task/18277
> >>
> >>      
> > any ETA on a new squashfs release? maybe we should give them some
> > time instead of patching ourself. although it looks like they don't
> > release very often and this patch is a few months old.
> >
> >    
> What is ETA? The patch does not look bad and solves the issue. Seems 
> that release of squashfs-tools are a bit slow:
> 4.0 2009/04
> 3.4 2008/08
> 3.0 2006/03
> 
> More info about bug report here: 
> http://sourceforge.net/mailarchive/message.php?msg_name=87k529zp8f.fsf%40macbook.be.48ers.dk

allright. fine by me then. hope Tpowa accepts it :)
(eta = estimated time of arrival)

> I guessed that you have enabled [testing] at all (on your enviroment
> and on iso) in reference to this:
> 
> On 02/09/2010 06:28 PM, Dieter Plaetinck wrote:
>  > i built this experimental isolinux image (with testing repo
>  > enabled!),
> 
> Latest git of archiso requires "mkinitcpio-0.6" from testing (by
> error, Aaron merge my "experimental" branch instead of "djgera") [#1]
> otherwise you need to reset to commit a2f6841c so can build against 
> current [core].

I meant that the iso is built from testing+core packages.  The
environment (build-chroot) is core only.
Frankly I'm not sure if there's much point in doing this.  Maybe it's
better to only use core for both the chroot and the actual iso's

Dieter