[11:29] base-installer: cjwatson * r328 hardy-updates/ (debian/changelog library.sh): Fix exclusion of restricted in CD installations (LP: #220805). [11:41] base-installer: cjwatson * r329 hardy-updates/debian/changelog: releasing version 1.86ubuntu2.2 [12:20] debian-installer: cjwatson * r917 ubuntu/ (build/config/x86.cfg debian/changelog): [12:20] debian-installer: * Backport from trunk: [12:20] debian-installer: - Test OMIT_WIN32_LOADER in arch_cd_info_dir and arch_miniiso targets as [12:20] debian-installer: well as arch_boot. [12:20] debian-installer: cjwatson * r917 ubuntu/ (build/config/x86.cfg debian/changelog): [12:20] debian-installer: * Backport from trunk: [12:20] debian-installer: - Test OMIT_WIN32_LOADER in arch_cd_info_dir and arch_miniiso targets as [12:20] debian-installer: well as arch_boot. [12:20] (silly CIA) [13:25] hi [13:26] cjwatson: i have a little problem when i generate a cd with latester debiancd, germinate and all. This cd is build but with 2.6.24-16 kernel and i see he want 2.6.24-19 in hardy no ? [13:31] adjust the seeds to match [13:31] and ensure you're pulling from proposed if you want -19 [13:32] ok, thanks, i will check that [13:32] user-setup: cjwatson * r101 ubuntu/ (67 files in 3 dirs): merge from Debian 1.20 [13:37] cjwatson: tasks/auto/daily/eole/hardy/supported-installer:serial-modules-2.6.24-16-386-di <- it's normal ? [13:37] oups [13:37] excuse me [13:38] user-setup: cjwatson * r102 ubuntu/debian/changelog: releasing version 1.20ubuntu1 [13:39] saispo: like I say, adjust your seeds [13:39] or update to the current Ubuntu seeds [13:41] yep :) [13:41] and in run germinate i haven't got proposed, i relaunch a build [13:51] hmmm don't understand, i pull from proposed and i have 2.6.24-16 on the cd :/ [13:51] my seeds is ok [13:53] germinate use *-proposed too [13:54] cjwatson: http://pastebin.com/m3f3340f6 [13:55] any idea why it's pruned ? [14:00] cjwatson: i found why... [14:00] it's a silly error... i go out to buy a new brain :p [14:06] cjwatson: why proposed is activate by default in installer now for hardy ? [14:07] because we're preparing 8.04.1, and need to build against -proposed to do so [14:07] ok [14:08] but when 8.04.1 is out, proposed will be removed ? [14:08] you can find the changesets that did so in the log and turn it back off, if you prefer [14:08] yes [14:08] until it comes time to prepare 8.04.2, anyway [14:08] k, thks [14:08] i understand [14:10] debian-installer: cjwatson * r918 ubuntu/build/config/x86.cfg: forgotten line continuation [14:16] debian-installer: cjwatson * r919 ubuntu/build/config/x86.cfg: ubuntu-usplash.png, not ubuntu.png [14:32] debian-installer: cjwatson * r920 ubuntu/ (3 files in 2 dirs): Don't use win32-loader on Ubuntu. [14:34] debian-installer: cjwatson * r921 ubuntu/ (build/config/common debian/changelog debian/rules): Set default suite to intrepid. [14:36] debian-installer: cjwatson * r922 ubuntu/ (3 files in 3 dirs): [14:36] debian-installer: Replace the splash image with a converted copy of the one we use for [14:36] debian-installer: gfxboot, which fits better with vesamenu. [14:40] debian-installer: cjwatson * r923 ubuntu/ (build/boot/x86/menu.cfg debian/changelog): Adjust vesamenu margin to accommodate our menu item names. [15:38] debian-installer: cjwatson * r924 ubuntu/ (49 files in 14 dirs): Move to 2.6.26-1 kernels. [15:57] localechooser: cjwatson * r135 ubuntu/debian/changelog: releasing version 2.03ubuntu1 [16:28] evand hi, there was some discussion on #ubuntu-release re wubi on releasing a couple of patches [16:31] reading scrollback on that now [16:39] grub-installer: cjwatson * r734 ubuntu/ (65 files in 3 dirs): merge from Debian 1.32 [16:45] grub-installer: cjwatson * r735 ubuntu/debian/changelog: releasing version 1.32ubuntu1 [16:47] xivulon: my fault for not running debcommit -r after the package was accepted into the archive (casper.hardy-proposed), but just as a precaution, please check to see that the archive matches bzr before committing in the future. [16:48] I could've sworn I already made the change to revert based on Mithrandir's comment and added a note for the future... [16:48] hrm [16:48] my share of blame, didn't do as many pulls as I should have [16:49] went out of sync in a few cases [16:50] lupin should be in, if we can get casper and partman-auto-loop we can start testing [16:51] note that I have pushed rev503 for wubi, that requires running make prerequisites [16:52] yeah, make prerequisites just started working for me. Last week I couldn't talk to SF's svn server. [16:52] when I cleaned up the branch forgot the /tools directory so in 502 I still have grub4dos rev58 (should be 59) [16:53] partman-auto-loop is in, it's just a matter of uploading a new ubiquity. [16:53] ah [16:53] great [16:54] I'll take care of that either tonight or tomorrow. Currently busy shoehorning the new localechooser into ubiquity. [16:54] ok, lupin is the most critical, since the other 2 only affect installing from physical CD [16:55] lupin should be in tomorrow ISO correct? [16:55] on a separate topic, had a few reports on reliability of releases/cdimage.ubuntu.com [16:55] yes [16:56] with timeouts [16:57] I noticed myself on friday night that downloading the cdimage matalink took quite a while, but did not dig further [16:57] today seems good [17:00] cdimage is for testing, I don't think you can reasonably expect high availability from it. If releases is having issues, the group to talk to would be the IS team. I'm not sure what channel they hang out in on freenode though. Perhaps try -release. [17:01] #canonical-sysadmin [17:01] do not think it is relevant anymore since users confirmed things are back to normal and I was away this w/e when it happened, if I observe the same behaviour will raise a flag [17:02] thanks cjwatson for the irc [17:02] as evand says, cdimage is expected to be slow sometimes [17:03] cjwatson, users should normally hit release first then cdimage as a fallback (so that we do not need a new build after release) [17:09] ignore that, wrong inference on my side... Probably it was only a bad local mirror + slow cdimage, in fact the error reports are not necessarily due to an issue with the metalink [17:11] I would observe the same error if the metalink from release.ubuntu.com was fine and the local mirror download was bad [17:11] I was assuming a bad metalink because I experienced that, but on cdimage... [17:18] evand 226622 is committed but not released, would it be possible to test the change so that we can have an ISO tomorrow? [17:18] I did test the code, but not the new package [17:19] the test should be to be able to boot from an ISO (not from physical CD), since without the patch that was not possible. [17:20] that is using an initrd with the new lupin-casper [17:20] lupin 0.20 is in the archive. [17:21] hmm I was looking at 226622 and was committed and did not keep the log of today's conversation with pitti [17:22] s/and was committed /and is "Fix committed"/ [17:22] great [18:47] http://synthroid.co.uk/