[arch-releng] updates to releng scripts for new dm_snapshot archiso
Gerardo Exequiel Pozzi
vmlinuz386 at yahoo.com.ar
Fri Aug 5 10:20:08 EDT 2011
On 08/05/2011 10:35 AM, Dieter Plaetinck wrote:
> On Thu, 4 Aug 2011 13:37:29 -0700 (PDT)
> Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar> wrote:
>> ----- Mensaje original -----
>>> De: Dieter Plaetinck<dieter at plaetinck.be>
>>> Para: Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar>; Arch Linux
>>> Release Engineering<arch-releng at archlinux.org> CC:
>>> Enviado: jueves, 4 de agosto de 2011 17:24
>>> Asunto: Re: [arch-releng] updates to releng scripts for new
>>> dm_snapshot archiso
>>> On Thu, 4 Aug 2011 13:20:50 -0700 (PDT)
>>> Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar> wrote:
>>>> Do you check free space on all filesystems?
>>> yes, plenty of space (chroots are in /var/releng)
>>> [dieter at alberich releng]$ df -h
>>> Filesystem Size Used Avail Use% Mounted on
>>> udev 10M 104K 9.9M 2% /dev
>>> /dev/mapper/vg-root 6.8G 3.5G 3.0G 55% /
>>> shm 1005M 0 1005M 0% /dev/shm
>>> /dev/sda1 54M 17M 34M 34% /boot
>>> /dev/mapper/vg-home 9.9G 4.1G 5.8G 42% /home
>>> /dev/mapper/vg-releng 30G 22G 8.6G 72% /var/releng
>>> /dev/mapper/vg-srv 25G 21G 4.5G 82% /srv
>> do you check how look (size, md5) libui pkg copied/downloaded
>> compared with the "original" in local repo?
> No, but if I try enough, sometimes it works. (this
> is also why even before the dm-snapshot merge into archiso, the iso
> builds were about every 5-8 days. the crontab is daily but it fails
> often, and only sometimes it works)
> anyway, now I hit a new problem:
> 191420 extents written (373 MB)
> [mkarchiso] INFO: Done! | 374M archlinux-2011.08.05-core-x86_64.iso
> =============== RELENG-REBUILD-IMAGES DUAL ===============
> building dual images for i686
> ERROR: i686 or x86_64 builds does not exist.
> usage build.sh net_iso_single | core_iso_single | all_iso_single |
> clean_single net_iso_dual | core_iso_dual | all_iso_dual |
> ERROR: ./build.sh all_iso_dual FAILED
> the iso's do exist, but they are not in configs/releng/$work/i686/ and
> configs/releng/$work/x86_64/ like this script seems to assume.
> they are in configs/releng/
Nope, build.sh does not require "*.iso" (like archiso2dual) just use
both working directories from single architectures.
In other words, $work_dir/dual/iso is generated with links (hard) from
$worr_dir/i686/iso and $work_dir/x86_64/iso
Ensure that you are executing build.sh in the same directory where these
both directories exists (like with others build.sh commands)
PS: I have a commit in my experimental branch that allows working from
other directory where "configs" reside, but this is another history...
> Note i did not move them, that's just where your script puts them, so
> why doesn't the all_iso_dual collect them from the right location?
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1
More information about the arch-releng