[01:24] <vorlon> rs2009: https://launchpadlibrarian.net/625054761/buildlog_ubuntu_kinetic_amd64_ubuntu-unity_BUILDING.txt.gz has saner germinate output now, but gnome-shell is still being pulled in.  Now we're getting into the pain of alphabetization of package names in apt; ubuntu-unity-desktop Depends: lightdm Recommends: unity-greeter Recommends: network-manager-gnome Recommends: gnome-shell; and
[01:24] <vorlon> policykit-1-gnome sorts after lightdm, and after network-manager-gnome, so the only way to get it pulled in before apt sees gnome-shell would be to make it a recommends: of lightdm
[01:24] <rs2009> vorlon: hmm
[01:25] <rs2009> guess we could try doing that for lightdm
[01:30] <jbicha> I had no idea alphabetization mattered there!
[02:35] <vorlon> jbicha: when you get to the point of apt resolving things, it's alphabetized (because dpkg sorts depends lists in output these days), depth-first
[02:46] <vorlon> jbicha, rs2009: lasciate ogni speranza, voi chi guardate https://launchpad.net/ubuntu/+source/lightdm/1.30.0-0ubuntu6
[02:47] <vorlon> oh, this is incomplete though, it takes care of network-manager-gnome Depends: gnome-shell | policykit-1-gnome, but not Recommends: gnome-shell | notification-daemon
[02:48] <vorlon> rs2009: you have 'notification-daemon' seeded in ubuntu-unity/desktop, but this is a virtual package; which implementation are you intending to use if not gnome-shell?
[02:50] <vorlon> rs2009: oops no, there is also a real notification-daemon package! Ok
[02:50] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [22.3-13-g70ce6442-0ubuntu1~18.04.1 => 22.3.3-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[02:51] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [22.3-13-g70ce6442-0ubuntu1~20.04.1 => 22.3.3-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)
[02:51] -queuebot:#ubuntu-release- Unapproved: cloud-init (jammy-proposed/main) [22.3-13-g70ce6442-0ubuntu1~22.04.1 => 22.3.3-0ubuntu1~22.04.1] (core, ubuntu-cloud)
[04:48] <vorlon> rs2009: no gnome-shell https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu-unity/+build/374280
[07:13] -queuebot:#ubuntu-release- New binary: aad-auth [amd64] (kinetic-proposed/universe) [0.3] (no packageset)
[07:15] -queuebot:#ubuntu-release- New binary: aad-auth [s390x] (kinetic-proposed/universe) [0.3] (no packageset)
[07:15] -queuebot:#ubuntu-release- New binary: aad-auth [armhf] (kinetic-proposed/universe) [0.3] (no packageset)
[07:16] -queuebot:#ubuntu-release- New binary: aad-auth [arm64] (kinetic-proposed/universe) [0.3] (no packageset)
[07:16] -queuebot:#ubuntu-release- New binary: aad-auth [ppc64el] (kinetic-proposed/universe) [0.3] (no packageset)
[08:01] <seb128> hum, does anyone understand what's going on there?
[08:01] <seb128> https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/g/gsfonts-x11/20220921_232358_8efd5@/log.gz
[08:01] <seb128> autopkgtest [23:23:41]: @@@@@@@@@@@@@@@@@@@@ apt-source gsfonts-x11
[08:01] <seb128> blame: gsfonts-x11
[08:01] <seb128> badpkg: rules extract failed with exit code 1
[08:02] <seb128> doing an apt source gsfonts-x11 here works fine
[08:08] -queuebot:#ubuntu-release- New: rejected nautilus-dropbox [source] (kinetic-proposed) [2019.02.14-1ubuntu2]
[08:17] -queuebot:#ubuntu-release- New binary: aad-auth [riscv64] (kinetic-proposed/universe) [0.3] (no packageset)
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [amd64] (kinetic-proposed) [0.3]
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [armhf] (kinetic-proposed) [0.3]
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [riscv64] (kinetic-proposed) [0.3]
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [arm64] (kinetic-proposed) [0.3]
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [s390x] (kinetic-proposed) [0.3]
[08:17] -queuebot:#ubuntu-release- New: accepted aad-auth [ppc64el] (kinetic-proposed) [0.3]
[09:01] <ricotz> seb128, hey, maybe caused by the launchpad outage?
[09:19] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-cagatay-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[09:19] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-cai-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[09:19] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-cagney-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[09:19] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-caia-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [amd64] (focal-proposed) [1.10~20.04.1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [armhf] (focal-proposed) [1.10~20.04.1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [riscv64] (focal-proposed) [1.10~20.04.1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [arm64] (focal-proposed) [1.10~20.04.1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [s390x] (focal-proposed) [1.10~20.04.1]
[09:20] -queuebot:#ubuntu-release- New: accepted ubuntu-advantage-desktop-daemon [ppc64el] (focal-proposed) [1.10~20.04.1]
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (focal-proposed) [2.12.5-1ubuntu2~20.04.4]
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (jammy-proposed) [2.13.1-1ubuntu0.22.04.2]
[09:53] <seb128> paride, jibel, hey, I'm trying to poke at why we didn't have a desktop iso promoted since august, checking on venonat the load is at 17 and top shows
[09:53] <seb128> 16162 libvirt+  20   0 2803068 107160  19180 S 100.3  0.2  11568:16 qemu-system-x86
[09:53] <seb128> 18557 libvirt+  20   0 2800036  70260  19152 S 100.3  0.1  13061:55 qemu-system-x86
[09:53] <seb128> 21374 libvirt+  20   0 2803068  29648  19236 S 100.3  0.0  20207:32 qemu-system-x86
[09:53] <seb128> those 10k+ times sounds like an issue
[09:53] <seb128> should we stop them? what's the proper way to do it?
[10:10] <jbicha> seb128: fonts-urw-base35 in -proposed provides the gsfonts packages now so we would need to ignore that autopkgtest and later remove the gsfonts source package
[10:12] <seb128> jbicha, would be nice if syncs would show the actually changelog entries which got synced on the mailinglist
[10:12] <seb128> jbicha, also shouldn't that kind of change require a ffe at this point of the cycle?
[10:14] <ricotz> hi :), could someone take a look at https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1990373
[10:15] <jbicha> yes, I'll file a ffe for it later today
[10:16] <rs2009> jbicha: gnome-shell's finally gone, and the build's working great
[10:16] <rs2009> thanks jbicha, vorlon and sil2100 :)
[10:16] -queuebot:#ubuntu-release- New: accepted oem-sutton.simon-cais-meta [sync] (focal-proposed) [20.04~ubuntu1]
[10:16] <jbicha> rs2009: congratulations!
[10:17] <sil2100> Wooohoo!
[10:17] <rs2009> jbicha: thank you! just one minor issue I found: the firefox snap doesn't seem to get installed, despite it being present in the seed
[10:17] <rs2009> gonna take a look now
[10:18] <sil2100> rs2009: oh, there's always something to fix o/ ;)
[10:18] <rs2009> sil2100: yep indeed lol
[10:18] -queuebot:#ubuntu-release- New binary: oem-sutton.simon-cais-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)
[10:19] <rs2009> sil2100: also, was wondering why https://cdimage.ubuntu.com/ubuntu-unity/daily-live/20220922.3/ wasn't automatically bumped up to daily-live/current
[10:19] <paride> seb128, hey, I'm having a look there
[10:22] <paride> seb128, I doubt it's only a load thing, the server images are all testing fine on the same machine
[10:29] <seb128> paride, right, but I wanted to start a desktop job and attach virt-manager to it so see what's going on, it's just that with the load and the number of active jobs it's not really working
[10:34] <paride> seb128, for some reason the desktop iso testing jobs are sometimes leaving lingering VMs behind. That, plus the fact that venonat has spinning rust storage doesn't help with the load
[10:38] <seb128> paride, can we clean out those long time active ones or restart the machine/instance to get a fresh state?
[10:38] <paride> seb128, yep I cleaned those up already
[10:39] <paride> now I'm waiting for the one to debug to come up
[11:09] <seb128> paride, k, I see the load is correct and I can connect with virt-manager now, let me know if you figure out something
[11:17] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-abdiel-meta [sync] (focal-proposed) [20.04~ubuntu1]
[11:19] -queuebot:#ubuntu-release- New binary: oem-sutton.newell-abdiel-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)
[11:21] <paride> seb128, I saw a kernel panic in the post-install reboot, and I see some errors in the install logs, e.g. ubiquity: zstd: error 25 : Write error : No space left on device
[11:21] <paride> see https://paste.ubuntu.com/p/8mWgckq7BV/ line 5425
[11:21] <paride> however I didn't see 100% full partitions and we install in a 10GB image
[11:22] <paride> however let me try to bump that...
[11:22] <paride> there was less than 1GB free in /target
[11:23] <paride> so hopefully it's that easy
[11:32] <seb128> paride, thx
[11:33] <seb128> paride, where is the target partition size defined?
[11:34] <paride> seb128, the *partition* is configured by the (preseeded) installer, the whole disk size is configured in /etc/utah/config
[11:35] <paride> the smoke test installs in "use whole disk" mode so they roughly coincide
[11:37] <seb128> paride, we are
[11:37] <seb128> paride, we are taking ~10G of disk space for a kinetic desktop install so maybe that disk needs to be increased
[11:39] <LocutusOfBorg> ubuntu-archive,  please NBS-proposed cleanup luajit/luajit2/luakit on ppc64el?
[11:39] <LocutusOfBorg> luajit on ppc64el is no-go, no matter if we try the jit or jit2 backend
[11:40] <paride> seb128, I see several messages like this in the logs: rsyslogd: action 'action-8-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2208.0 try https://www.rsyslog.com/e/2007 ]
[11:40] <paride> rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') [v8.2208.0 try https://www.rsyslog.com/e/2359 ]
[11:40] <paride> These I have no idea of what they are. See https://paste.ubuntu.com/p/rcKpbMTH3k/
[11:44] <paride> in any case it seems to be behaving better now
[11:44] <paride> let's see if the test actually passes
[11:45] <seb128> paride, fingers crossed
[11:52] <paride> sil2100, passed and promoted! https://cdimage.ubuntu.com/ubuntu/daily-live/current/
[11:52] <sil2100> seb128: ^
[11:53] <paride> oops sorry
[11:53] <paride> seb128, it's an image of a couple of days ago because of these failures https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu/+build/374071
[11:54] <seb128> paride, great, thanks!
[11:56] <seb128> paride, so you increased the target disk now?
[11:56] <paride> seb128, yes, to 12GB
[11:57] <seb128> paride, 👍
[11:57] <paride> rs2009, apparently the ubuntu-unity 20220922.3 build didn't go well: https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-unity/kinetic/daily-live-20220922.3.log
[11:58] <paride> so maybe that's why it's not under pending/ nor current/
[11:58] <sil2100> ohoho, someone did a typo in the cdimage code!
[11:58] <paride> well it did go well it's the publishing that didn't go well
[11:58] <sil2100> Let me fix that
[11:58] <paride> int / inT :)
[11:59] <cjwatson> Somebody was naughty and didn't run ./run-tests?
[11:59] <sil2100> Apparently
[11:59] <cjwatson> Though I think people have not been keeping the test suite working in general ...
[11:59] <cjwatson> Might be worth some gardening time to sort that out
[12:00] <rs2009> ic
[12:00] <sil2100> A few months ago I did make it green again, since it was failing due to some bad test cases (assuming certain series), not sure if it's still green
[12:01] <cjwatson> When I tried running it just now it looked like there were maybe some missing mocks around simplestreams or something.  It was trying to actually do publishing on my laptop.
[12:01] <sil2100> rs2009: let me trigger a new build
[12:40] <seb128> could I get a +1 on https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1989359 ?
[12:41] <seb128> I'm writting the email to the documentation team
[12:45] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-abdiel-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[12:45] -queuebot:#ubuntu-release- New: accepted oem-sutton.simon-cais-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[12:55] <sil2100> seb128: done o/
[12:56] <seb128> sil2100, thanks!
[12:58] <blackboxsw> sil2100: if there is SRU vanguard review time today. cloud-init has a supplemental -proposed upload queued for 22.3.3 for Bionic|Focal|Jammy with a minor bug fix release for bugs found during SRU validation of proposed. LP: #1987318
[12:59] <sil2100> blackboxsw: looking o.
[13:21] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.167~18.04.5 => 1.173.2~18.04.1] (core) (sync)
[13:21] -queuebot:#ubuntu-release- Unapproved: grub2-signed (focal-proposed/main) [1.167.2 => 1.173.2~20.04.1] (core) (sync)
[13:44] <RikMills> sil2100: can we get this landed? https://bileto.ubuntu.com/#/ticket/4927
[14:12] <coreycb> jbicha: ginggs: the error that the new alembic triggered for zaqar autopkgtests appears to be due to no nameservers defined in /etc/resolv.conf. interestingly it only fails on arm64, which seems to be the only architecture that runs in a container.
[14:24] <utkarsh2102> coreycb: eeks. But if they fail now, they should be failing all this while, no? What’s different?
[14:26] <coreycb> utkarsh2102: it's quite possibly taking a new code path but I guess if it is expected that /etc/resolv.conf in the test machine will not container nameservers, then I may skip that arch.
[14:26] <coreycb> s/container/contain/
[14:30] -queuebot:#ubuntu-release- Unapproved: xorg-server (jammy-proposed/main) [2:21.1.3-2ubuntu2.1 => 2:21.1.3-2ubuntu2.2] (desktop-core, i386-whitelist, xorg)
[15:01] <sil2100> blackboxsw: oh, so that's an SRU on top of the current SRU? Got it
[15:02] <sil2100> RikMills: so... I sadly didn't have the time to dig into the code, didn't find any obvious workaround. Could we do the trick with copying uim over manually and the rest via Bileto?
[15:02] <sil2100> RikMills: sorry for that
[15:02] <sil2100> I'm a bit all over the place because of my incoming vacation
[15:03] <blackboxsw> yes thanks sil2100 yeah resolved the bugs while in before officially published into -updates
[15:12] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (jammy-proposed) [22.3.3-0ubuntu1~22.04.1]
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (focal-proposed) [22.3.3-0ubuntu1~20.04.1]
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted gallery-dl [source] (jammy-backports) [1.23.0-1~bpo22.04.1]
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted yt-dlp [source] (jammy-backports) [2022.09.01-1~bpo22.04.1]
[15:44] -queuebot:#ubuntu-release- Unapproved: accepted gallery-dl [source] (focal-backports) [1.23.0-1~bpo20.04.1]
[15:46] <tjaalton> I'd need a review of the mesa ffe, bug 1990387
[15:49] <blackboxsw> excellent thx sil2100 on cloud-init
[15:50] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.10.1~18.04.1 => 27.11~18.04.1] (core)
[15:50] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.10.1~22.04.1 => 27.11~22.04.1] (core)
[15:50] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.10.1~20.04.1 => 27.11~20.04.1] (core)
[16:21] -queuebot:#ubuntu-release- Unapproved: rejected etcd [source] (focal-proposed) [3.2.26+dfsg-6ubuntu0.1]
[16:29] <rbasak> ^ I'm looking at ubuntu-advantage-tools as I reviewed it prior to upload already
[16:30] <renanrodrigo> rbasak: thanks!
[16:30] <renanrodrigo> I don't see it in the queue for Xenial - how was this sorted last time?
[16:31] <rbasak> I was about to ask
[16:31] <rbasak> paride: ^ no upload for Xenial?
[16:37] <bdmurray> coreycb: We saw an issue with name resolution on armhf lxd containers recently
[16:38] <bdmurray> paride: ^
[16:39] <coreycb> bdmurray: oh interesting, maybe that's what we're hitting
[16:40] <bdmurray> coreycb: Is there a log file we can look at?
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (bionic-proposed) [27.11~18.04.1]
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (jammy-proposed) [27.11~22.04.1]
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (focal-proposed) [27.11~20.04.1]
[16:41] <coreycb> bdmurray: this is all I have currently, but the traceback and looking at the code seem pretty clear that there's no nameserver defined in /etc/resolv.conf: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/armhf/z/zaqar/20220919_101909_958b8@/log.gz
[16:43] <bdmurray> coreycb: Oh armhf? just retry it
[16:43] <bdmurray> You'd previously said arm64
[16:43] <bdmurray> I'm retrying it
[16:44] <coreycb> ah, yes. thanks. I think I retried yesterday but don't recall and maybe it's fixed since then.
[16:44] <bdmurray> The logs I saw were from the 19th and we switched image providers on the 20th-ish
[16:47] <vorlon> LocutusOfBorg: "luajit is no-go" - what has changed since the versions in the release pocket that did build successfully on ppc64el, why are we accepting a regression in architecture coverage?  Also, there are other ppc64el binary packages depending on libluajit-5.1-2 so this is complex enough that I think it warrants a bug report
[16:50] <vorlon> sil2100, cjwatson: I *usually* run run-tests before pushing :/
[16:50] <vorlon> sil2100, cjwatson: and yeah, sil2100 says it's green for him but I consistently get 4 failures around simplestreams which I have to accept ignoring
[16:57] <bdmurray> coreycb: I'm gonna rerun the results of this for you too 'retry-autopkgtest-regressions  --log-regex "no nameservers"'
[17:00] <coreycb> bdmurray: great, thank you
[17:14] <utkarsh2102> bdmurray, coreycb: hey, just ping me as well when we have the results, please
[17:19] <bdmurray> utkarsh2102, coreycb: the ones I retried have all passed
[17:19] <utkarsh2102> s.w.e.e.t!
[17:29] <coreycb> \o/
[17:29] <coreycb> thanks!
[17:34] <LocutusOfBorg> vorlon, tests were not really covering it
[17:34] <LocutusOfBorg> bugs.debian.org/1013807
[17:35] <LocutusOfBorg> bugs.debian.org/1004511
[17:35] <LocutusOfBorg> bugs.debian.org/1012362
[17:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.10.1~16.04.1 => 27.11~16.04.1] (no packageset)
[18:29] <vorlon> LocutusOfBorg: so the ppc64el binaries in the archive that depend on libluajit are broken?  Do these packages need source fixes to replace them with non-jit?
[19:59] <vorlon> LocutusOfBorg: aegisub was fixed in unstable to not build against luajit on ppc64el; looking at the others
[20:00] <vorlon> snort removed from testing, Debian bug #1019230
[20:19] <vorlon> ok how does vcmi get a runtime dep on libluajit without build-depending on lua
[20:20] <vorlon> ah n/m I was looking at jammy sources
[20:21] <vorlon> LocutusOfBorg: ok luajit revdeps removed (includes luakit), doing luajit now and then will look at luajit2
[20:29] <vorlon> LocutusOfBorg: as far as I can tell there are no binaries depending on luajit2 that don't also depend on luajit (which I find super weird).  I'll let my removals from above propagate and then recheck.
[21:27] <jbicha> ubuntu-archive: see the request in #ubuntu-devel
[22:28] <rs2009> vorlon and jbicha: the Firefox snap doesn't seem to get installed for Ubuntu Unity, despite being present in the seed (and isn't mentioned even once in the ISO build logs, even though it's present in the all.snaps file in the germinate-output folder)
[22:33] <bdmurray> rs2009: where are you seed files?
[22:35] <vorlon> rs2009: missing declaration of BASE_SEED in livecd-rootfs
[22:35] <bdmurray> found it
[22:35] <rs2009> https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/+git/ubuntu-unity
[22:36] <rs2009> vorlon: ah, didn't realise it had to be set too. thanks :)
[22:37] <vorlon> too many places that need touched, so I'm refactoring this one
[22:39] <vorlon> rs2009: https://launchpad.net/ubuntu/+source/livecd-rootfs/2.782
[22:53] <mwhudson> vorlon: https://launchpad.net/ubuntu/+source/livecd-rootfs/2.782 <- https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+ref/expand-task fixes this flavour of bs too!!
[22:53] <mwhudson> (i think anyway)
[22:54] <vorlon> mwhudson: hah.  Does that still apply cleanly?
[22:55] <mwhudson> vorlon: not sure. probably not the appropriate time in the cycle to land it :)
[22:55] <vorlon> I could be convinced otherwise
[22:55] <vorlon> -                SEED=kubuntu-active.$SUITE
[22:55] <vorlon> 113	+                FLAVOUR=kubuntu-active
[22:55] <vorlon> shouldn't this all be collapsed to FLAVOUR="$PROJECT" tho
[22:56] <vorlon> or even just lose the intermediate $FLAVOUR
[22:57] <vorlon> ah I guess the current code handles ubuntu-server -> ubuntu.  Anyway, lots of repetition there :)
[22:59] <mwhudson> vorlon: i rebased the branch, not remotely tested obv
[23:00] <mwhudson> heh i need to account for the ubuntu-unity project i guess
[23:02] <mwhudson> also heh the only reference to BASE_SEED left starts with this particularly fantastic line of code:
[23:02] <mwhudson> if [ -n "${BASE_SEED}" ] && [ -n "${BASE_SEED}" ]; then
[23:03] <mwhudson> (i have no idea what the rest of that block is doing)
[23:08] <vorlon> lolol
[23:09] <ogra> doublechecksafe !