[00:51] robert_ancell: right and thanks :) [00:55] robert_ancell: (And accepted, BTW) [03:48] Good morning [03:48] hi [03:48] infinity: lpia> that's what I did, thanks [03:49] dpb___: postgresql> no, not known to me; I saw you mailed me, will answer via email [03:49] zyga: udisks> yay you! === Garheade is now known as Garheade_AFK [04:26] hm, quantal is still frozen? [04:27] pitti: yep, until release, so saith the release manager :) [04:27] but we did release [04:27] until final release [04:28] pitti: https://lists.ubuntu.com/archives/ubuntu-release/2012-September/001981.html [04:28] uh? [04:28] *shrug* okaya [04:29] a little backscroll in -release about it as well [04:29] micahg: ah, it's the third-next email in my "to read" list; thanks for pointing out! [04:30] sure, I miss working at this hour :) [05:57] pitti: thx for the follow up. I'll file a bug tomorrow. === dendrobates is now known as dendro-afk [06:34] pitti: your 9.1.6 packages works great in my 12.04 LTS production environment [07:01] good morning [07:04] joeljacobson: thanks for the additional testing! [07:14] speaking of which… [07:14] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and general discussion for hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: didrocks [07:14] EVERYBODY: PLEASE HELP OUT SPONSORING! [07:14] * dholbach hugs didrocks [07:15] * didrocks hugs dholbach back :) (told you I couldn't last week and that I'll do my shift in a quieter time) [07:15] Mirv: hey, around? [07:16] didrocks, sure, that's totally fine [07:16] it's just that some folks seem to have moved their piloting sessions to "somewhere in the next five years", which seems to have become a problem [07:17] dholbach: maybe there is a bug in the FHS symlinking to /dev/null :) [07:17] something like that :) [07:28] dholbach: many missing patch pilot shifts? [07:28] unfortunately yes [07:29] and what's most depressing is that there are lots of requests in there which are very easy to deal with, so somebody putting in an hour could clear out many of them [07:30] dholbach: some of us are still slowed by merge proposals [07:30] micahg, can you explain? [07:31] dholbach: any simple thing that has a merge proposal vs debdiff for me multiplies the time needed to handle it [07:31] really? [07:31] yeah [07:31] bzr branch A; cd A; bzr merge B; bzr bd -- -S [07:32] in a lot of cases that's all you need to do [07:32] yeah, and then push back up (and possibly a commit or 2 for fixing stuff up) [07:33] ah, I often don't push it but let the importer do it :) [07:33] I'm at a loss for the best way to offer a patch to mod_auth_mysql package in Ubuntu. Suggestions? [07:34] dholbach: that kinda defeats the whole purpose of using a VCS IMHO [07:34] in any case it gets the patch into Ubuntu - if I do the commit or the importer does it - I'm not sure where the difference is [07:34] for me it's a step less [07:35] Is this the correct channel for my question? [07:35] didrocks: hey [07:35] Mirv: hey, look at my question on the font MR [07:35] Pelam: https://bugs.launchpad.net/ubuntu/+source/libapache-mod-auth-mysql/+filebug [07:35] Pelam: https://bugs.launchpad.net/ubuntu/+source/libapache-mod-auth-mysql/+filebug-advanced [07:35] Pelam, yes - either here or #ubuntu-motu [07:36] Pelam, you can file a bug, as sladen suggested, then attach your patch and subscribe the 'ubuntu-sponsors' team which will get somebody to take a look at it [07:36] alright, I need to rush off to the doctor - see you in a bit [07:37] Thanks guys! It's more like a feature so I was hesitant to submit it as a bug :) [07:37] Here is a small writeup about the thing: http://stackoverflow.com/questions/12543883/apache-mod-auth-mysql-with-phpass-encrypted-password-wordpress/12543884#12543884 [07:37] If you are interested ;) [07:43] sladen: Sorry, what did dholbach mean with "subscribe the 'ubuntu-sponsors' team"? [07:48] Hum... launchpad gave timeout error :( [07:48] same here [07:48] fixed now [07:48] col [07:48] cool [07:49] Hello everybody [07:50] Ah. Now I see, A "subscribe someone else" feature :) [07:53] My first patch submitted to Ubuntu project, suggestions welcome: https://bugs.launchpad.net/ubuntu/+source/libapache-mod-auth-mysql/+bug/1057946 [07:53] Launchpad bug 1057946 in libapache-mod-auth-mysql (Ubuntu) "A patch to support Phpass hash (Used by Wordpress, phpBB3, etc)" [Undecided,New] [07:59] pitti: hey, would you mind rejecting https://code.launchpad.net/~thor-peter/ubuntu/quantal/ftpcopy/bug-305831/+merge/126112 please? [07:59] done [07:59] thanks :) [08:00] Hello. Thanks for feedback! I was just in fact looking at submitting the patch to Debian. [08:05] Ignore my last message... thought someone was talking about my bug (my name happens to be Peter) === henrix_ is now known as henrix === smb` is now known as smb [08:12] SpamapS, Not in solving it yet. Seems something with the route cache. But it is slightly complicated. [08:12] Mirv: please don't remove the merge proposal :/ [08:13] Mirv: I had a followup on it [08:13] Mirv: you need the Qt version from -proposed [08:13] Mirv: can you please repropose it and get the changelog targetting -proposed? [08:21] didrocks: ah, sorry, the proposal was not very useful since the libreoffice bug filed is only a part of the larger, old bug [08:21] didrocks: and I don't think it's very sensible to change the font without editing the sources, and the sources cannot be edited with free tools alas [08:22] Mirv: ok, keep me posted if anything changed in that front [08:22] I will, there is some recent action at least now on the old bug [08:23] is LO still broken with just the qt4-x11 patch? [08:24] Mirv: ^ as you tested it (only tested your patched font with qt4-x11 patch and was looking fine in LO) [08:26] I didn't test the qt patch at all, only LO with a modified font [08:36] Laney: Sorry about all my trivial MP's [08:36] ;p [08:36] all 22 of them === mcclurmc_away is now known as mcclurmc [08:43] Laney: you are sponsoring some work from bkerensa? we should maybe coordinate to not overlap :) [08:43] didrocks: nah, he's responding to my mail on -devel [08:43] * Laney hugs bkerensa :P [08:44] ah ok :) [08:44] will do some sponsoring in a bit though [08:51] dholbach: cz tells me you can edit the fridge calendar. Can you update it to reflect our temporary DMB meeting changes please? (8th → 15th and 22nd → 29th, and delete 5th Nov) [08:51] tumbleweed: ^ is that right? [08:51] errrrr [08:51] fridge calendar [08:51] fridge, yes [08:51] but calendar [08:51] let me see [08:52] 28/09 09:46:28 who can? [08:52] 28/09 09:46:46 dholbach [08:52] Blame Laura™ [08:53] Laney, I'm afraid I can't [08:53] I added it to my calendar (j5q85mmi6ujvjtii5s1n3li5io@group.calendar.google.com), but can't edit it [08:54] ok [08:54] you could try asking in #ubuntu-news [08:54] will do [08:54] somebody in there should have the necessary powers, I can only edit the fridge blog [08:55] pitti: https://code.launchpad.net/~bkerensa/ubuntu/quantal/app-install-data-ubuntu/fix-for-control/+merge/125938 <- reject please :) [08:56] didrocks: aye sir! [08:56] thanks :) [08:57] didrocks: ahh on that one its marked as need brace removed [08:58] my understand if braces are supposed to be removed? [08:59] bkerensa: you meant, on https://code.launchpad.net/~bkerensa/ubuntu/quantal/app-install-data-partner/fix-for-brace-lists/+merge/125946 ? [09:00] didrocks: correct its on the todo to remove shell braces since they are not supported [09:00] http://lintian.ubuntuwire.org/quantal/tags/brace-expansion-in-debhelper-config-file.html [09:00] ^ [09:01] bkerensa: oh interesting, i didn't know about this lintian tag :) [09:03] bkerensa: ok, so the only issue is that you didn't target the right Vcs-Bzr, please submit on the correct branch :) [09:03] didrocks: it is now re-targeted [09:04] bkerensa: hum, I doubt the branch has the same base, did you check? [09:07] didrocks: it will not allow me to MP to the other branch [09:07] bkerensa: that happens when the base of the branch isn't the same AFAIK [09:07] bkerensa: so you need to branch from the real target branch [09:08] put your change in [09:08] >.< [09:08] commit [09:08] kk [09:08] bkerensa: well, makes sense, it's not a patched file :) [09:08] bkerensa: look at Vcs-Bzr always (there are other MR in the same case) ;) [09:08] kk [09:13] didrocks: upstream does not have the issue [09:14] bkerensa: Vcs-Bzr is not targetting upstream, it's where the packaging lives officially [09:14] if it doesn't have the issue, it means that it's either been fixed recently or that the next upload will fix it :) [09:16] (if you are speaking about that above MR ^) [09:17] didrocks: yeah it appears to be fixed recently [09:17] excellent! :) [09:18] aptitude 0.6.8.1 seems to fix the multiarch bug (I think). Would it be possible to merge it to quantal and backport it to precise and other versions? [09:19] cousteau: if it's a bug fix only release, should be possible for quantal. Care to work on that? :) [09:20] cousteau: I don't know the diff between 0.6.6 (precise) and 0.6.8, I think the safest for precise would be to cherry-pick the commit [09:21] so it turned out the reason the yubikey didn't work with my PC is that I was inserting it the wrong way around ... [09:21] bug #831768 [09:21] Launchpad bug 831768 in aptitude (Ubuntu Oneiric) "aptitude cannot handle conflicts with multiarch enabled" [High,Triaged] https://launchpad.net/bugs/831768 [09:22] I'm not actually sure 0.6.8.1 does fix the multiarch problem, but it seems so for what I read [09:24] cousteau: please try to get the patch in shape and follow https://wiki.ubuntu.com/SponsorshipProcess to get it sponsored [09:24] http://packages.debian.org/changelogs/pool/main/a/aptitude/aptitude_0.6.8.1-2/changelog aptitude (0.6.8.1-1) unstable; urgency=low * Multi-arch update for the problem resolver: - handle conflicts without removing all foreign-arch packages (Closes: #672340) (LP: #831768) [09:24] (in shape == tested ;) [09:24] Launchpad bug 831768 in aptitude (Ubuntu Oneiric) "aptitude cannot handle conflicts with multiarch enabled" [High,Triaged] https://launchpad.net/bugs/831768 [09:25] Laney: can we not find who added the event to the calendar? They can edit it [09:25] (p.s. I'm not a developer, but I'll see what I can do) [09:25] tumbleweed: dunno [09:25] delegated now [09:25] cousteau: thanks :) [09:25] Laney: :) [09:26] aptitude sponsorship> sponsoring a merge for that package will be way more effort than doing it [09:26] IME [09:26] apparently it was Cody though [09:26] didrocks, anyway I don't think patching/testing is needed since that has already done in debian [09:27] cousteau: I'll have a look at it [09:27] cjwatson: hi, someone told me about issues with the upgrade and https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1053896/comments/2 is the root cause. any thoughts what we should do ? push the update for ubuntu-keyring into -update real quick? or fix the update-manager in precise to be robust about missing keys (as long as there is a single valid sig)? [09:27] Launchpad bug 1053896 in ubuntu-keyring (Ubuntu Precise) "Add new archive key to precise" [Medium,Fix committed] [09:27] (0.6.8.1 is already in debian testing) [09:27] one day I will grep to hunt and kill "Rather than invoking init scripts through /etc/init.d, use the service(8)" message [09:27] mvo: Oh seriously? Argh [09:28] and since aptitude in oneiric/precise is in "Don't use it" state, I think backporting would be a good idea [09:28] cousteau: unfortunately the patch will probably be unSRUably huge [09:28] from previous experience [09:28] so leave that 'til later 'cos thinking about it is just going to slow me down getting it into quantal [09:29] pitti: ^- would you be happy to rubber-stamp a waiver of the usual waiting period for ubuntu-keyring/precise, to unbreak upgrades? [09:29] mvo: and once we do that, will do-release-upgrade force the ubuntu-keyring upgrade first, or do we need some kind of special measures? [09:29] ok, I've got to go now, see you [09:30] cjwatson: I don't have any formal authority about this any more, but this looks fine to me to release now [09:30] well, TB hat I guess [09:30] even on a Friday [09:31] TB hat was what I was aiming for :) [09:31] right, it's a serious enough issue that I'm going to do it and apologise later if it bothers somebody, then [09:32] mvo: copied [09:32] risk/benefit is sufficiently small here IMHO [09:32] we may end up having to revert to a single-signed Release if the problem is still gnarly, although I'd hope not to [09:32] cjwatson: we should probably add a dependency and do a SRU for update-manager, but there is no trivial way to enforce this I think because it happens before the release upgrader itself is run [09:32] (or update-manager-core) [09:32] but let me think a little bit about it [09:33] Wait, this is just for the signature on the upgrade tool itself, right, not the signature on Release? [09:33] cjwatson: just on the upgrade tool itself [09:33] I could easily change ubuntu-archive-publishing to single-sign the upgrade tool [09:33] cjwatson: would be a reasonable short term I think [09:34] cjwatson: what do you think long(er) term? make the release upgrader accept a single sig if another one is missing? [09:34] Yeah, I think it should behave like apt [09:35] cjwatson: ok, I will work on a fix [09:39] cjwatson: python-defaults was uploaded as a native package it seems, was it wanted? [09:39] didrocks: I just matched the previous version [09:40] cjwatson: sorry, not sure to get you, you mean that the previous version was also treated as a native package, right? [09:40] yes [09:40] didrocks: looking at http://archive.ubuntu.com/ubuntu/pool/main/p/python-defaults/, it seems to have been consistently native for a long time [09:41] cjwatson: ok, continuing that path then until next upstream version I guess :) just checking, thanks! [09:45] pitti: https://code.launchpad.net/~bkerensa/ubuntu/quantal/app-install-data-ubuntu/fix-for-control/+merge/126892 -> rejected please as it's the branch without the same base we discussed above. [09:55] can anyone think why gcc-4.6 in precise would silently ignore the "section" attribute on a global variable, when it works fine with gcc-4.7 in quantal? [10:07] oh, never mind, i figured it out [10:07] didrocks: that URL doesn't exist; I suppose someone already deleted the MP? [10:08] seems so [10:09] tseliot: you might like dh_fixperms for fglrx-installer-* [10:10] Laney: nice, thanks, I didn't know it [10:29] zul: test failures in the nova build [10:46] dholbach: http://reports.qa.ubuntu.com/reports/sponsoring/ < 100 now (95) ;) [10:46] @pilot out === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and general discussion for hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [10:50] mlankhorst, hi [10:50] heya [10:52] mlankhorst, can you have a look at bug 1029865? You told in comment #6 that the bug is temporary, but it is still there. Is there any chance for a fix? [10:52] Launchpad bug 1029865 in linux (Ubuntu) "Intel HD graphics: Starts always with 1024x768 resolution on a 1920x1080 monitor (HDMI and DisplayPort)" [High,Confirmed] https://launchpad.net/bugs/1029865 [10:52] didrocks, ergh, patching a conffile from casper and not reverting the patch will cause issues [10:53] tkamppeter: daniel said it was a hardware quirk and nothing can be done about it [10:53] if it was a pure sw bug it would have been easy === ivoks is now known as SiIverSpace [10:53] ogra_: Why? === SiIverSpace is now known as ivoks [10:54] cjwatson, it will cause questions on upgrades, no ? [10:54] didrocks, YES :) [10:54] ogra_: What upgrades? [10:54] +if [ -d /root/etc/gdm ]; then [10:54] + sed -i '/^[UG]ID_MIN/s/\<1000$/ 999/' /root/etc/login.defs [10:54] +fi [10:54] ogra_: What upgrades? [10:54] cjwatson, release upgrades [10:54] ogra_: In a live session? [10:54] erm [10:54] ogra_: Remember that ubiquity copies the squashfs [10:54] * ogra_ blushes and hides somewhere [10:55] ogra_: It doesn't copy the results of casper patching stuff [10:55] Quite deliberately :-) [10:55] yeah [10:55] tkamppeter: there was a different bug that also affected that hardware rthat owuld have been fixable, but in this case it just reports that some connector on vga-1 is found without edid [10:55] mlankhorst, I have also another new X problem, which appeared after an update some days ago. Sometimes, when I stay away from my PC for longer time and the screen power saving kicks in, I cannot return to my desktop, I get a black screen with only the mouse cursor. [10:55] which is, sadly, valid [10:55] tkamppeter: sigh, I'll run a valgrind over it again.. [10:55] ogra_: you put me in doubt for a sec :-) [10:55] sorry [10:56] no worry :) [10:56] tkamppeter: do you know if X is still alive at that point? [10:56] mlankhorst, you mean the valgrind for the black screen problem? [10:57] tkamppeter: maybe, do you know if X still runs at that point or not? [10:58] mlankhorst, is there a way to "blacklist" VGA1? The GPU is part of the CPU and probably there arte motherboards with different plug configurations. Perhaps mine has some kind of "dead circuit" telling to the on-CPU GPU that there is a VGA screen. [10:59] mlankhorst, unfortunately, I do not have another i5 board here. [10:59] you had a workaround for blacklisting it.. [10:59] but unfortunately there are a lot of broken displays out there that may not have a valid edid [11:00] mlankhorst, I tried a workaround, adding video=VGA1:d to the kernel command line, but this did not change anything. [11:01] For the black screen, X was probably still running, as the mouse cursor was there and I could move it with the mouse. [11:01] can you file a bug after that happens so all the relevant logs are attached? [11:02] mlankhorst, according to the display part of GNOME settings my monitor is discovered with its correct product name and native resolution. [11:02] yeah but if it's mirrored to VGA-1 that would explain it [11:03] mlankhorst, I get no crash pop-up after restarting the system afterwards. How do I report a bug which automatically attaches the correct files? [11:03] stgraber, i was just pointed at bug 50093 (yeah, 6 years old) ... shouldnt bridge-utils just call sysctl from an if-up.d script ? [11:03] Launchpad bug 50093 in procps (Ubuntu) "Some sysctl's are ignored on boot" [Low,Confirmed] https://launchpad.net/bugs/50093 [11:04] tkamppeter: apport-bug in command line [11:04] mlankhorst, can that mirroring be suppressed? [11:04] mlankhorst, apport-bug with which package name? [11:05] if you want a fix in Xorg, xrandr --output VGA1 --off; xrandr --output whatever --mode 1920x1080 [11:05] tkamppeter: just xorg === MacSlow is now known as MacSlow|lunch [11:08] mpt: http://poppy-dev.local/ - how does the legend look to you? [11:08] hm, not sure why Firefox puts such a massive gap between the groups in the legend [11:13] ev, "all collected", not "all selected" :-) [11:13] ev, other than that it looks good [11:13] hah, that's what I get for looking at the d3 api for too long [11:13] thanks [11:17] * pitti hugs didrocks after his piloting shift [11:18] mlankhorst, and where do I put this command line so that it is used by lightdm? [11:18] * didrocks hugs pitti back [11:18] erm I tend to override it [11:19] mlankhorst, what do you mean with that? [11:19] make /etc/X11/X2, executable [11:19] put this in: [11:19] #!/bin/bash [11:19] exec /usr/bin/valgrind --freelist-vol=500000000 --track-origins=yes --leak-resolution=high --malloc-fill=ef --free-fill=df /usr/bin/Xorg "$@" -verbose 10 &>> /home/mlankhorst/nfs/vg.$(hostname) [11:19] then do a symlink from /etc/X11/X to X2 [11:19] the usr/bin/X wrapper hates if /etc/X11/X is not a symlink, or if it's a symlink to a symlink [11:20] change path and it should be good to go :-) [11:20] install the -dbg packages too for synaptics, evdev, i915, xserver-xorg-core [11:21] but it's probably unneeded at this point [11:21] just something I should do now [11:21] as verification there are no random crashing bugs in quantal [11:28] mlankhorst, there are no -dbg packages of synaptics, evdev, i915. === Quintasan_ is now known as Quintasan [11:34] mlankhorst, I have followed your instructions. X is now running under valgrind. [11:35] till@till:~$ ps auxwww | grep valg [11:35] root 5426 40.3 10.7 998192 870236 tty7 Ss+ 13:31 1:07 /usr/bin/valgrind.bin --freelist-vol=500000000 --track-origins=yes --leak-resolution=high --malloc-fill=ef --free-fill=df /usr/bin/Xorg :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -verbose 10 [11:42] tkamppeter: you should have -dbg for those [11:43] at least on quantal [11:43] I added them to the most common quantal xorg server packages to make debugging a lot easier :-) === cpg is now known as cpg|away === MacSlow|lunch is now known as MacSlow [12:10] mlankhorst, I found the dpg packages now. [12:11] mlankhorst, but there are no packages with i915 in their name in Quantal, probably replaced by xserver-xorg-video-intel. [12:12] oh right [12:13] mlankhorst, now I have everything installed, I will do a system update now and then restart the session. [12:15] pitti, ubuntu-drivers-common ping [12:16] doko: what's up? [12:17] pitti, ftbfs [12:17] just retry it; slow armel builders FTL [12:17] ScottK, Riddell: https://launchpad.net/ubuntu/+archive/test-rebuild-20120922/+build/3807395 [12:21] ogra_: oh, so you guys are having fun with the current arm builders as well? [12:21] ogra_: (just reading platform release report) [12:21] err, "Foundations" [12:22] pitti, you mean webkit ? [12:22] ogra_: no, qt [12:23] pitti, ah, that one, yeah, thats from doko [12:24] pitti, webkit and qt4-x11 are upstream made issues, but yes, there are otheres too. [12:24] e.g. abiword on armhf [12:25] bryceh, https://launchpad.net/ubuntu/+archive/test-rebuild-20120922/+build/3844164 could you have a look? it's a package set [12:27] mlankhorst, now I have everything together, all -dbg packages and valgrinding X. [12:28] tkamppeter: might be a bit slower but as long as you don't use sw fallbacks you shouldn't notice it much :-) === dendro-afk is now known as dendrobates [12:35] mlankhorst, so now I only need to wait for the black screen appearing again and then attach the log to a bug report? [12:36] tkamppeter: if something suspicious shows up :-) [12:37] I need to run valgrind once too, there were a lot of bugs in quantal that could have been caught with it [12:37] precise* [12:38] pitti, re-opening ubuntu-drivers-common. needs to be addressed for the release, in one way or another [12:40] mlankhorst, I can see in the log already that my monitor reports a correct EDID, but VGA1 is without EDID at all (no pseudo EDIDE from mobo), perhaps one should dropm interfaces without EDID. === salem_ is now known as _salem [12:42] tkamppeter: and that is valid too, only windows 7 certified monitors require a valid edid [12:42] :p [12:42] iirc [12:42] mlankhorst, all of display discovery/selection is here: http://paste.ubuntu.com/1247443/ [12:44] tkamppeter: I know but upstream marked it resolved/wontfix so not much i can do about it :( [12:44] doko: re avogadro - tons of direct GL calls that aren't going to work on our armhf (it last built on arm* in natty), so that's not happening. [12:45] unless you can convince upstream it's not a problem on windows i think nothing will happen :\ [12:45] ScottK, looked like a float/double/q_float thing again [12:47] No, it's GL. [12:47] Even if it weren't, fixing whatever it is wouldn't help since the GL issues are still there. [12:52] doko: well, *shrug*, if that proves anything, it's that our arm builders have a problem [12:52] doko: I really don't want to disable tests for umpteen packages just because they occasionally fail [12:52] can't we just retry the build? [12:53] pitti, I can understand it. had retried now three times. let's keep it open until we can address it in some form [12:54] hm, I guess at last upload we still had the armel builders running on natty's kernel [12:54] that must have been long ago then [12:54] buildds switched to hf quite a while ago i think [12:54] well, if "long ago" means "two weeks", then sure [12:55] 1:0.2.69 was uploaded on September 6 [12:55] (one or two releases) [12:55] ogra_: but until recently they were running natty kernels; now they are running precise's and are swapping themselves to death [12:55] the kernel should be the same for hf and el [12:55] not that long [12:55] https://rt.admin.canonical.com/Ticket/Display.html?id=51115 [12:55] it should just use different chroots [12:55] ogra_: yes, it is [12:56] ogra_: and armel and -hf also have the same problems in e. g. glib [12:56] hmm [12:56] it's pure luck that u-d-common failed on one and succeeded on the other [12:56] in fact that indicates nihal is still on a natty kernel (as of that last update anyway) [12:56] though the referenced ticket number is wrong [12:57] i know ppisati's last merge fixed a ton of issues with power management (or rather cpufreq), i wonder if we could switch to a quantal kernel for them [13:00] pitti, did you do a testbuild on a quantal panda locally by chance ? [13:00] ogra_: no, but I can try one [13:01] * pitti powers up his board === _salem is now known as salem_ [13:02] pitti: you know you have access to porter boxes? Are they no good? [13:03] oh, scheat is back? [13:03] indeed [13:04] Daviey, they will very likely use the same kernel as the buildds [13:04] still, time to update my panda board [13:04] wont help much for checking if its a kernel issue :) [13:04] scheat is running 2.6.38 [13:04] i. e. natty kernel [13:04] ugh ! [13:04] so I'll test build on my panda with the quantal one [13:05] * pitti dist-upgrades first, that'll take a bit [13:09] ogra_: I think we need to get sysctl to run whenever we get network-device-added, though it's something we need to think about carefully and not rush into a release... [13:09] jodh might have an opinion on that as IIRC he's touched-it-last on procps :) [13:10] stgraber, yeah, i didnt mean to rush or anything it just made me feel bad that such a bug is open since 2006 [13:10] and it would be easy to work around it from bridge-utils until a proper fix is in upstart/procps [13:11] for a proper fix upstart shoudl just emit a bridged-network-up event or some such that could be added to porcps.conf [13:11] * ogra_ glares at his fingers [13:13] ogra_: udev will send a network-device-added even, so "start on ... or network-device-added" and have it run in "instance" mode would do the trick [13:14] ah, procps already has network device event code, but restricts that to static i think [13:14] well, procps start condition would work with bridges if it wasn't for the "or virtual-filesystems" part [13:15] yeah [13:15] as virtual-filesystems is usually emitted before static-network-up [13:15] if it was just "start on static-network-up", it'd most likely work fine with bridges, though it may break other things as it'd likely be starting much later on most systems [13:16] one of those things is the ipv6 privext key that we usually like to have set as early as possible (before bringing up the network) [13:17] so I think the way forward is going to be to apply sysctl once very early (start on virtual-filesystems), then once per interface (using instance + start on network-device-added) and possibly also once per kernel module load (if we can get an event for that somehow) [13:17] that should cover all the cases I can think of [13:18] Daviey,jamespage: so, update on bug 1050595: I've successfully done a 128M install by forcing lowmem mode; but I also had to delete vga=788 from the command line, otherwise lowmem mode just booted to a blank screen. I've uploaded a tweak to lowmem to avoid that problem by leaving the framebuffer enabled with vga=*, but an enabled framebuffer uses more memory, so I'm going to have to wait until I get that fix landed and in ... [13:18] Launchpad bug 1050595 in lowmem (Ubuntu Quantal) "Ubuntu Server installation with 128M ram hangs" [High,In progress] https://launchpad.net/bugs/1050595 [13:18] having 2 upstart jobs ? [13:18] ... images before I can get true memory measurements [13:19] ogra_: that or a single job using the "instance" feature of upstart (like we do in network-interface.conf) [13:19] ah [13:21] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and general discussion for hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: stgraber [13:23] stgraber/ogra_: kernel modules + network interface should cover it. That said, potentially running sysctl every time a module gets loaded seems pretty extreme. Ideally, we'd have a way to calculate the optimal number of invocations and the point at which we need to make the calls. See https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/comments/4 suggestion point (4) for some thoughts. [13:23] Launchpad bug 771372 in procps (Ubuntu Oneiric) "procps runs too early in the boot process" [Medium,Fix committed] [13:24] jodh, how about making bug 50093 a dup of that one ? ;) [13:24] Launchpad bug 50093 in procps (Ubuntu) "Some sysctl's are ignored on boot" [Low,Confirmed] https://launchpad.net/bugs/50093 [13:25] its confirmed since 2006 [13:29] tkamppeter: hey there. I'm reviewing http://launchpadlibrarian.net/117644201/brother-lpr-drivers-common_1.0.0-4-0ubuntu2_1.0.0-4-0ubuntu3.diff.gz in the queue for quantal. That one isn't linked to a bug and I don't know the uploader so I'd just like to check with you that this change should indeed work and won't somehow break the resulting binaries. [13:31] stgraber, there was nothing done on these Brother driver packages for years as the volunteer who originally made them went away/ [13:31] ogra_: done. [13:32] jamespage, is there still something to do about the java byte code format in main? [13:32] jodh, i bet you have made a bunch of waiting people happy now :) [13:32] doko, one thing I think - apport [13:33] stgraber, the debdiff is harmless, only assuring to build under Quantal, you can let it pass. By the way, the author of the patch is not the original author of these packages. [13:33] pitti, ^^^ apport & java byte code format [13:34] doko: sorry, what? [13:35] tkamppeter: ok, thanks [13:35] pitti: when compiling java files, use -source 1.5 explicitly === Quintasan_ is now known as Quintasan [13:36] oh, can do; just add that as an option? [13:36] subprocess.check_call(['javac'] + glob('com/ubuntu/apport/*.java')) [13:36] i. e. ['javac', '-source', '1.5'] ? [13:36] yes, should work [13:38] doko: ok, builds and java tests succeed; committing to trunk, thanks [13:38] doko: OOI, does something break right now? [13:39] I wasn't even aware that anyone used those [13:39] pitti: only if somebody tries to run these files using openjdk-6 [13:40] pitti: ubuntu-drivers-common fails for me locally too in the testsuite, but in other places [13:41] doko: dist-upgrade still running for me, I'll try on my panda after that [13:41] doko: are you running on precise or quantal? [13:41]