[03:23] doko__: so the net effect of this is that ipv6 transitional addresses would only be used for connecting to IPv6-only sites? that seems reasonable [03:34] Unfortunately the IETF consensus seems to be that breaking IPv4 NAT is a feature, not a bug. [03:34] So we get stuck trying to make it work in the real world. [03:36] well, as described, it doesn't *break* NAT; the only argument for making this change is that IPv6 transitional addresses are less reliable than established IPv4 NAT [03:37] Which I think is a fair statement. [03:39] that hasn't been my experience, FWIW - I find them equally reliable, with certain obvious benefits to being able to use a public address in the former case - but I'm ok with this change if others find that to be the case [03:39] (I had to think through it to assure myself that it wasn't going to make 6to4 and teredo /completely/ useless, since if someone has deployed either of those they've done so for a reason) [03:40] * ScottK nods [09:11] cjwatson: you added a note to https://wiki.ubuntu.com/BetaProcess right after 8.04.1 asking for a u-d-a announcement about post-release plans, but I don't find anything in my mail history about this; what level of detail were you looking for, if you remember? [09:12] hm, nothing in wetware memory ... [09:12] * cjwatson searches the external memory store :-) [09:17] 13:59 this thread on -devel has gotten me wondering... [09:17] 13:59 did anyone tell the community about the 8.04.1 plan? [09:17] 14:07 hmm, I mentioned the team focusing on 8.04.1 in a public meeting, and the .1 team meetings were on the fridge, but I'm not seeing anything where the whole plan was laid out [09:18] 14:10 I think we should try to do better at that for the next LTS [09:18] 14:10 whatever our approach is [09:18] 14:10 it seems big enough (certainly in retrospect) to have warranted a -devel-announce email [09:18] 14:27 as at least a probably-good-enough placeholder, I've added a note to BetaProcess about it [09:18] (private conversation on 2008-07-07; seems to be nothing secret though) [09:18] ok [09:19] are there any plans for 10.04.1 like there were for 8.04.1? [09:19] and I think that the thread being referred to was https://lists.ubuntu.com/archives/ubuntu-devel/2008-July/025720.html and thread [09:20] hmm, I haven't been told that there wasn't, and my understanding was that the 8.04 cycle was setting a pattern for future LTSes [09:20] but I see that LucidReleaseSchedule doesn't have anything explicit about it [09:20] in terms of dedicating folks to work on post-release fixes? [09:20] robbiew: ^- has this been discussed among the platform managers? [09:21] I mean, I've assumed there would be LTS point releases again staggered at roughly the halfway point of the cycle [09:35] cjwatson: the slight drawback of using debian-installer/splash=false is that existing server installation preseeds will have to be modified to keep the "old" (as in pre-10.04) server boot behavior [09:35] cjwatson: or am I understanding it wrong ? [09:36] ttx: isn't the server ISO setting that by default on the boot commandline? [09:36] slangasek: I was thinking about netboot-ers [09:36] ah [09:36] then yeah [09:37] I just saw the splash screen on my just-installed netbooted UEC setup :) [09:37] it's purty! [09:38] (tbh I have to look very fast to see it) [09:38] ttx: yes - I don't really see a way round that [09:38] I think I suggested release-noting that in the bug, though I don't remember for sure [09:38] in any case, preseeding has never been guaranteed to be stable from release to release [09:38] cjwatson: that works for me, we just need to document that well. [09:39] we don't break it gratuitously, but we've never hesitated to change it when we need to [09:39] (togather with the Alt-F7 trick) [09:40] cjwatson: The beta2 behavior has been working for me so far, I still have to debunk some spotty reports of failure (https://lists.ubuntu.com/archives/ubuntu-server/2010-April/004022.html) [10:33] hello folks [10:34] could anyone take a look at this? bug 561316 [10:34] Launchpad bug 561316 in codelite "Sync codelite 2.5.2.4031~dfsg-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/561316 === ogra_ is now known as ogra === rgreening_ is now known as rgreening === barry` is now known as barry_ === barry_ is now known as barry [15:17] pitti: what are the chances for a FFe for bug #45129 (diff http://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/revision/1778) ? I'm trying currently to do a formal FFe, but LP won't let me :/ [15:17] Launchpad bug 45129 in update-manager "update-manager should have per-package changelog locations (was: uses changelogs.ubuntu.com for all packages)" [Wishlist,Fix committed] https://launchpad.net/bugs/45129 [15:20] mvo: sub'ed -release and approved [15:20] mvo: it's half a bug fix anyway [15:20] pitti: nice, thanks! [15:20] pitti: I felt so too, but wanted to check with you first [15:21] thanks to you! [15:34] slangasek: wanna kick another livecd-rootfs build on acorn, just to see? [15:34] it's kinda disk abused atm, but that's just to see if I can make it fall over faster - so don't take this run as indicative of time needs [15:56] lamont, archive is out of sync on armel atm [15:56] (gnome-c-c needs to finish building and promotion) [17:45] ogasawara: doesn't matter so much - acorn fell over [20:00] lamont: is acorn less over-fallen now? Any use in another livefs try? [20:07] slangasek: well, it'll either work or fall over..drives arrive in a day or 2 [20:07] so doing another try doesn't tell you anything new :)