April 2010 - Arch-releng - lists.archlinux.org

[arch-releng] 2010.04.05 snapshots ready for testing
by Dieter Plaetinck 12 Apr '10

12 Apr '10

Hello all, please find new testing images @ http://build.archlinux.org/isos/ This time, there are no big known issues! [1] I just did an installation myself and it worked, but of course images require a lot more testing, especially for the exotic things (lvm, encryption, automatic installs, all new features such as pxe booting, etc). So please give these images a spin. They can't be much worse then the last official release ;-) If you tested the image and it worked fine, be sure to let us know and briefly describe which special thingies (if any) worked fine for you. http://build.archlinux.org/isos/Changelog http://build.archlinux.org/isos/README The more feedback I get from the community, the faster a new official release will happen. Dieter [1] (I did not figure out the issue i had earlier - http://mailman.archlinux.org/pipermail/arch-releng/2010-April/000941.html, but I re-setup the build chroots and now it's magically fixed.

8 19

Re: [arch-releng] 2010.04.05 snapshots ready for testing
by Dieter Plaetinck 10 Apr '10

10 Apr '10

On Sat, 10 Apr 2010 13:27:17 -0500 Chris Brannon <cmbrannon79(a)gmail.com> wrote: > > well, crap. if the problem occurs only when not doing logging, then > > this is going to be a bitch to investigate. (did you try just just > > '-l' or just '-d' instead of '-l -d' ?) > > It also fails with -l (no -d), though the log file isn't too helpful. > It always succeeds with -d, regardless of whether -l is present. you could run aif -p interactive -l and change relevant debug calls (eg those in process_filesystem) to log calls. > I wonder whether die_error is actually dying when debugging is > enabled? it definitely should. why do you doubt this? (you see that aif exists, after spawning the error, right?). you see. try -l then > > AFAIK, here is the line in the AIF code that is failing: > [ "$2" != lvm-lv ] && [ -z "$1" -o ! -b "$1" ] && die_error > "process_filesystem needs a partition as \$1" # Don't do this for > lv's. It's a hack to workaround non-existence of VG device files. > It's line 692 of src/core/libs/lib-blockdevices-filesystems.sh in my > (up-to-date) clone. > > The -b $1 caught my attention. Is it possible that this is failing? > My /dev/mapper/cryptoroot is a symlink to another device > (/dev/dm-0, IIRC), and that is a block device. the fact that it's a symlink, is by itself not a problem: example: $ ls -alh /dev/mapper/cryptpool-home lrwxrwxrwx 1 root root 7 Apr 10 08:28 /dev/mapper/cryptpool-home -> ../dm-3 $ [ -b /dev/mapper/cryptpool-home ] $ echo $? 0 we first of all must be sure that $1 is what we expect. so put a log call as the very fist thing in process_filesystem that logs "$@" > I wonder if that block device somehow didn't become available > soon enough for process_filesystems /dev/mapper/cryptoroot ext4 to use > it? I'm running this in a VM after all. it should. process_filesystems is designed to do them in correct order (this is why it's very useful to change the debug calls to log calls, then you can follow which devices it does) each process_filesystem call is definitely synchronous btw. ie. the function runs as long as the mkfs/cryptsetup/.. is running. once cryptsetup > > PS. I'm mainly testing this because you said that you'd like for > folks to test the exotic features. thank you. this is definitely needed.

1 0

[arch-releng] 2010.04.04, i686 images have x86_64 kernel
by Dieter Plaetinck 05 Apr '10

05 Apr '10

So, i built new images. http://build.archlinux.org/isos/ they "should" work. built from the latest archiso, using the latest configs however when i try to boot the i686 image, just after the isolinux menu, i get this: "this kernel requires an x86_64 cpu, but only detected an i686 cpu. Unable to boot - please use a kernel appropriate for your cpu." any of the archiso hackers know how this can happen? the makefile does just a `uname -m` and obviously i was in the i686 chroot (and it named the isos i686.iso, so the detection should work) and: cat root-image/etc/mkinitcpio.d/kernel26.kver # DO NOT EDIT THIS FILE ALL_kver='2.6.32-ARCH' Dieter

4 4

Re: [arch-releng] [arch-general] Arch Linux Release Question
by Dieter Plaetinck 04 Apr '10

04 Apr '10

"release team" currently that means me. yes, i'm working on new images. see: http://build.archlinux.org/isos/ http://mailman.archlinux.org/pipermail/arch-releng/2010-March/thread.html progress is rather slow, but there is not so much work anymore, so they'll come.. Dieter

2 1

[arch-releng] Arch Linux Release Question
by Keith Hinton 03 Apr '10

03 Apr '10

Hi, First of all, if anyone is curious as to why I have posted to the Arch-General mailing list, I'm mainly doing this, in case any of the Arch Release team is actually hanging out on this list. I was curious, seeing as the last Arch Linux release was in August of last year, if there will be one for the lovely new year of 2010? If someone could get back to me on that question I would for sure appreciate it. I hope that all is going well for Arch Linux development! Talk to you folks later. I haven't been as active on this list due to personal commitments but do watch for any interesting activity from time-to-time. Thanks. Sincere Regards, --Keith

1 0