[10:50] Hello [14:58] nebuchadnezzar: hi - thanks for your reports [14:59] nebuchadnezzar: what revision of ubuntu-cdimage are you on right now for bug 1133321, and exactly what command line are you running? [15:01] I'm using trunk cdimage [15:03] Right, I know, but what revision number? [15:03] and I run: ARCHES=amd64 DIST=lucid CDIMAGE_ROOT=$(pwd) bin/for-project $MY_PROJECT ${CDIMAGE_ROOT}/bin/cron.daily [15:03] sorry: 1038 [15:04] It looks like Config.set_default_arches() do not use environment variables [15:04] Any local modifications? [15:05] Ah, yes, my mistake then [15:05] only in for-project to accept my custom project name [15:05] and some logging in build.py [15:07] It's all been very awkward with the temporary bridging between shell and Python [15:08] sure, I'm following it near in live ;-) [15:08] * cjwatson attempts to write a test case [15:11] My initial attempt at fixing this (by not exporting values from the config file to the environment at all, and relying on anything non-Python that needs them to source etc/config) horribly broke debian-cd [15:12] I think perhaps the answer is to explicitly export the Config to debian-cd in its environment [15:13] I must admit I'm not completely aware of how it works, I have a quite hard time understanding seeds and germinate, I set LOCAL_SEEDS, add a $PROJECT.$DIST/ seed directory, I added a $PROJECT.$DIST/$PROJECT seed file with my custom metapackages, list it in STRUCTURE which include ubuntu.$DIST, the germination is OK, I got my $GERMINATE_OUT/$PROJECT.packages but the $TASK_OUT/MASTER do not include $PROJECT/$DIST/$PROJECT [15:14] It's generally better to add your custom metapackages to an appropriate existing seed instead [15:15] Otherwise you have to modify cdimage.germinate.Germination.list_seeds to look at your additional seeds [15:15] I looked cleaner to me, avoiding conflicts with ubuntu ones [15:15] Or alternatively you can make some appropriate seed (e.g. "ship" or "desktop") inherit from your new seed [15:16] By adding your new seed to the right-hand side of that line in STRUCTURE [15:16] I though TASKPROJECT was use for the task MASTER [15:16] I'd probably be inclined to do the latter [15:17] No, different named seeds have specific purposes [15:17] There's no "ubuntu" seed, for instance ... [15:18] For instance, desktop and the seeds it inherits constitute the packages that should be installed for a default desktop install; ship constitutes extra packages shipped on the image which may be installed conditionally or may just be available for manual installation without having to go to the network; etc. [15:18] What do you think about a configration option to be used in cdimage.germinate.Germination.list_seeds [15:18] The various modes of list-seeds list the seeds that are used for various purposes [15:19] It doesn't sound necessary or desirable in your case; the seeds are intended to be modified [15:29] so, looking at cdimage.germinate.Germination.seed_dists, I create a $PROJECT.$DIST seeds directory, and create a seed file called "required" and list my metapackages in it, an empty seed file "$PROJECT" which depends on "boot required minimal standard" to build my alternate ISO with my packages? [15:36] I really thought of building a seed tree and the roots are the $PROJECT listing some metapackages and depending on other seeds, but it seems that seeds file names are quite static, or maybe the $PROJECT-server is what I need, I'll make some tests [15:49] trying to be clear of what I did: http://paste.ubuntu.com/5567938/ [15:55] You really shouldn't use required for this ... [15:55] That has a specific meaning, roughly the set of packages installed by debootstrap [15:55] I really actively recommend against this idea that you should name your seed after your project. [15:55] It will only confuse you. [15:56] Treat seeds as having functional names, not branding names [15:56] I suspect you ought to just replace the server seed contents with yours; I'd recommend taking a bzr branch of the Ubuntu seeds to make it easier to manage [15:57] no, I just add packages on-top [15:57] I get the impression that your image is more like the Ubuntu server image than the alternate image? [15:59] Well, the guy before me did some things, and we got alternate images, with a boot menu to install all our flavors (hack of $DIST/boot.$ARCH) [16:00] I try to make it more "clean" in the ubuntu way [17:35] nebuchadnezzar: Try r1039 and see if it fixes bug 1133321? [17:35] Sorry for the delay - had to pick up my bike from the repair shop, then had a meeting [18:09] not a problem, I'll try tomorrow [18:10] good evening