[00:02] barry: another thing blowing up in the archive after the new python landed: https://bugs.launchpad.net/juju/+bug/1048864 [00:02] Launchpad bug 1048864 in juju (Ubuntu Quantal) "Latest python in quantal breaks juju test suite" [Critical,Triaged] [00:03] SpamapS: the same python fixes also caused https://bugs.launchpad.net/ubuntu/+bug/1048710 [00:03] Launchpad bug 1048710 in python3.2 (Ubuntu) "Regression in argparse for Python 2.7, 3.2 and 3.3" [Undecided,Confirmed] [00:04] stgraber: ah, so perhaps this is really just a dupe and the python regression will be fixed? [00:09] SpamapS: well, it's certainly a change of behaviour on the python side, now it's not completely clear whether it was intended or not and if it was, the doc is not reflecting that properly [00:10] stgraber: for now I'll leave it in a holding pattern until folks smarter than I figure it out. [00:33] stgraber, SpamapS: should we be reverting this change to python if it's causing serious regressions? [00:34] (revert, and wait for a better fix) [00:35] doko: has anyone brought bug #1048710 to your attention? [00:35] Launchpad bug 1048710 in python3.2 (Ubuntu) "Regression in argparse for Python 2.7, 3.2 and 3.3" [Undecided,Confirmed] https://launchpad.net/bugs/1048710 [00:37] slangasek, stgraber: handled for now by barry. I'm not that sure that this exposes regressions in many existing builds. but quantal will see a resolution for all pythonx.y packages [00:38] doko: ok [00:38] doko: sorry, just assigned the bug to you; feel free to reassign it to barry, or just take the credit for the bugfix when it's closed ;) [00:43] slangasek: so far juju and arkose are the only two that I'm aware of, it's apparently limited to pretty specific (weird) uses of argparse, so as it's, I think we can wait a few days. I worked around it in arkose for now (by removing the unnecessary type=str). [00:44] I see it's being looked at/discussed upstream, so hopefully we'll know more soon === dendro-afk is now known as dendrobates === cpg is now known as cpg|away === Logan_ is now known as RebeccaBlack === RebeccaBlack is now known as Logan_ === jtechidna is now known as JontheEchidna [03:35] Good morning [03:36] infinity: ntfs-3g> sure, will do; should have checked myself, thanks for pointing out === jtechidna is now known as JontheEchidna [03:46] How good is errors.ubuntu.com at verifying that a precise-proposed package fixes a crasher bug that's not trivially reproducible? === dendrobates is now known as dendro-afk [03:49] RAOF: perfect [03:49] RAOF: it measures 'fixed' by 'not happening any more' [03:50] RAOF: which of course depends on a) reproduction and b) users reporting it [03:51] infinity: done [03:52] infinity: I rejected my previous upload [03:53] RAOF: the 'perfect' was sarcasm btw [03:53] RAOF: we don't (AFAIK) have any machine learning in there yet [03:53] RAOF: but it should be fairly goof [03:54] lifeless: People seem to be reasonably good at randomly hitting the crash, so not finding any crashes in the proposed version would be a reasonable herustic [03:54] *heurstic [03:54] ... [03:55] RAOF: heuristic ? [03:56] Heh. [03:57] I am *terrible* at spelling that. [03:58] RAOF: you need a better engrish heuristic :) [03:59] :P [03:59] [04:10] pitti: Thanks. [04:11] RAOF: I kinda like "herustic". Like a log cabin decorated with Master of the Universe toys. [04:11] Masters* [04:38] infinity, ScottK: looks like the noise on bug 956071 has been sorted out, the hotkey issue is a separate bug [04:38] Launchpad bug 956071 in xserver-xorg-input-synaptics (Ubuntu Precise) "Xorg crashed with SIGSEGV in XIGetDeviceProperty()" [High,In progress] https://launchpad.net/bugs/956071 [04:42] tjaalton: Alright, that's good enough for me. [04:43] tjaalton: Released to updates. [04:43] tjaalton: Thanks for digging deeper. [04:43] infinity: excellent, thanks [04:44] I'll try to search for the hotkey bug, that must be reported === cpg|away is now known as cpg [04:53] the hotkey bug is in gnome-settings-daemon, hitting the key toggles /org/gnome/settings-daemon/peripherals/touchpad/touchpad-enabled [04:55] bug 804109 [04:55] Launchpad bug 804109 in gnome-settings-daemon (Ubuntu) "can't enable touchpad in Ubuntu (thinkpads)" [Low,Confirmed] https://launchpad.net/bugs/804109 === orated_ is now known as orated [05:11] pitti, i'm trying to introspect a p2p dbus connection (for bgo #681093) but get a "TypeError: Argument 1 does not allow None as a value". See example script here: http://paste.ubuntu.com/1198008/ [05:11] pitti, the strange thing is, that "gdbus introspect ..." works well and there is the first parameter null [05:13] pitti, see http://git.gnome.org/browse/glib/tree/gio/gdbus-tool.c#n1436 [05:24] toabctl: answering in #python [05:41] RAOF: the incompatible fglrx keeps breaking the ubuntu-drivers-common test cases; I just checked, and that seems to be right [05:41] RAOF: do you know when we'll get a compatible fglrx? [05:41] I do not, no. [05:42] ok; at least the tests do what they are supposed to do [05:42] Sarvatt or tselliot are your best bets for that knowledge; tjaalton is also has a reasonable chance of knowing. [05:45] cyphermox: https://jenkins.qa.ubuntu.com/view/Quantal/view/AutoPkg%20Test/job/quantal-adt-network-manager/lastFailedBuild/ARCH=i386,label=albali/console -> is that perhaps a missing dependency? [05:45] cyphermox: (dnsmasq) [05:57] good morning =) [06:06] pitti, RAOF: my bet is on week 41 or 42.. [07:01] good morning === cpg is now known as cpg|away [07:36] tseliot, do you think you or somebody else could respond to https://twitter.com/marcosbarbosa/status/245228540952473602? [07:37] dholbach: sure, we don't have an fglrx driver which support's Quantal's xserver ABI yet [07:38] ok === cpg|away is now known as cpg [08:19] jibel: in Jenkins, do we have tests that run under a full desktop session? [08:20] jibel: I have a work item to write UI related suspend/resume tests (indicator integration, inhibition by movie player, low battery, and so on) [08:20] jibel: but these would be full desktop integration tests === henrix_ is now known as henrix [08:24] pitti, there are a few to test unity with autopilot. They run on hardware. For example https://jenkins.qa.ubuntu.com/job/dx-autopilot-run/label=00000000-0000-0000-0000-8C89A516023C/ [08:24] jibel: ah, I was hoping for a VM (as on real hw it's rather brittle to set up auto-resume) [08:25] jibel: but that shouldn't stop me, I could stub out the actual suspend call somehow [08:25] jibel: I guess it would not be appropriate to stuff them into the daily image testing? [08:26] pitti, we could run them as post-install test [08:26] *tests [08:26] jibel: would that be appropriate for now, until we have real adt-like integration tests? [08:26] jibel: or should I rather try to use adt-*, and just depend on gnome-session etc. and run the stuff under xvfb? [08:27] ah, unity and xvfb might not be that friendly to each other, I fear [08:27] pitti, hi [08:27] hello tkamppeter_ [08:29] I have some packages which are very close to Debian or even in sync, and they have recommends which we do not have in main, foomatic-db, see bug 1048982 and ghostscript, see bug 1048820 [08:29] Launchpad bug 1048982 in printing-metas (Ubuntu) "[MIR] printing-metas" [High,Incomplete] https://launchpad.net/bugs/1048982 [08:29] Launchpad bug 1048820 in fonts-droid (Ubuntu) "[MIR] fonts-droid" [High,Incomplete] https://launchpad.net/bugs/1048820 [08:30] tkamppeter_: I thought we used foomatic-db-compressed? [08:30] pitti, my concern is that we can shoehorn the tests in the current daily image testing, but it will ported to utah soonish, which means porting the suspend/resume tests too. === tkamppeter_ is now known as tkamppeter [08:30] pitti, I'll look to provision a testbed for adt with a full desktop environment [08:30] jibel: yeah, and they don't really fit into iso testing [08:31] jibel: so perhaps we should just wait for UTAH for this? [08:31] Now for us these recommended packages are not really important, how to proceed without breaking sybcs and/or without getting extra delta. [08:31] pitti, maybe but I have no ETA, gema will know [08:32] tkamppeter: I don't understand bug 1048820 [08:32] Launchpad bug 1048820 in fonts-droid (Ubuntu) "[MIR] fonts-droid" [High,Incomplete] https://launchpad.net/bugs/1048820 [08:32] $ apt-cache show ghostscript|grep droid [08:32] $ [08:32] ghostscript doesn't recommend fonts-droid [08:32] pitti, we really use foomatic-db-compressed-ppds, but some automatic consistency checker seems to have found this stuff. [08:33] pitti, can one perhaps demote the binary package foomatic-db? Or is it not possible as it is a build dependency for other packages in main? [08:33] tkamppeter: oh, I see -- it's libgs9-common which recommends it [08:34] tkamppeter: yep, see "reverse-depends -b foomatic-db" - b-deps of m2300w and ptouch-driver [08:34] pitti, I did not set this, I even did not know that there is a package named fonts-droid. This probably comes from Debvian. [08:34] tkamppeter: right, so what the bug says -- either we drop it to a suggests, or use a font which we already install [08:35] I'm not that keen on adding YET another font to the default install [08:35] we have plenty already [08:36] pitti, I do not have fonts-droid installed and I nver had problems with Ghostscript, so I would make a suggests out of fonts-droid. [08:36] tkamppeter: sounds fine [08:37] pitti, problem is that we have another delta, as the Debian maintainer has probably some reasons to recommend it in a Debian environment. [08:37] tkamppeter: as for foomatic-db, perhaps m2300w etc. also build with -compressed as a b-dep somehow? [08:38] pitti, problem is that m2300w and ptouch-driver ship Foomatic XML files and no corresponding PPDs, so the build process has to build the PPDs which needs foomatic-db. [08:41] tkamppeter: so you could also drop printer-driver-all recommends to suggests? [08:42] pitti, I am investigating now whether the two driver packages really need foomatic-db to build ... [08:42] pitti, main problem of foomatic-db is that it is synced with Debian. [08:42] tkamppeter: no, it's not -- 20120823-0ubuntu1 here ? [08:43] jibel: ok; let me play around with how much of a session I can get in xvfb and the adt env [08:44] pitti, it is at least identical. Sometimes I update from OpenPrinting, sometimes OdyX. All in the debian/ directory is always the same. [08:44] tkamppeter: ah, so perhaps some syncs are in order to get us to identical versions? [08:44] tkamppeter: so ideally the foomatic-db build deps coudl be dropped [08:45] tkamppeter: if not, we coudl change the foomatic package in Debian to add the recommends only when you build for Debian, but not for Ubuntu === henrix is now known as henrix_ === henrix_ is now known as henrix === doko_ is now known as doko [08:56] pitti, is ibus-m17n wanted in main? you did add support for it in language-selector (but already in precise), and cjwatson seeded it in June [08:57] hm, not sure -- it fell out of main after lucid apparently [08:59] *shrug* I think I was just syncing up with something or other [08:59] why does that only pop up now, hmm; /me reads seed history [08:59] Probably with language-selector [08:59] ah [08:59] revno: 1738 [08:59] drop ibus-m17n, it's a very little used package and has far inferior input methods compared to pinyin; use pinyin with small db-android instead; per Aron Xu [08:59] timestamp: Fri 2010-08-20 14:33:14 +0200 [08:59] Yeah, but l-s should match the seeds either way [08:59] so that's what caused it to drop out of main [09:00] r2051 [09:00] we should drop it from l-s then? [09:00] I have no opinion on whether -m17n is any good or not, but if it isn't, it should be dropped from the seeds and l-s in tandem [09:00] ArneGoetje: hey Arne, how are you? [09:00] ArneGoetje: do you know of m17n is still relevant for anything? [09:01] cjwatson: yes, I agree [09:01] bug 753476 [09:01] Launchpad bug 753476 in language-selector (Ubuntu) "[te]ibus-m17n needs to be part of CD/DVD for indic language support " [Medium,Fix released] https://launchpad.net/bugs/753476 [09:01] filed some months after r1738 [09:01] ah, there we go [09:01] right, then I guess let's just promote it back? [09:02] . o O { yay for having history for everyting } [09:03] This is what it's for ... [09:04] doko: re-promoted then [09:04] thanks! === mcclurmc_away is now known as mcclurmc [09:48] ev, poppy-dev doesn't have the data point tooltips. Is that deliberate? [09:49] mpt: try now [09:50] bueno [09:50] So, what was the spike yesterday? [09:52] mpt: not sure yet - firefighting the django openid deployment. Will dig in a bit === cpg is now known as cpg|away [10:18] doko: ceph currently has some binaries which are in universe - rest-bench being one of them which has this dep [10:49] pitti: I'm going to write a bug for the music player showing up in quantal as a usb driver what commands are you likely to want me to run to help you guys diagnose it? [10:50] pitti: also I'm assuming the fix you added to precise got pulled in right? [10:52] pitti: and would a comparison with what precise lists be useful? [10:57] jamespage, I assume I'll just have to add rest-bench-dbg to Extra-Excludes [10:57] doko, yes please - I really don't think the rest-bench packages need to go into main [10:57] radosgw is another matter [10:59] any known bug that could cause gobject-introspection stuff to be commented out in generated Makefile ? [11:00] building tp-glib from source does not build .gir, wondering if that could be a bug in ubuntu quantal gobject-introspection package or something like that [11:04] cjwatson: can I bug you for some help with a quantal upgrade please - it's left my machine in a bit of a state [11:06] davmor2: re (sorry, was at the phone) [11:06] davmor2: an useful piece of information/comparison would be "udevadm info --export-db", this will tell me whether the device was recongized as a player [11:07] bah forget my question above, found my error :) [11:08] bigjools: well, I may or may not know the answer, but sure [11:08] cjwatson: ok, I'll just paste some stuff [11:08] pitti: apparently AlanBell has a similar issue with his android phone too [11:09] cjwatson: but first problem is that I have two X servers running on different vts [11:10] I know nothing of that [11:10] cjwatson: then this http://pastebin.ubuntu.com/1198419/ [11:10] bigjools: could you tar up /var/lib/dpkg and put it somewhere for me please? [11:10] sure [11:11] probably not immediately worth debugging your X problem until your package database is in a remotely sane state [11:11] yeah [11:11] but if it persists then you'll want somebody from the desktop team [11:11] ok [11:11] is U1 a suitable place for you to pick up files? [11:12] ah I'll stick it on chinstrap [11:12] pitti: http://paste.ubuntu.com/1198424/ [11:12] U1 would mean I'd have to figure out why my syncdaemon is busted [11:12] which I've been merrily ignoring [11:12] heh [11:12] I just thought that I'm not sure I can rely on mine in this state [11:12] I think somebody posted me a weblink from U1 recently that no longer required extranous sign-up [11:15] pitti: udevadm stuff, quantal = http://paste.ubuntu.com/1198425/ and precise = http://paste.ubuntu.com/1198430/ and I just thought I'm not sure what package to write it against :( [11:20] mpt: is there anything in the javascript console? [11:20] errors, that is [11:22] ev, [12:20:31.651] SyntaxError: JSON.parse: unexpected character @ http://poppy-dev.local/static/js/yui/build/json-parse/json-parse-min.js:7 [11:23] mpt: does it change if you click on a bucket page and login first? [11:24] ev, there's no buckets to click on [11:24] bigjools: right, so this is basically http://lists.debian.org/debian-devel-announce/2012/03/msg00005.html [11:24] (that won't especially help immediately, just for background) [11:24] ok, reading [11:24] bigjools: I suspect this won't work, but try 'sudo dpkg -P libao4' [11:25] cjwatson: same dpkg error [11:25] OK, let's edit dpkg's brain [11:25] \o/ [11:25] trepanning [11:26] bigjools: edit /var/lib/dpkg/status. There are two paragraphs that start with "Package: libao4"; you want the one that also contains "Architecture: amd64". Delete that paragraph. [11:26] ok [11:26] (It should be "Status: deinstall ok config-files". [11:26] The old dpkg incorrectly left this in a half-arsed state on a previous upgrade. [11:27] it's now an ex-paragraph [11:27] Now 'sudo dpkg --configure -a' [11:28] doing stuff, but reporting dependency problems [11:28] Yeah, expected since you were probably interrupted mid-upgrade [11:28] looks like it :( [11:28] But it'll do what it can to start with [11:28] Then 'sudo apt-get -f install' [11:28] ok it's done [11:28] And after that I'd run 'sudo apt-get dist-upgrade' [11:28] zoiks [11:29] it wants to remove about 100 packages [11:29] pastebin? [11:29] ev, http://paste.ubuntu.com/1198449/ [11:30] bigjools: Out of interest did you use update-manager to do this upgrade - that is, if update-manager happened to have been smart enough to detect this problem earlier, would it have helped? [11:30] cjwatson: http://paste.ubuntu.com/1198460/ [11:30] I did use update manager yes [11:30] and I suspect anything would have been better than this :) [11:31] short of leaving it unbootable [11:31] Well, yeah, all I mean is we can't fix the bare apt-get dist-upgrade path so easily [11:31] But in principle we can beef up u-m to help people who use it [11:32] so it wants to remove 238 in fact [11:32] So, that's entirely multiarch-related stuff; it could be caused by any one of those packages being out of sync between amd64 and i386, which is a standard multiarch problem while running development releases [11:33] If this were my system I would let it remove all of that and worry about putting google-earth-stable, skype, and wine1.4 (which are the application-level packages in there) back later [11:33] yeah [11:34] Oh, with the exception of erlang-docbuilder which has genuinely been removed from quantal === _salem is now known as salem_ [11:34] well, I hit the button, let's see how it goes :) [11:35] This systematic out-of-sync problem will be fixed once we start using -proposed to stage everything in a cycle or two [11:35] ev, if the Launchpad info is effectively just for styling the rows, have you considered displaying them unstyled quickly, and then applying the class= attributes when the Launchpad data arrives? [11:35] mpt: yes, I've thought about it, but it requires fetching much of the same data twice [11:35] ev, you changed the error: Timestamp: 11/09/12 12:34:10 [11:35] Error: SyntaxError: JSON.parse: unexpected end of data - Source File: http://poppy-dev.local/static/js/yui/build/json-parse/json-parse-min.js Line: 7 [11:35] hmm [11:35] that shouldn't change [11:35] but try logging in off a problem page [11:35] clicking on a function link [11:35] that's what I think I fixed [11:36] slangasek: ^- Do you know of a bug that corresponds to bigjools' multiarch upgrade disaster? We should definitely do something about this in ubuntu-release-upgrader [11:36] ev, success [11:36] yay [11:36] tuples should suffer an awful death [11:38] now to fix your javascript error [11:42] mpt: does http://poppy-dev.local/api/1.0/instances-count/?format=json&limit=365 work? [11:43] ev: that or just don't use them :P [11:45] ev, I'm not going to count parentheses, but it looks right [11:45] cjwatson: ha, dist-upgrade shows 1988 packages to upgrade. I am guessing my u-m bailed out very early :( [11:45] weird [11:45] davmor2: indeed :) [11:45] cjwatson: the question is, will it have missed important upgrade steps I need to care about? [11:46] ev: just use lists always see how much havoc that causes instead ;) [11:47] bigjools: probably not; I don't think there are many quirks in the precise-to-quantal upgrade as yet [11:48] righto [11:48] bigjools: you might want to ensure that all the PPAs you care about are enabled at the end of the upgrade [11:48] cjwatson: yeah, done that already, it's one of those automatic things you do after upgrades I guess [11:49] pitti, no, dnsmasq-base is pulled in... there is something else; perhaps ifblacklist_migrate.sh isn't doing what it should well enough so the connections never come up; that would explain dnsmasq not starting [11:51] * mpt winces at bug 947107 [11:51] Launchpad bug 947107 in ubiquity (Ubuntu Precise) "No partition labels in 12.04 partition wizard" [High,Triaged] https://launchpad.net/bugs/947107 === MacSlow is now known as MacSlow|lunch [12:00] mpt: I've narrowed it down to just happening in Firefox. I'll figure it out after lunch. [12:09] doko via slangasek: are you looking at bug #1048710 or should i spend some time on that today? [12:09] Launchpad bug 1048710 in python3.2 (Ubuntu) "Regression in argparse for Python 2.7, 3.2 and 3.3" [Critical,Confirmed] https://launchpad.net/bugs/1048710 [12:09] barry, please go ahead, you already started the upstream issue =) [12:10] doko: k! [12:14] mpt: I did add a comment to it, after I did some minimal test. But still needs more time. === orated_ is now known as orated === Zdra is now known as xclaesse === didrocks1 is now known as didrocks [12:47] doko: lowering javascript-common to Suggests for lp #1020278 [12:47] Launchpad bug 1020278 in wwwconfig-common (Ubuntu) "[MIR] raphael" [High,Incomplete] https://launchpad.net/bugs/1020278 [12:47] would be the fix, is that ok with you? === Guest4054 is now known as zumbi [13:01] roaksoax, sure, if it makes sense. [13:03] doko: /win 13 [13:03] err soryr :) === MacSlow|lunch is now known as MacSlow === didrocks1 is now known as didrocks [13:36] infinity, ogra_ : https://launchpadlibrarian.net/115081690/buildlog_ubuntu-quantal-armel.pdf2djvu_0.7.12-2ubuntu5_FAILEDTOBUILD.txt.gz ?? [13:42] cjwatson, cat is in the just rebuilt coreutils === skaet_ is now known as skaet [13:46] doko: what? [13:46] Oh geez [13:47] but wait, this the pdf2djvu was built on friday, before the upload [13:47] doko: Are you sure this isn't a toolchain regression? I didn't touch cat at all [13:47] no, if built on Friday, this was before the binutils and gcc uploads [13:48] where does this message come from, kernel printf? [13:49] running a 2.6.38 kernel [13:50] aren't some of the builders on precise? [13:54] hrmm, how close to latest 3.6-rc kernel is the current quantal kernel? [13:54] I think quantal is on 3.5.3 [13:55] Good question; I can't find that text in eglibc, which is where I expected to find it [13:55] Oh, libgcc maybe? [13:56] micahg: do you know if 3.6-rc is packaged anywhere for precise? [13:57] * micahg just sees quantal in the mainline dir, kernel team would probably know more [13:57] doko: src/libgcc/config/arm/linux-atomic-64bit.c [13:57] in gcc-4.7 [13:58] lovely [13:59] * cjwatson neatly deflects blame [13:59] * highvoltage is an expert at deflecting blame [13:59] * highvoltage blames the education system for that [14:00] cjwatson, ok, fsf 4.7.why do we see this only now? [14:01] hmm, that's because we default to v5 [14:03] is it even worth to put time into armel at all ? [14:04] * ogra_ thinks we can count its lifetime in weeks anyway [14:05] Personally I like ports to die by explicit decision rather than by falling apart [14:05] heh, true ... and fixing it will likely help debian ... [14:06] though i wonder why we cant just take that decision instead of wasing time on it :) [14:06] barry: any word on that python argparse regression? [14:06] SpamapS: not yet, but working on it [14:07] barry: ok. I have a slightly different failure case involving FileType.. but I think its basically the same problem. [14:08] SpamapS: if you can boil it down, can you add it to the (launchpad) bug report and i'll at least check it? [14:08] barry: yeah I am doing that right now [14:08] cool [14:12] barry: ok, test case posted to bug 1048710 [14:12] Launchpad bug 1048710 in python3.2 (Ubuntu) "Regression in argparse for Python 2.7, 3.2 and 3.3" [Critical,Confirmed] https://launchpad.net/bugs/1048710 [14:15] smoser: hi, did you see my pings over the weekend about testing the new mountall package in our iscsi cloud environment? [14:15] (well, cloud-init) [14:20] slangasek, i mean to get to that today. [14:20] smoser: ok :) [14:22] pitti, I have eliminated the foomatic-db build dependencies in both m2300w and ptouch-driver. [14:23] tkamppeter: nice! [14:23] mpt: fixed: http://poppy-dev.local/ops/instances/ [14:23] so yeah, 3,341 on the 7th. 1,651 on the 6th. [14:24] for 12.10 [14:24] \o/ [14:24] 3341 what? [14:25] Oh, right, the blue line [14:25] So, that's the beta 1 release [14:26] but why would that cause a spike, if we're dividing by the number of machines anyway? [14:26] Maybe there's an influx of people trying previously-untested things? [14:27] hm [14:27] mpt: is there a correlation between a spike with # of machines upgrading to quantal? [14:27] lets see what the 90 day user count did that day [14:27] ;) [14:28] aha [14:28] I was thinking the division would remove that factor completely [14:28] but it will only completely remove it 90 days later [14:28] The first day, it removes only 1/90 of it [14:29] or does it [14:29] No, we're dividing by the 90-day total, not by the last-90-days average [14:29] hmmmm [14:29] mpt: unique systems count for 12.10 was 20596 and 21612 for the 6th and 7th respectively [14:30] A 5% increase [14:30] tiny [14:31] slangasek, to clear my memory... even if i have the moutnal fix, i'll still need some hacks though, right? [14:31] ev, but you know what, the #1 error is in ubiquity. What happens to the error rate if you ignore just that error? [14:31] because i need /run to be mounted (and mountall emitted) before cloud-init runs. [14:31] I'm pretty sure it wasn't ubiquity yesterday, or the day before [14:31] ho. wait, no. that will happen in parallel with your branch. [14:34] mpt: 551 and 565 for the 6th and 7th [14:34] So there's the spike explained. It's ubiquity. [14:34] =( [14:35] too many daily iso testers?! [14:35] milestone testing :) [14:35] *snap* [14:36] I'm not so sure [14:36] if you look at http://poppy-dev.local/bucket/?id=%2Fusr%2Flib%2Fubiquity%2Fbin%2Fubiquity%3AValueError%3Awatch_debconf_fd_helper%3Aprocess_input%3Await%3Acleanup%3Apreseed%3A%3Clambda%3E%3Acommand [14:36] it's been pretty high for a few days [14:37] since the 25th [14:37] so surely that would make a longer spike [14:37] hmm, somehow my .local domain is different from yours :P [14:38] xnox, not nearly as many daily iso testers as beta 1 testers, that's all. [14:38] ogra_: :) [14:38] but milestone testing usually starts somewhere on the weekend and only ends on next thu ... [14:39] ev: what if you exclude ubiquity? (this is fiddling with numbers now) [14:39] xnox: exclude all ubiquity crashes? [14:39] yeah. [14:41] ev, the general increase in instances since the 23rd is (mostly) matched by an increase in error rate too, so I think that's just Feature and UI Freezes [14:41] ev: that ValueError was high since forever =) see my last merge proposal to ubiquity, hopefully it will fix that. [14:41] yeah, could be [14:41] xnox: excellent [14:42] ugh, how did I break the date range selection *again*? [14:42] ev, while you're there, use for the date fields :-) [14:43] ev: open a reverse port forward. There is a juju charm to do that using a cloud instance =) [14:43] oh, you already are [14:43] I did [14:43] yeah [14:43] I wonder why it isn't showing a calendar [14:43] because Firefox is a pile of rusted bolts [14:43] infinity, will you still merge clang and llvm-defaultgs? [14:44] xnox: will do [14:44] though it'd probably be more helpful to just deploy to canonistack [14:44] so bdmurray can see trunk [14:44] and whomever else wants to hack on this [14:44] true it can has public IP =) [14:49] smoser: shouldn't need any hacks that I can recall [14:50] How can I reset my compiz / unity settings back to default? I think some setting is causing compiz to crash and respawn repeatedly [14:51] bdmurray, unity --reset ? [14:51] (not sure that still exists) [14:51] ogra_: I think it does but wasn't sufficient [15:01] rumour has it --reset is broken [15:01] t's removed from trunk btw [15:02] yeah, it's useless since the gsettings migration [15:12] what's the preferred way to ping an archive admin to accept a package in -proposed? [15:13] For preference, ping one of ~ubuntu-sru instead [15:13] (I don't know) [15:14] cjwatson: ping. can you accept ncurses in oneiric-proposed? [15:14] it in the queue for 10 days [15:14] s/it/it's/ [15:15] I suppose I asked for that, but I'd rather one of the more regular SRU folks did it [15:15] hm, though it's easy [15:16] cjwatson: who belongs to the more regular SRU folks? [15:16] ubuntu-sru ? [15:16] bdrung: done now [15:17] I think there is a daily schedule somewhere for the ubuntu-sru team [15:17] ogra_: the question was, who of the nine ubuntu-sru members are the more active ones. [15:18] cjwatson: thanks [15:18] bdrung, indeed the one with the highest karma *g* [15:19] ogra_: the karma just tell you how active someone is, but not how active in one specific team ;) [15:19] details :P [15:22] bdrung: here it is https://wiki.ubuntu.com/SRUTeamProcess [15:22] skaet added a section about publishing the uploaded packages just some weeks ago. [15:23] bdmurray: thanks. that list appeared on https://wiki.ubuntu.com/StableReleaseUpdates too. rechecking wiki pages for updates sometimes help. ;) === orated_ is now known as orated [15:26] mvo, cjwatson: see bug #1048566, i386 only [15:26] Launchpad bug 1048566 in hwloc (Ubuntu) "[1.4.1-4] want to uninstall the whole system" [High,Triaged] https://launchpad.net/bugs/1048566 [15:27] doko: Thanks, I'll sort that out [15:28]