[00:02] oooh, yaboot?! [00:12] hmm? i thought banshee was going to wait until next week to be approved? [00:13] Urgh, who accepted banshee? [00:13] Thanks for wasting my time. [00:16] hyperair: Unfortunately there's no way to leave notes in the queue for people who don't read IRC before processing it. [00:28] cjwatson: thanks for the email, I have replied. === NCommander is now known as Guest30162 === Ursinha is now known as Ursinha-afk === NCommander is now known as Guest52279 === mcasadevall_ is now known as NCommander === henrix_ is now known as henrix [08:02] olli: OK, I will try that fix later on today (I have to leave quite soon). You can check on LP to see if libunity-webapps had an upgrade or something (or #ubuntu-unity, they should know). [08:03] hmm [08:03] olli: And regarding the version of bamfdaemon - I've got 0.3.0-0ubuntu2 installed. [08:03] should we decron and do a full image set to b2? === henrix is now known as henrix_ === henrix_ is now known as henrix === seb128_ is now known as seb128aw [09:04] all node related syncs are for the switch from /usr/bin/node -> /usr/bin/nodejs in Debian [09:05] (I'll get that added to release notes as well) [09:22] there are two OVERSIZED entries in cdimage.u.c for quntal amd64 and amd64+mac, i guess this is not so alarming since there is no cd support? [09:23] psivaa: depends, i thought the OVERSIZED check has been adjusted for the new target size.... therefore it can be alarming [09:24] * xnox now ponders about MB MiB units.... [09:25] xnox, both are 764 and 765 M's , but i suppose for quantal 800M is allowed? [09:25] psivaa: the text of the warning is miss leading. See that i386 751MB doesn't have warning. [09:26] psivaa: yeah 8000 but base 2 or base 10? [09:26] psivaa: yeah 800MB but base 2 or base 10? [09:27] http://www.wolframalpha.com/input/?i=800+MB+in+MiB [09:27] seems likely [09:27] xnox, the size is less than 800M base 2 [09:28] psivaa: otherwise known as 800MiB [09:28] Laney: I like that link! Didn't know WOlfram did that! [09:28] wolfram does all [09:28] or jsut use GNU units [09:29] Laney: so the text of the warning should be modified to say "above target size %s" and ideally substitute that value. [09:30] or just leave at above target size. [09:30] and it does look like amd64 is oversized =( [09:31] tumbleweed, i see :) [09:31] xnox, i guess so there will be something done to trim it? [09:31] * xnox is not on release team =))))) [09:31] xnox, just take a look at debian-cd :) [09:32] it has (($foo * 1024 *1024)) everywheer [09:33] ogra_: I like $foo =) [09:33] heh [09:33] lol [09:33] bytes is so unambigious. [09:45] ogra_, i am just wondering if those two oversized images will be rebuilt soon, will they :)? === mmrazik is now known as mmrazik|lunch [10:26] Daviey, I have a new upstream bugfix release prepped for ceph - OK to upload now or would you prefer if I waited until after beta-2? [10:26] its seeded but does not ship [10:26] psivaa, no idea [10:27] ogra_, ok, thanks [10:27] size change may not affect our test results too much, but just wanted to confirm, we are continuing the testing on those images [10:28] i would assume so, but for respins better wait for someone from the release team [10:29] psivaa: the oversized warning is wrong; for now, ignore it [10:29] haven't got round to adjusting those limits [10:29] jamespage: please upload, that will be fine. [10:30] it won't fit on a CD, but that was what was agreed for 12.10 [10:30] it was 1G now, wasnt it ? [10:30] 800M [10:30] oh, k [10:31] * jamespage was wondering where nodejs had got to [10:31] Daviey, ack - ta [10:37] cjwatson, ok thanks,that helps [10:40] jamespage: why the Architecture s/linux-any/any/ ? [10:40] cjwatson: "Sep 04 20:59:28 plars: the limit was already changed by slangasek" no other sources. Note that amd64[+mac] have oversize markers, but i386 does not. Although all three are >>705MB but i386 is below the magical 762.9MiB (as per Laney's link above) [10:40] xnox: the code is authoritative :-) [10:40] the warning text is misleading though =) [10:41] xnox: sod the warning text, the limit is wrong [10:41] cjwatson: well, I either have no access or don't know where it is =) [10:41] lp:ubuntu-cdimage [10:41] ah, ok. [10:42] * ogra_ still hasnt got his head arund all that python stuff :) [10:42] "This branch may be out of date, because Launchpad has not been able to access it since 2012-08-17." [10:42] lib/cdimage/tree.py:DailyTreePublisher.size_limit in this case [10:42] oh damn [10:42] well you're out of luck until I switch it to fully hosted, sorry [10:42] take my word for it for the moment :) [10:43] Daviey, actually hold fire - its in the queue twice - I think SpamapS may have already done this [10:43] cjwatson: the code is authoritative :-) [10:43] lol [10:43] * xnox "a wise man taught me that" [10:43] http://paste.ubuntu.com/1224250/ then [10:44] I mean, it has 800000000 there [10:44] but that obviously isn't working [10:44] nah, you could just have made that up in pastebin *g* [10:44] jamespage: SpamapS's seem to include an additional fix? [10:44] I'll look at it when I have a chance ... [10:44] oh, wait [10:45] my apologies, I'm completely wrong, I was misled by the units on cdimage.ubuntu.com [10:45] ok, yeah, in that case we *do* need to do something about the oversizedness and you're right it's just the warning text [10:45] sigh. coffee. [10:45] what did we decide the limit was? [10:46] 800MB (decimal) [10:46] then yeah [10:46] though I wonder if that should be 800 * 1024 * 1000 * 1000 [10:46] err, 800 * 1024 * 1000 [10:46] Daviey, yes he did - but he also did not do the python-ceph linux-any -> all change [10:46] since that's what "decimal" MB usually means [10:46] * jamespage scratches his head [10:46] You have: 800 MB [10:46] You want: bytes * 8e+08 [10:46] that pasted well [10:47] But decimal MB per disk manufacturers usually means 1000s of KiB [10:47] Because the world sucks [10:47] jamespage: but why did you do that change? [10:47] Daviey, didrocks and I discussed it after the last set of MIR actions [10:47] slangasek: ^- should we bump the size limit to 800 * 1000 * 1024, do you think? [10:47] we agreed on a number 800 but not the units.... *sigh* [10:47] jamespage: did he say why [10:48] jamespage: It seems an odd request.. [10:48] Daviey, the package has no specific architecture requirements in Ubuntu [10:48] hmm, https://en.wikipedia.org/wiki/Megabyte alleges that disks are actually pure powers of 10 [10:48] not sure that matches my experience but maybe I can't be bothered to check now [10:49] cjwatson: I'm guessing what matters is that we fit on the common 1GB usb-sticks when unpacked using usb-creator. [10:49] Daviey, suggest that you reject my upload and I'll catchup with SpamapS when he starts later today [10:49] jamespage: considering we only release linux.. linux-any == any.. So i'm suprised it was made a fuss. [10:49] cjwatson: as we target typical media sizes, not numbers. [10:49] Daviey, it was not 'fuss' - it was a suggestion for when it was next uploaded... [10:50] jamespage: ah, ok. [10:50] Did someone else just reject that? [10:50] xnox: not that simple because the 800MB was known to be an artificial target for the purposes of controlling the rate of bloat [10:50] Anyway, easy fix is drop a langpack from amd64 [10:50] I'm doing that now [10:51] who did that? ^ [10:51] cjwatson: yeah, cause "disk manufacturers" 1GB gives me 953.6 MB [10:51] Daviey: a phantom queuebot bug - it's still in unapproved [10:51] cjwatson: no, it was uploaded twice [10:51] oh [10:52] cjwatson: I just tried to reject, and was told it was already rejected by LP. [10:53] * cjwatson accepts alsa-tools to give the publisher something to do along with his seed change [10:54] cjwatson: \0/ === mmrazik|lunch is now known as mmrazik === smartboyhw_ is now known as smartboyhw === doko_ is now known as doko [12:23] when do we start milestone images publishing? [12:23] Today or Tuesday? [12:23] when we get a Conrad [12:24] Laney: I see. [12:24] * xnox off to do a quick ubiquity upload then..... [12:24] ... [12:25] * xnox is only trying to annoy Laney =) [12:25] it's all good fun eh [12:25] Laney: it's to fix top errors.ubuntu.com crasher [12:26] bug 1027648 [12:26] Launchpad bug 1027648 in ubiquity "ubiquity crashed with ValueError in command(): I/O operation on closed file." [High,Confirmed] https://launchpad.net/bugs/1027648 [12:27] great [12:27] let's see it! [12:27] https://code.launchpad.net/~xnox/ubiquity/fix-value-errors/+merge/123727 [12:27] I mean in the queue :P [12:28] * xnox mutters something incomprehensible in Russian and mentions Laney three times [12:28] * Laney assumes that they are nice words [12:28] any chance we could get the yaboot-installer fix in the queue, if we're respinning for ubiquity anyway? [12:29] not mandatory but might help the powerpc folks [12:29] * xnox waits [12:29] I'll look after lunch [12:29] at both [12:29] unless someone else gets there first [12:29] Laney: cause yaboot needs to be included in the ubiquity upload..... [12:29] oh, like that is it? [12:29] Laney: due to the funny way we repackage udebs in ubiquity. [12:30] fine, sessioninstaller can wait [12:30] well, yaboot-installer does, not yaboot [12:31] xnox: I tried having the udeb-producing source packages also spit out debs, and it was indescribably painful to maintain so I stopped :-) [12:31] believe me this sucks less [12:31] ls ../ [12:31] bah [12:31] cjwatson: I totally agree. And Build-using: X is also path to fail. [12:32] Build-Using is only useful if you can get the binaries in a useful way [12:34] cjwatson: Build-Using should get you `apt-get source $pkgs` unpacked as tarball components. And auto-substitute the version numbers in the control file. Otherwise it's just dfsg metadata hack on top of the real problem: cannot build-dep on a source package instead of binary package. [12:34] which totally makes sense for all the toolchains and compilers we have in the archive. [12:36] I don't agree [12:36] It's useful to have a way to tell the archive "don't garbage-collect this source" [12:36] accepted, to lunch [12:36] Build-deps wouldn't help for that [12:37] Laney: thanks. [12:37] cjwatson: ok. I only think with "i want to bootstrap a new arch" hat, cause I don't have "archive admin" hat yet ;-) [13:07] ^^ buddycloud-server was (hopefully) the last sync with Debian due to the node -> nodejs binary name migration === Ursinha-afk is now known as Ursinha [13:37] ^ that's the last bit of the webapps feature story [13:39] so even when we get webapps working for quantal, it'll just be fancy bookmarks since we're not doing any chromeless mode? [13:41] jbicha, fancy bookmarks, sure. That can tell when they are open [13:42] I did not want to advocate for them squeezing in more features :) [13:43] it just doesn't seem very useful yet, especially since we have the shopping integration in the dash home & the music lens [13:43] so, one of these packages is the one that gives us the new launcher webapp icons? [13:44] & the feature still has the disappearing/duplicate icons problem [13:44] Laney, new launcher webapp icons are in unity-webapps-common. They are added to launcher by default by unity, if they are present. The recent ubuntu-meta update just puts the packages in the image [13:44] jbicha, U1 is still a server side fix coming [13:44] mterry: are the 2 Amazon launchers & 2 U1MusicStore launchers in the dash known yet [13:45] jbicha, amazon should only have one icon at a time, but it does hide and reappear [13:45] jbicha, they are working on a fix for that [13:45] jbicha, and U1 team is working on theirs [13:45] jbicha, but yeah, for a feature that will cause more commercialization concerns, I wish it at least worked flawlessly :-/ [13:46] cjwatson: jbicha just noticed that gcompris somehow got into the ubuntu-desktop packageset when it's a universe package only seeded in edubuntu and was in the edubuntu packageset for 12.04. Any idea of what happened there? [13:50] good question ... [13:51] it moved secretly to restricted ? :P [13:51] ah, no, that would have just ignored it [13:51] hmm, probably something to do with the weirdness around Edubuntu DVD seeding [13:51] Let me see if that can go away nowadays === rickspencer3_ is now known as rickspencer3 [14:06] Laney: ubiquity ^^^ =) to go with yaboot and webapps stuff [14:06] great [14:07] I'd like to do the accept on that if you don't mind [14:07] as a test case for process-accepted-bugs-job [14:11] go for it [14:19] olli, mterry, popey - what is the status with the fix to libunity-webapps? Is there anything ready to be tried? [14:20] skaet, no. Are you talking about the Amazon launcher? [14:21] skaet, the bamf/window management issues seems to be resolved [14:21] mterry, no window management/missing appmenu function. [14:22] olli, great. has something been uploaded? if so, details please. [14:22] err [14:22] those launchers are literally just opening tabs in my browser [14:22] process-accepted-bugs-job: hooray, glorious success [14:22] is that right? [14:22] Laney, the chromeless mode got dropped for time reasons [14:22] I was under the impression it would still be a separate firefox window [14:23] Laney, so yeah, they open tabs, and are supposed to reflect the open/closed status of the tab [14:23] bug 745799 should no longer be an issue through this freeze; assuming that holds, I'll remove all the obsolete code and close that bug on Friday [14:23] Launchpad bug 745799 in launchpad "DistroSeries:+queue Timeout accepting packages (bug structural subscriptions)" [Critical,In progress] https://launchpad.net/bugs/745799 [14:23] or thereabouts [14:23] Laney, that was the grand vision, and will be in 13.04 [14:23] OK I could "quit" it [14:24] skaet, I don't know what resolved it, asked here yday - I have libunity-webapps0-2.3.8-0ubuntu2 which provides the missing *so.0, but the changelog doesn't hint at any update [14:24] I was not able to verify what happened [14:24] ... would it be controversial to suggest delaying installing this by default? [14:24] happened as in what fixed what I was seeing (I did an update/upgrade) [14:25] olli, would like make sure we've got fix firmly identified, so we don't get "surprised" later. I'll update my broken system and let you know what I find. [14:28] hmm. [14:29] skaet, willcooke will get in touch with you [14:30] cjwatson: nice one [14:32] olli, have applied the latest updates, rebooted machine. No change in behaviour, still no menus. === marrusl_ is now known as marrusl [14:36] * skaet working with willcooke now [14:42] skaet, does a "sudo apt-get install ubuntu-desktop^" (with the hat) pull any missing bits in? [14:45] popey, yes. libunity-webapps0 is in that set (with some others) [14:46] thats the issue then, something didn't come in or something was removed previously [14:49] Laney: I'd prefer it wait for 13.04 but I'm of course not RT [14:49] mvo: psivaa was just asking me about https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1052605 - is this a problem that really needs to be fixed in precise, for upgrade purposes, or is it strictly quantal? [14:49] Launchpad bug 1052605 in update-manager "ERROR:root:getListFromFile: no '/usr/share/update-manager/removal_blacklist.cfg' found: exception during Precise to Quantal upgrade on amd64+mac" [High,Confirmed] [14:50] jbicha: http://www.flickr.com/photos/diegoe/4843409030/ [14:50] http://blogs.gnome.org/diegoe/2010/07/30/annual-gnome-soviets-meeting/ [14:52] plars: quantal is fine I think, but I will double check - in a meeting right now [14:53] plars: FWIW the way it works is that we can fix a lot of upgrade bugs of this type just in quantal, because the release upgrader downloads a tarball of upgrade code from quantal as one of the early things it doe [14:53] *does [14:54] popey, applied, reboot has menus and proper behaviour again. Thanks. [14:55] iulian ^ if your system is also still affected.... [14:56] cjwatson: interesting, do you consider this one critical enough to make a target of opportunity? If it's not a regression, I would think the answer is normally "no", correct? [14:56] skaet, yay.. cc: olli ^^ [14:57] the question of regressions makes less sense for upgrades [14:57] and I thought I already made it a target of opportunity by accepting the rls-q-incoming nomination :) [14:58] didrocks: I don't see any sign of the upstream changes in overlay-scrollbar? [14:59] Laney: really? the previous upload was a native upload, which was wrong, I did a tarball of it and merge-upstream it, let me check [14:59] didrocks: https://launchpadlibrarian.net/117169400/overlay-scrollbar_0.2.16%2Br353-0ubuntu2_0.2.16%2Br356-0ubuntu1.diff.gz [15:00] I see the same when diffing the unpacked source packages manually, just to be sure [15:01] Laney: but, the upstream changes are in 0.2.16+r356 tarball normally [15:01] Laney: let me check [15:01] Laney: maybe the +rev353 naming was wrong [15:02] Laney: yeah, so they were backported, confirmed in -0ubuntu2 [15:02] skaet: hey, so what is the status of getting a bug fix into beta2 right now? I have a fix for ufw (would affect all images). It probably isn't worthy of a respin on its own, but would be nice to have fixed since it contains a fix for a bug found during iso testing [15:02] Laney: but at least, now, we have a real package with an upstream tarball and packaging change separated [15:02] (iso testing from last time) [15:02] Laney: which wasn't the case before [15:02] didrocks: OK, fair enough, thanks for looking [15:02] Laney: thanks for checking :) [15:02] we should have it for the Qt fix anyhow [15:02] Laney: yeah, not sure if you want it for beta2 proper [15:03] Laney: or just upgrade it afterwards [15:03] jdstrand, we haven't started spinning the images yet, so if its safe, put it on the pad as an opportunity target and go ahead with upload. [15:03] skaet: it is low regression potential and passes QRT [15:03] confirming it's fixing/workarounding the issue [15:03] i'll take it into proposed [15:03] sounds the safest :) [15:03] skaet: ok. where is the pad? [15:04] skaet: should this target quantal-proposed or just quantal? (it is a python package with only one build) [15:04] http://pad.ubuntu.com/ubuntu-release [15:07] skaet: thanks. added [15:08] cjwatson, xnox: we did agree on the units, we said 800MB. :) There was a discussion on list where pitti found that the USB sticks he tested were pure decimal. [15:08] OK [15:09] cjwatson: if we want to fudge to make powerpc fit though, it's not the end of the world [15:12] slangasek: yes, 800MB apart from MB is ambiguous. Are we using "disk-manifacturer's" MB (aka decimal / base 10) or the computer science MB (aka base 2). [15:12] slangasek: in other words can we define the sizes in bytes please =) [15:12] xnox: it's not ambiguous, we have a Units Policy. :) [15:13] slangasek: yeah, thanks for reminding me about it. [15:14] slangasek: cdimages.ubuntu.com does not compile with the Units Policy. [15:14] slangasek: it uses M when it means Mi and it uses K which doesn't exist (should use Ki) [15:15] ... or I got all of it backwards. [15:15] http://cdimages.ubuntu.com/daily-live/current/ [15:16] slangasek: powerpc isn't currently oversized [15:16] xnox: that's apache's fault and I haven't found a way to do anything about it [15:17] P.S. the official hostname is cdimage.ubuntu.com [15:17] * xnox blames chromium's auto remembering host names [15:19] iulian: shotwell ^^^ is for you [15:36] stgraber: unity is reaaaaly slow on edubuntu on kvm, is that normal and if so, something that should be release noted? [15:36] highvoltage: slower than on beta1? [15:36] highvoltage: does it at least work? [15:37] stgraber, tumbleweed: yes [15:38] highvoltage: what's your screen resolution in the VM? [15:38] here it's pretty slow by default but that's because kvm is being weird and sets up the screen at 2360x1770 :) [15:39] stgraber: 1024x768 [15:39] hmm, weird. it's reasonably fast here once I get the resolution down to 1280x800 [15:39] I rebooted into installer only and that's at least a lot better [15:40] highvoltage: what video driver are you using in kvm and how much memory do you have allocated to the vm? [15:41] (but yeah, I think Ubuntu should issue a generic, Unity completely sucks in VMs, please use something else kind of warning) [15:41] stgraber: cirrus 9mb with 1500MB RAM [15:41] (I guess the 9mb video ram is the reason why I don't get a massive default resolution) [15:41] highvoltage: ok. I'm using vmvga 9MB, also with 1.5GB of RAM [15:41] that unity-lens-photos upload is a trivial fix to a crasher that affects 103 people [15:42] * xnox ... and me. [15:42] exactly 103! [15:42] :P /me looks [15:42] skaet: Do you fancy considering the seed change? [15:44] Laney, fancy - no, but if its fixing crashers, and is safe, yeah, rather it in now before we spin images. Just don't want things to get worse though.... [15:44] It's not to fix crashers, it's to seed the packages which bring the webapp launchers in [15:46] Laney, ok, yes. [15:50] up to The Public to decide whether this makes things get worse :P [15:50] done [15:50] kenvandine: and yours, thanks for that [15:51] thx [15:51] there will be some promoting from -proposed to do before spinning [15:53] hey, re https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1048600 [15:53] Launchpad bug 1048600 in ayatana-design "[FFe] Restore "Ubuntu Medium" weights in Ubuntu's binary .deb" [High,Fix committed] [15:53] I've tracked the Qt bug down and worked around it https://bugs.launchpad.net/ubuntu-font-family/+bug/744812/comments/53 [15:53] Launchpad bug 744812 in ubuntu-font-family-sources "FontConfig/Qt stack choke on Ubuntu Medium font meta-data (No medium in Inkscape and too bold in Qt apps)" [High,Confirmed] [15:54] it's not a proper fix, 'cause that would break API, and requires work across backends and platforms [15:54] here's the patch https://launchpadlibrarian.net/117079074/fix_medium_font.diff [15:55] and packages are built in the mentioned PPA to test the impact [16:14] skaet: We might have a late edubuntu-live and edubuntu-netboot upload to change our default session on LTSP from Unity to gnome-classic (with fallback to gnome-fallback). [16:14] I think I'm going to need to upload for bug 1054323 once I figure out what the problem is [16:14] Launchpad bug 1054323 in grub-installer "Installer fails at 'grub install dummy' on PowerEdge Hardware in EFI mode" [High,New] https://launchpad.net/bugs/1054323 [16:14] Quite possibly grub2 rather than grub-installer [16:14] we should probably switch to making images for b2 ... [16:14] skaet: waiting to hear from highvoltage but considering how little progress the unity team has done on making it working in VMs, it doesn't seem likely we'll be able to ship with it in quantal [16:15] stgraber, ack. [16:15] stgraber: I'll proxy skaet and tell you to put it on the pad :P [16:15] * skaet chuckles. Thanks Laney ;) [16:16] Laney: yeah, will put a "no need to rebuild for now" note until we know what we'll be doing [16:16] stgraber, is arm going to be available for edubuntu for beta2? [16:17] skaet: nope, ARM is staying daily-only for 12.10, we won't release it [16:17] stgraber: to be honest all you need to do, is change blur effect to static & disable fade-in / fade-out. And all of those are just compiz settings. [16:17] stgraber: I did that on my machine it's flying fast now. [16:17] xnox: well, unity doesn't start at all on LTSP, so no [16:17] stgraber: ah [16:17] and unity explodes in interesting ways when using 16bit color depth [16:17] :) [16:18] skaet: Shall we go ahead and change default_milestone and decron now? [16:18] stgraber: i'd expected to expload in a rather dull way when using 16bit color depth [16:20] xnox: on 16bit: https://launchpadlibrarian.net/114128260/unity-16bit-quantal.png. It gets worse when you try to actually do something with it (like open a window) :) [16:20] use the door then :P [16:21] wow, modern art [16:23] Laney, please [16:24] (and thanks!) [16:24] skaet: it's alright, I've spotted infinity now :-) [16:24] :) === rickspencer3_ is now known as rickspencer3 [16:46] cjwatson, is it normal that there is an amd64.squashfs file at http://cdimage.ubuntu.com/ubuntu-server/daily/current/ ? === fginther is now known as fginther|lunch [16:47] bug 1048361 [16:47] Launchpad bug 1048361 in ubiquity "installer stuck in download packages even if not connected or download not selected" [Undecided,Confirmed] https://launchpad.net/bugs/1048361 === fginther|lunch is now known as fginther [16:53] ogra_: mm, I think probably a weird leftover - removed, thanks [16:54] cjwatson, so hggdh seems to still see bug 1054143 [16:54] Launchpad bug 1054143 in debian-installer "armhf-omap4: Beta 20120924 server image fails to install with "no kernels found"" [High,New] https://launchpad.net/bugs/1054143 [16:54] and comparing the .list files beween x86 and arm server images i dont see a pool on the arm side [16:54] xnox: regarding adding encrypted volumes at install time from ubiquity... [16:55] xnox: shouldn't I be able to do something with it after creating it? [16:56] xnox: oh, I see, I have to change it after creating it, and add the mountpoint then [16:57] Laney: Did someone take my name in vain? [16:57] ogra_: and I confirmed it on bamboo-feeder and on a manual install [16:58] hggdh, yeah, something is weird with the images ... [16:58] infinity: We wouldn't dare. [16:58] or infinity messed up d-i completely when bumping the ABIs :P [16:58] I was going to do some nusakan twiddling, but then you showed up. [16:58] ogra_: Seems unlikely. [16:59] plars: if you are a casual user of debian-installer (netinst / alternate / server cds), you will find the current implementation very intuitive. As in, it's a tad disorientating. [16:59] thus the :P [16:59] Laney: Feel free to twiddle what you were going to twiddle, if you were halfway there. [16:59] no, I was 0% [16:59] xnox: heh [16:59] Laney: Oh. Well, thpt. [16:59] plars: and somehow you should now upfront, that you are meant to create a separate /boot partition before creating the encrypted volume. [16:59] s/now/know/ [16:59] xnox: btw, I just got an error 141 from ubi-partman trying to remove an encrypted volume I had just created [17:00] plars: hmmm.... =( shouldn't get 141, it should not let you do that in the first place. At least I did add guards against it. Please file a bug with steps to do it. [17:00] infinity: I'll do it. It's just disabling cron and other similar things. [17:00] xnox: yes, doing that now... waiting on apport at the moment [17:00] Laney: Sure, please do. I'm tearing through queues and such. [17:01] plars: what did you try to remove? The underlying partition, the ecrypted "disk" or the final filesystem? [17:01] xnox: the underlying partition [17:01] plars: not good. [17:02] plars: there are all sorts of guards missing, same as seen on panda boards with the sd-card. The installation medium is not properly guarded. The encrypted volumes / lvm make the discovery of unguarded partitions easier. [17:03] there [17:03] I'll not do any spins or such fun until the promotions are done [17:07] So, I'm going to let the evolution 3.6.0 final stuff through, since it would be nice to see it heavily tested. [17:09] sigh [17:09] can we get overlay-scrollbar yanked from proposed please? [17:09] it slays thunderbird [17:09] Lovely. [17:09] And can do. [17:09] ogra@anubis:~/Desktop/images$ mount-image-partition quantal-server-armhf+omap4.img 2 /mnt [17:09] ogra@anubis:~/Desktop/images$ find /mnt -name *kernel-image* [17:09] ogra@anubis:~/Desktop/images$ [17:09] Have you filed a bug and/or poked the appropriate people? [17:09] cjwatson, am i assuming right that this is wrong ? [17:09] someone else commented on the bug [17:09] I'll poke now [17:10] (i.e. there should be a kernel-image udevb in the pool, or not ?) [17:10] *udeb [17:10] xnox: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1055640 [17:10] Launchpad bug 1055640 in ubiquity "ubi-partman error 141 when removing encrypted partition" [Undecided,New] [17:10] ogra_: where is mount-image-partition from!? [17:10] highvoltage, my own script [17:11] ogra_: I'm on a call [17:11] i have a bunch of image fiddling tools here === henrix is now known as henrix_ [17:11] I'll get back to you [17:11] thx === henrix_ is now known as henrix [17:11] infinity, we may get a reverted kernel, discussing with kernel team now. [17:12] Laney: Removed. [17:12] highvoltage, http://paste.ubuntu.com/1224895/ [17:12] infinity: cheers [17:12] thanks, ogra_! [17:13] skaet: Kay. Then I don't have to feel bad about letting in some userspace bits. :P [17:14] ogra_: that test is certainly wrong though; I wouldn't normally expect to see *kernel-image* on images [17:14] cjwatson, hmm, where should i look for it then ? i thought it is in pool [17:14] kernel-image is only for use when building d-i [17:14] oh, k [17:15] no point in shipping the kernel-image udeb when we have a perfectly good kernel we booted with [17:15] the bug as described there looks more like debconf template misplacement [17:15] hm, no [17:16] xnox: is there a bug open already that you are aware of for the fact that the mount point dropdown is available, but greyed out on the create partition screen for that feature? [17:16] argh [17:16] http://paste.ubuntu.com/1224904/ [17:16] not necessarily related, but definitely a bug as well [17:17] well, maybe a bit excessive, but at least it has the kernel we want [17:17]