[01:19] wxl: d-i is broken in general currently, I'm working on fixing it right now. [02:07] thanks a lot infinity ;) === hyperair is now known as Guest74530 === sakrecoer_ is now known as sakrecoer [06:29] apw, infinity: looking at http://people.canonical.com/~ubuntu-archive/nbs.html: don't we need a d-i rebuild for the new (well, not so new any more) kernel? [06:29] and isn't that a blocker for d-i beta-1 images? [06:29] Laney: ^ [06:33] (including Lubuntu Alternate which we want to release...) [06:49] pitti: hi! I've been told that I should contact a SRU member, about this: https://requests.ci-train.ubuntu.com/#/ticket/1669 [06:49] pitti: do you have some time, or can you point me at someone else? [06:52] mardy: ah; I figure most SRU members tend to ignore these as they are really annoying to review (no LP generated diff, and the one in the PPA is wrong); I'll have a look later [06:52] pitti: that might explain it :-) Thanks, and let me know if I can help in some way [07:08] mardy: meh, is it really necessary to shuffle the packaging around so heavily in an SRU? [07:09] mardy: do the new libaccount-plugin-* binaries ship entirely new functionality, or were these libraries in another binary before? I don't see any Replaces:/Breaks:, so want to make double-sure that this doesn't break upgrades [07:09] * mardy checks [07:09] pitti: they are new [07:10] pitti: I think the packaging is more complex than what might seem logical, because there are some bits we also want to use in phone images, but not all (the new libaccount-plugin-* stuff is useful for unity7 only) [07:18] mardy: the yakkety version is broken (just followed up to #1565772) [07:19] why does yakkety get a 16.04+ version anyway.. [07:22] pitti: ok, I'll see if I can bump the version [07:22] same for account-plugin [07:22] the status in that bug report is *completely* wrecked [07:22] marked as v-failed for now [07:23] pitti: mmm... is there something else to be done, beside making sure that the yakkety version is proper? [07:24] mardy: I don't know -- as I said, the status in that bug is a complete wreck [07:24] e. g. look at https://bugs.launchpad.net/ubuntu/yakkety/+source/gnome-control-center-signon/+bug/1565772/comments/3 [07:24] Launchpad bug 1565772 in gnome-control-center-signon (Ubuntu Yakkety) "[SRU] Allow plugins to decide which username to set on new accounts" [Critical,In progress] [07:24] so this apparently was already uploaded to *xenial* in Ubuntu and fixed, but yet the x task was open and now there was that SRU [07:24] and the y version is *older* than that comment [07:25] so I have NFC what happened/landed where and where the bug actually got fixed :( [07:26] lots of ppc64el are "test in progress", but the test is not in progress, can it be retried? otherwise I guess they won't complete [07:26] e.g. strip-nondeterminism speech-dispatcher and so on [07:26] LocutusOfBorg: cf. #u-devel some hours ago, ppc64el was broken; I fixed it, now it's catching up [07:26] but I don't see them in the queue... [07:26] wait until the next britney run, I figure they are done but excuses.html hasn't caught up yet [07:27] ok thanks [07:27] I did have to kill various dcraw and libreoffice test requests, I'll re-queue them once the current backlog settles [07:28] pitti: weird indeed. But now, I can definitely see the persion problem for gnome-control-center-signon, so I can fix that hopefully [07:28] mardy: I also have a feeling that this isn't just a version problem but that the fixes aren't actually in y yet [07:28] pitti: but it's not clear to me what the issue with account plugins is; it looks like the version numbers are correct here: https://launchpad.net/ubuntu/+source/account-plugins [07:29] pitti: ok, let me check the actual packages [07:30] pitti: yakkety seems correct, all the packages are there, with the right files: http://packages.ubuntu.com/source/yakkety/account-plugins [07:31] mardy: I mean https://launchpad.net/ubuntu/+source/gnome-control-center-signon [07:31] mardy: this definitively doesn't have the changes from this xenial SRU [07:31] as xenial and yakkety have the exact same version [07:34] pitti: mmm... I see different versions, xenial is 0.1.8+16.04.20160201-0ubuntu1 and y is 0.1.9+16.04.20160405-0ubuntu1 [07:34] pitti: and the yakkety version seems correct, at least looking at the changelog [07:35] ah, right; how did that bump the "real" upstraem version but not +16.04? [07:35] so if the code is there, then only the version number needs bumping [07:36] pitti: don't ask me, but could it be that it was a silo with dual landing (vivid overlay + xenial) which we hoped to land for the LTS proper, but then didn't land in time...? [07:37] pitti: I see that the y package was apparently copied from xenial (so it says), but indeed that version is not in xenial [07:37] quite messy [07:38] it was probably built before yakkety existed [07:38] cjwatson: right, indeed [07:40] Mirv: so, I need to do a no change rebuild on gnome-control-center-signon for yakkety; what is the best way? should I make a dummy MP for and land it via the CI train? [07:47] mardy: you can probabl commit the new changelog record/tag directly to trunk and skip the MP/train process [07:47] or maybe you find a typo somewhere for an MP :) [07:48] W: gnome-control-center-signon source: ancient-standards-version 3.9.3 (current is 3.9.8) [07:48] mardy: ^ that might be a good thing to bump :) [07:48] mardy: you can do even just empty MP (trunk pushed to your own branch, then MP to trunk) [07:48] pitti: suggestion taken, thanks! [07:49] Mirv: I'll update the deb standards version as pitti suggested [07:49] mardy: sure === ant_ is now known as Guest56195 [08:07] tsimonq2: pitti: d-i> well, if someone fixes it then they can get a release, but if it's broken in general then I guess that's not going to be for Beta 1. [08:23] Laney: d-i is fixed in proposed. [08:24] Laney: It just needs to migrate and have ISOs rebuilt. [08:24] pitti: ^ [08:25] pitti: It got out of sync because we forced that Qt transition. [08:25] oh, so it's a question of resolving those two ftbfs [08:25] pitti: What two FTBFS? [08:25] pitti: excuses is waaaay behind reality. [08:25] linker segfaults [08:25] infinity: https://launchpad.net/ubuntu/+source/debian-installer/20101020ubuntu470 these two [08:25] pitti: Wrong version. [08:25] pitti: See above, re: excuses being behind reality. [08:26] pitti: Like, 7 hours behind. Might want to look at that. [08:26] I should be in bed. [08:26] And I'm going there. [08:26] ergh, yes, will look [08:27] Anyhow, if d-i migrates, lubuntu alternate can rebuild and be fine. [08:27] And NBS will clear out. [08:28] bug 1611010 [08:28] bug 1611010 in apt (Ubuntu) "yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''" [Critical,Fix committed] https://launchpad.net/bugs/1611010 [08:29] we have a fix for that in the images already? [08:30] Yes [08:31] Allegedly anyway [08:31] A workaround in ubiquity. [08:31] The real fix is in apt, which is still in proposed. [08:32] That's fine for me. [08:32] Why T F is britney not running though? [08:34] also, a regular Lubuntu tester reported bug 1616400 [08:34] bug 1616400 in debian-installer (Ubuntu) "Lubuntu's alternate i386 installer cannot connect to a network" [Undecided,Confirmed] https://launchpad.net/bugs/1616400 [08:34] 3728 10725 0.6 2.8 981464 927556 ? S 01:43 2:31 | \_ /usr/bin/python3 -u /home/ubuntu-archive/proposed-migration/code/b2/britney.py -c /home/ubuntu-archive/proposed-migration/code/b2/britney.conf.ubuntu.trusty -v --distribution=ubuntu --series=trusty [08:35] tsimonq2: Yes, that's the same d-i bug that's been brought up several times. [08:35] tsimonq2: And, as noted 20 lines up, will be fixed by d-i migrating. [08:36] sorry didn't see that [08:36] Stabbed, hopefully will work on a re-run [08:39] it runneth [08:43] Laney: oh, thanks (was just about to look) [08:54] pitti: well, looks like it hung retrieving autopkgtest results: http://people.canonical.com/~ubuntu-archive/proposed-migration/log/trusty/2016-08-25/01:42:59.log [09:08] Laney: it seems precise's python3 already supports the timeout= parameter for urlopen(), I'll robustify this [09:08] pitti: great! [09:10] done, https://git.launchpad.net/~ubuntu-release/+git/britney2-ubuntu/commit/?id=928be985868e [09:11] testsuite succeeds on snakefruit [09:13] nicé [09:13] d-i and apt went in === plars_ is now known as plars [13:05] did the kubuntu image builds crash or are they really still building? [13:07] tsimonq2, sakrecoer How are things looks from your point of view? [13:08] For Beta 1 that is :-) [13:08] it's coming along :) [13:08] Lubuntu Alternate needs some help [13:08] so does Kubuntu [13:08] but otherwise managing ;) [13:08] Is it going to be a late night? [13:08] flexiondotorg: what tsimonq2 said, need to check with kubuntu to see how its going for them probably [13:08] well I'm in the US, so it'll most likely stretch to the afternoon :P [13:09] sakrecoer: they have no images right now [13:09] it's still rebuilding [13:09] sakrecoer: our images say "re-building" for what feels like the whole day already? [13:09] eeek! [13:09] I got no build failure mail at least so far, so I'm clueless what's up [13:09] flexiondotorg: can't say... not enough experience i suppose. over at Ubuntu Studio, the only hardware test of amd64 has failed... trying now without encrypting home [13:10] https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/kubuntu [13:10] well.. didni't work without encrypted home... [13:10] flexiondotorg: so they're not building *right now* ? [13:10] The following packages have unmet dependencies: [13:10] kactivitymanagerd : Breaks: kactivities (< 5.20~) but 5.18.0-0ubuntu1 is to be installed [13:10] plasma-desktop : Breaks: kactivities (< 5.21) but 5.18.0-0ubuntu1 is to be installed [13:10] plasma-desktop-data : Breaks: kactivities (< 5.21) but 5.18.0-0ubuntu1 is to be installed [13:10] E: Unable to correct problems, you have held broken packages. [13:10] because http://iso.qa.ubuntu.com/qatracker/milestones/366/builds says so [13:11] They failed. [13:11] Because of the above umet deps. [13:11] I know that, I want to know if there is a build in progress [13:11] Not that I can see. [13:11] ok, then just the ISO tracker is broken [13:12] Laney, can you confirm there are no kubuntu images building right now? [13:13] yofel, We you aware of the broken packages? [13:13] s/We/Were/ [13:13] yes, we attempted to fix that yesterday/today by kicking okular off the images [13:14] yofel, Sec... just checking something. [13:14] OK, https://launchpad.net/ubuntu/+source/kubuntu-meta [13:15] Published one hour ago. [13:15] So I suggest you cancel the rebuilds in the iso tracker. [13:15] And then request builds again. [13:16] so I said to cancel the builds, and it still says (re-building) [13:16] Laney, help please ^^^ [13:17] yofel, Also check the germinate output. [13:17] http://people.canonical.com/~ubuntu-archive/germinate-output/kubuntu.yakkety/ [13:17] well, kubuntu-meta is generated from germinate, so I assume that'll be correct [13:19] yofel, Well kactivitymanagerd still appear in the desktop seed. [13:19] http://people.canonical.com/~ubuntu-archive/germinate-output/kubuntu.yakkety/desktop [13:20] yofel: I cancelled it, go request your rebuild [13:20] tsimonq2: You got new builds a couple of hours ago. [13:20] flexiondotorg: that's the one that's supposed to appear, but I see the other problem, thanks for the hint [13:20] so this will need another fixup [13:20] Laney: thanks! [13:20] Laney: I'm aware, we have queuebot in #lubuntu-devel, thanks ;) [13:21] yofel, yw :-) [13:21] tsimonq2: Well, you said that it needs some help [13:21] I did? hm [13:21] d-i is fixed [13:22] Okay then. [13:23] Go get it marked as ready [13:25] Laney: I don't have access. I'm only sort of an assistant release manager. I do everything a release manager does EXCEPT mark the images as ready and other technical things related to that. [13:25] Laney: tl;dr I don't have access [13:26] Do you have someone around to do that? [13:26] wxl does that, but if the images are tested, afair, he's ok with them being marked as ready [13:27] so usually I pop in here before he does and somebody from the release team just does it ;) [13:27] (I get on at like 8 AM my time when he's on at like noon) [13:28] k [13:28] So are they ready? :-) [13:28] desktop is 100% ready [13:28] we're just waiting on alternate [13:28] so unless you can mark half of 'em as ready (I don't know, again, I don't have access to that side of things), then no [13:30] well would you look at that [13:30] hey that works \o/ [13:30] thanks :) [14:19] Laney: this was just brought to my attention: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1616400/comments/8 [14:19] Launchpad bug 1616400 in debian-installer (Ubuntu) "Lubuntu's alternate i386 installer cannot connect to a network" [Undecided,Fix released] [14:19] Laney: could you take a look? [14:22] Laney: (Nio's recent comment) [14:24] tsimonq2: I suspect that's related to pitti's nplan work [14:24] Probably going to have to release note it [14:24] Laney: no chance we could get it fixed? [14:25] I guess we'll have to deal if that answer is no but it would be nice [14:25] Laney, tsimonq2: nplan does not meddle at all with d-i [14:25] the only thing that wouldn't currently work with an alternate installer is that NeworkManager wouldn't connect to ethernet devices, but that's *after* installation [14:25] pitti: you mean? [14:26] and d-i would have set up /etc/network/interfaces for the ethernet anyway [14:26] Yes, that's what the comment says [14:26] if I read it correctly [14:26] so the net effect should be by and large zero [14:26] so if the installer itself says "could not connect to network" that's something else [14:26] o/ [14:26] It's the installed system [14:26] Hi Nio [14:26] Nio wrote that comment, ask him ;) [14:27] oh, that's not what the description says -- but I see comment #8 now, sorry [14:27] I'm here listening [14:27] Nio: hello [14:27] Nio: did you actually configure the ethernet in d-i? [14:27] Nio: if so, it should have written /etc/network/interfaces with it [14:27] did it? [14:28] I let the installer do the default tasks, which has produced a working ethernet connection both during the installation and in the installed Lubuntu system. [14:29] Now (today's iso file) works during installation, but the installed system does not autoconnect via ethernet, but can connect via Wifi. [14:30] Nio: right, and I'm asking what /etc/network/interfaces says (and interfaces.d/*) -- d-i is expected to create one for the interface you configured in d-i [14:31] I'm not very good at networking details, but I can do the things described at https://help.ubuntu.com/community/Lubuntu/Documentation/MinimalInstall#Unmanaged_Wired_Network [14:32] I noticed that 'managed=false' and changed it to 'true', but it did not help. [14:32] Let me check that ... [14:33] Nio: no need to -- just pastebin the contents of /etc/network/interfaces please [14:33] if it helps, when doing the testcase I just did, I thought it was weird that it claimed it was an unmanaged network interface [14:36] source /etc/network/interfaces.d/* [14:36] # The loopback network interface [14:36] auto lo [14:36] iface lo inet loopback [14:37] nothing in /etc/network/interfaces.d/* ? [14:38] No [14:39] The directory exists, but is empty, not even any hidden files. [14:39] Nio: ok, then please put the above file into the bug and reopen it [14:39] and attach /var/log/installer/* [14:39] netcfg apparently failed to write an /e/n/i [14:39] tsimonq2: ^ [14:40] Which above file? [14:40] /etc/network/interfaces [14:40] ok [14:41] pitti: any chance we can get a fix for Beta 1? :) [14:41] not sure, if you find someone to investigate and work on that, it isn't too hard, and there's still time to respin/retest images.. [14:42] but the chance of that isn't too great, I figure [14:42] pitti: what's it written in? [14:42] installer logs are important, thoug [14:42] tsimonq2: the d-i component/source package is "netcfg" I believe, and it's in C [14:43] but looking at the logs first should hopefully be instructive [14:43] how can I reopen the bug report [14:43] ? [14:43] Nio: just mark as confirmed [14:43] I just did [14:43] oh cool [14:43] pitti: C...not my strong suit [14:45] netcfg was recently merged, but I see no obvious reason it would suddenly fail. [14:47] http://launchpadlibrarian.net/278554355/netcfg_1.135ubuntu6_1.138ubuntu1.diff.gz looks harmless enough anyway [14:48] Yeah. [14:48] where is the button to click? [14:48] If it were python, that indentation change would be scary, but it's not. :P [14:48] (Also, <3 gcc-6's "misleading indentation" warning) [14:49] I think I found it - marked confirmed :-) [14:50] * infinity spins up a quick test. [14:50] Have you got the files you need from the installed system now? [14:51] Aug 25 14:32:55 netcfg[31980]: DEBUG: No interface given; clearing /etc/network/interfaces [14:51] Nio: yes, thanks [14:52] ooh that doesn't look good [14:52] but earlier on: [14:52] Aug 25 14:16:36 netcfg[18267]: DEBUG: Writing DHCP stanza for enp3s0 [14:52] Aug 25 14:16:36 netcfg[18267]: DEBUG: Success! [14:52] Weird. [14:52] so it apparently is written multiple times, and on the second invocation it lost its state and cleaned the previously written one [14:52] over 15 minutes later [14:52] yeah netcfg is weird like that. [14:53] Seeing if I can reproduce with a mini.iso [14:53] we force clear things in ubuntu delta, which results in extra debug messages that wipes things before configuring things. [14:53] i hope i did not screw it up too much. [14:53] so either we fix whatever causes netcfg to be called twice, or we make it more robust to not trample over an existing /e/n/i? [14:54] The more curious question is why this suddenly stopped working. [14:55] Can I blame systemd interface renaming? :P [14:55] I like to blame it. [14:55] For everything. [14:55] I tested with the mini.iso (the i386 version that was current yesterday. It worked - wired network both during installation and in the installed system. (I made a text-only mini system, which I think is overwritten now). [14:56] infinity, when in doubt blame canada?! =) [14:56] Nio: Well, that's even more curious. I can think of no valid reason why a server install or a lubuntu install would differ. [14:57] Maybe some change since the last mini.iso was uploaded. [14:57] mini.iso == debian-installer == same thing on the lubuntu CD. [14:57] The only difference is the packages that get installed. [14:58] -rw-rw-r-- 1 nio nio 50331648 aug 10 21:03 mini.iso [14:58] s/packages/extra packages/ [14:58] Oh. That's an old one indeed. [14:58] Very. [14:58] I'm testing with yesterday's. [14:58] $ md5sum mini.iso [14:58] ccb12a3f21171bfa7c1fa0fbc34a59ed mini.iso [14:59] That was the mini.iso version available yesterday [15:01] Obviously a new version arrived yesterday [15:02] -rw-rw-r-- 1 nio nio 50331648 aug 25 11:15 mini.iso [15:02] $ md5sum mini.iso [15:02] 04468e5f9d1ba33aaba5f628c800d347 mini.iso [15:02] infinity: Are you testing it now? [15:03] Nio: Yes. Install done, about to reboot. [15:03] wow that was fast infinity [15:03] I have a fast laptop. And very fast internet. :P [15:04] installing into tmpfs with a proxy FTW :) [15:04] :D [15:05] and I thought apt-cacher-ng when using sbuild on /dev/shm was fast :P [15:05] it is [15:05] well it is, you're right ;) [15:06] could someone please push kactivities into yakkety release? That should fix the kubuntu images as that was the last recommend that I could find.. [15:06] Well, we are waiting for the result: Can mini.iso create an installed system with a working ethernet connection. [15:06] FWIW, the current mini.iso works fine. [15:07] I get a proper e/n/i with a dhcp entry for ens3 [15:07] infinity: what does the log say, is netcfg running twice? [15:07] hm, is it buggy mini.iso or the ubiquity.iso -> note that we had patches in ubiquity's patched netcfg which was there to make things nice and use NM rather than ifupdown on "desktops" [15:08] pitti, most recently twiddled with that. [15:08] Laney: see above (you're supposedly on duty?) [15:08] I cleaned up the obsolete /e/n/i and /etc/iftab migration, yes; but these were no-ops already, adn this is d-i [15:09] pitti: Define "twice". [15:09] pitti: It clears e/n/i, then writes it. [15:09] pitti: But I don't see it writing it before that. [15:09] infinity: as in the logs of that bug report [15:09] pitti: bug3? [15:09] pitti: bug#? [15:10] bug 1616400 [15:10] bug 1616400 in debian-installer (Ubuntu) "Lubuntu's alternate i386 installer cannot connect to a network" [Undecided,Confirmed] https://launchpad.net/bugs/1616400 [15:12] yofel: okay [15:12] pitti: Oh, WEIRD. [15:13] pitti: Kay. I don't see that second run on finish-install. /usr/lib/finish-install.d/55netcfg-copy-config is silent here. [15:13] pitti: But that also hints at where to look. [15:14] pitti: Bingo. [15:15] pitti: copy-config checks if NM is installed and, if so, wipes the e/n/i config. [15:15] oha [15:15] pitti: So, to follow with your netplan ideals, that should ALSO change the netplan management options. [15:15] pitti: Then we get what we want in both installers. [15:15] pitti: Sound sane? [15:15] infinity: but that would mean that the config in d-i gets ignored entirely [15:15] pitti: Yes, but it seems that's what we've always done and no one's complained. :P [15:16] infinity: yes, we could just change/amend that to create the policy snippet to let NM manage devices, but that still sounds conceptually weird [15:16] pitti: So, I'm fine with maintaining the status quo. [15:16] as long as it's just DHCP there's not much difference indeed [15:18] pitti: It actually copies NM configs. But not sure how that does anything useful since we don't use NM in d-i... [15:18] right [15:18] infinity: well, there is still a work item to port netcfg to emit netplan instead of /e/n/i, so that would help too [15:18] although it was questionable whether we'd actually do that (subiquity et al) [15:18] Or maybe it's more clever than I think. [15:18] Looks like it might actually speak NM. [15:19] pitti: So, I think just tweaking the CONFIG_NM case to also set your nplan configs the same way you do in a ubiquity nm-only world is the right answer. [15:19] pitti: And, I assume, trivial. [15:20] infinity: right, pretty well a copy&paste from http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/auto/build#L196 [15:20] pitti: Shiny. Want my name on the changelog or yours? [15:20] with substituting chroot with /target or so [15:21] pitti: (as in, want to fix it, or shall I?) [15:21] infinity: please go ahead, seems you already found the place to poke [15:21] * infinity nods. [15:21] Staring at it right now. [15:21] thanks [15:21] nice find [15:30] pitti: http://paste.ubuntu.com/23089317/ [15:30] pitti: Looketh good? [15:31] infinity: it's a real pleasure to the eyes! [15:31] thanks muchly [15:32] Tossed at the queue. [15:32] infinity: in your mini.iso installed system do you actually have some /etc/NetworkManager/system-connnection/* thing from d-i? [15:32] so then a respin with this will fix the problems? [15:32] first needs a d-i rebuild AFAIK [15:32] pitti: No, cause it was a base install, with no NM. [15:32] pitti: That block only triggers if NM is installed in /target/ [15:33] pitti: I could redo it with ubuntu-desktop. Would take longer. [15:33] should be fine; sorry, I wasn't aware that we wipe the generated /e/n/i in d-i [15:34] In context, it all makes sense. [15:34] It didn't when I first saw the chatter in the channel. :P [15:34] Please handle the unblocks and stuff [15:35] Yeah, it'll neet a d-i respin first. For obvious reasons, netcfg is in the d-i initrd. [15:35] Cause it's sort of needed to find the rest of the bits. [15:35] Well, I can do netcfg, but will be out for a bit in 90 minutes or so [15:35] I can unblock both, it's fine. [15:35] Ta [17:01] infinity: sounds like you're fixing d-i and we're getting a respin. still planning on releasing today? [17:02] wxl: Depends, are you planning on testing when the respin happens? :) [17:03] wxl: (I'm not the one releasing, you'd have to ask Laney, but he seemed on board) [17:04] yep we have testers good to go :) [17:04] Do it in the next 2-3 hours [17:05] I'm going out, and will be back to press some buttons [17:05] but if you're not ready then, I don't fancy hanging around all night :) [17:05] Laney: I'll respin for them as soon as it migrates. [17:05] Laney: If they don't meet your deadline, that's on them. [17:05] ok by me, right wxl? ;) [17:07] We could also release the remainder tomorrow [17:08] (Or they could miss beta 1) [17:08] I'm looking at kubuntu too [17:08] yofel: ^ [17:11] sorry i disappeared. i spent like 12,000 hours reading the ubuntu-release backlog. sheesh. you guys talk too much. [17:11] anyways i guess the questions are: [17:12] 1. infinity: do you have any guess as to when the migration would be complete? [17:12] 2. Laney: how long to plan on staying around for? [17:12] 0 minutes (bye!) [17:13] Laney: so 2-3 hours or nothing is what you're saying [17:13] I'll be back later [17:13] oh well we'll talk about it then :) [17:13] but not back to hang around, back to publish some images [17:14] what version of d-i and/or netcfg are we talking about here? [17:40] wxl, netcfg is 1.138ubuntu2 i believe [17:41] thx apw [17:41] wxl, and i believe d-i was 20101020ubuntu472 [17:42] apw: was or is? looks like 472 came an hour ago [17:43] looks like nfg is in main but d-i is still in proposed [17:44] Yeah, it's getting there. Patience. [17:44] I'll trigger the rebuilds as soon as it's published. [17:45] you're the man, infinity [17:47] wxl, that hour is the source publishing, and typically the binaries miss that cycle and fall in the next [18:12] hello, could you guys please let me know how long this beta1 freeze will last? [18:12] we have landed a fix related to qt5.6 in telepathy-qt, but it is waiting in proposal [18:12] boiko: A few more hours. [18:14] infinity: ok, thanks :) [18:18] Laney: When you run cron.source for milestones, run it with ALL_PROJECTS="participating projects" [18:18] Laney: Rerunning for you. [18:19] Laney: Or, maybe rerunning after the lubuntu ISOs are done, to not block. [19:08] infinity: any progress on those images? what's going on? [19:18] tsimonq2, sakrecoer I've been afk for a bit. [19:18] What's the situation? [19:18]