On Tue, 03 May 2011 20:51:59 -0300 Gerardo Exequiel Pozzi <[email protected]> wrote:
> On 04/14/2011 11:02 PM, Gerardo Exequiel Pozzi wrote: > > On 04/14/2011 10:57 PM, Gerardo Exequiel Pozzi wrote: > >> Needs mkinitcpio>= 0.6.9-1 (otherwise does not work with passed > >> options to xz). > >> > >> Signed-off-by: Gerardo Exequiel Pozzi<[email protected]> > >> --- > >> configs/syslinux-iso/mkinitcpio.conf | 2 +- > >> 1 files changed, 1 insertions(+), 1 deletions(-) > >> > >> diff --git a/configs/syslinux-iso/mkinitcpio.conf > >> b/configs/syslinux-iso/mkinitcpio.conf > >> index f5f8c79..aea436d 100644 > >> --- a/configs/syslinux-iso/mkinitcpio.conf > >> +++ b/configs/syslinux-iso/mkinitcpio.conf > >> @@ -3,4 +3,4 @@ MODULES="" > >> BINARIES="" > >> FILES="" > >> HOOKS="base udev memdisk archiso archiso_pxe_nbd > >> archiso_loop_mnt pata scsi sata usb fw pcmcia filesystems usbinput" > >> -COMPRESSION="lzma" > >> +COMPRESSION="xz" > > I will push it this to master when mkinitcpio 0.6.10-1 (now in > > [testing] hits [core]) if there are no objections. > > > pushed to master. > > build enviroment should be update. I thinks that this is done > automatically now, right? > yes, before every image build, the latest archiso gets installed from git (master branch) (aif package also gets rebuilt, from the develop git branch) Dieter
