[00:12] great, new poppler upload obsoleting today's maint+1 work [00:21] Laney: yay thanks [00:21] doko: Heh, I was just complaining about that in #-release :P [00:53] Oh, thank god, I was worried we might go a whole month without a poppler ABI bump. [00:53] I wonder if maybe we should rename PlusOneMaint to PopplerAndEDSMaint. [00:53] just staff two people from -desktop for the team, there's not much to do for -foundations === cpg is now known as cpg|away [02:00] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Archive: Open | 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: TheMuso [02:17] Hello all, im helping to pull some data for Ubuntu Beta releases and have a very short survey up on google documents found here. https://docs.google.com/spreadsheet/viewform?formkey=dFdSTUgzREoyeFZNSWRHSjlXMGYteGc6MQ Anyone interested please take the survey and feel free to share the link. The results will be published in two weeks to the public domain. [02:19] needhelp1: could you publish some context (who you are; what it's for (eg. Thesis research, graphics design) [02:20] needhelp1: many people are unlikely to click random URLs, so you may end up missing out on results (but that depends on who your target audiences is, and we don't know that either!) [02:23] sladen, im a college student [02:23] sent you a pm also [02:35] nb ^^, there's more context at http://nathanheafner.com/home/2012/09/11/ubuntu-beta-users-survey/ [03:24] cjwatson: do you need another test from me ? [03:38] Good morning === cpg|away is now known as cpg [05:04] micahg: thanks. dannf reported a recent bug and we rebased on latest upstream release 1.2.0. an update package should be submitted soon. [05:57] @pilot out === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Archive: Open | 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: === charles__ is now known as Guest11727 === Guest11727 is now known as charles [06:55] good morning === tkamppeter_ is now known as tkamppeter [07:53] help [07:53] The following packages have unmet dependencies: [07:53] fglrx : Depends: xorg-video-abi-11 but it is not installable [07:53] Recommends: fglrx-amdcccle but it is not going to be installed [07:53] E: Unable to correct problems, you have held broken packages. [07:53] ? [07:54] rose7676: not much you can do right now -- current quantal fglrx driver is broken [07:54] you need to wait until a compatible one gets uploaded, and use the free one until then (do give it a try, it shoudl work well) [07:56] pitti, The following NEW packages will be installed: [07:56] fglrx-amdcccle nvidia-current-updates [07:56] 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. [07:56] Need to get 73.7 MB of archives. [07:56] After this operation, 215 MB of additional disk space will be [07:57] ????? nvidia-current-updates [07:58] mvo: ^ what was the magic again to ask apt to be verbose about dependency resolution? [07:58] rose7676: what did you try to do, dist-upgrade? [07:58] 12.04 [07:59] and 12.10 [08:01] pitti: -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::AutoInstall=true [08:01] pitti: I guess we should add a --debug-resolver shortcut actually [08:01] pitti: to make this more acessable [08:01] that'd be great === henrix_ is now known as henrix [08:10] can somebody please reject https://code.launchpad.net/~vpilvio/ubuntu/quantal/gpiv/typo-fix/+merge/123450? [08:11] shadeslayer, I'm not sure what to do with https://code.launchpad.net/~andreagrandi/ubuntu/quantal/kdevelop-custom-buildsystem/typo-fix/+merge/121225 [08:11] dholbach: done [08:12] thanks [08:12] ugh, I forgot about kdevelop .... it's in my PPA atm, need to include that fix [08:13] can I assign code reviews to myself? [08:13] hmm ... can't even subscribe myself [08:15] shadeslayer, I added you to it [08:15] thx [08:16] lifeless: nothing more to test right now; I tried to set up a simpler reproduction environment (just linear dmraid), but it passed; so I think this is specific to striped, and I need to remember how to set that up [08:22] mpt: we finally finished the deployment: https://errors.ubuntu.com/ [08:23] \o/ [08:23] I'm most annoyed by that unchecked-by-default teams checkbox [08:24] ... I see no checkbox [08:27] looks great [08:28] mpt: when you are thrown into the openid check [08:28] is there an explanation for the colors in the ranking table? [08:28] heh [08:28] * ev metaphorically bangs his head on the desk [08:29] geser, we're trying to work out how to do without one, but haven't succeeded yet. In the meantime: grey = not observed in the latest version, red = supposedly fixed but observed since. [08:29] dholbach: can I close branch merges with the changelog? [08:29] or is that only for boogs [08:30] shadeslayer, no, but you can mark it merged (or merge the branch via bzr and it should(?) get auto-merged) [08:30] ev, I just realized that if the default table is top errors for all Ubuntu users, eventually a majority may fall into the "not observed in the latest version" category, because they'll be in old releases but not the development release. Already it's 41/100. [08:31] hmm yeah [08:31] ev, I suppose that could be refined to "not observed in the latest version on the same release". [08:31] how would you do that though? [08:31] oh [08:31] dholbach: Actually, there's a new upstream bugfix release that I'm planning on uploading [08:32] cool [08:36] mpt: is it intended that the bug link doesn't point to the "master" bug for duplicated bugs? (like for the jockey-gtk entry at rank 11 which also points to a private bug where I first thought it was a broken link because I wasn't logged in into LP) [08:37] geser: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414 [08:37] Launchpad bug 764414 in apport (Ubuntu) "private master bugs are confusing and lead to more duplicate filings" [Wishlist,Triaged] [08:39] lifeless: in this case the master bug is public, but errors.u.c links to 927985 (which is private) instead of 734376 (master and public) [08:42] geser, I don't know how that part works, sorry, ask ev [08:43] geser: oh, thats interesting, and unusual. [08:43] doko_, just finishing up a rebuild test for java 7 - FTBFS now look much better but > 150 packages build bytecode for >= Java 7 only [08:44] dholbach: will be fixed once I QA everything from : https://launchpad.net/~rohangarg/+archive/experimental/+packages === henrix is now known as henrix_ === henrix_ is now known as henrix [08:46] geser: I'll look into it shortly [08:53] ev++ good deployment of errors, hunting some info down now. [08:53] xnox: cheers [09:47] geser: so the information for that comes from apport's crash-digger [10:07] infinity: so, the touchpad hotkey mess is due to acpi-support. /etc/acpi/asus-touchpad.sh gets triggered as well, and it can mess things up if it's a synaptics touchpad.. === mcclurmc_away is now known as mcclurmc [10:09] also, if you happen to have the touchpad disabled setting in g-s-d and boot the machine up, there is no user-friendly way to get the touchpad working again, since the properties are flip-flopped so it'll always be disabled (nice that synaptics has two properties to disable the device..) [10:10] g-s-d does the right thing [10:11] pitti: what happened to https://blueprints.launchpad.net/ubuntu/+spec/acpi-support-deprecation :) [10:12] tjaalton: I guess it died off at the last mile :( [10:12] yeah :/ [10:13] was wondering why one laptop with Alps worked fine, and the other with synaptics hit these weird issues, but it was because asus-touchpad.sh doesn't recognize Alps :) [10:18] hi [10:18] is it possible to track down why a video streams when it is not suppose to ? [10:19] I mean, figuring out what is working more than all the error messages [10:29] jamespage: just to double check, the packages you want in main in addition to those that already promoted are radosgw and python-ceph, right? [10:29] didrocks, yes please [10:29] jamespage: doing the promotion now [10:30] ta [10:30] yw :) [10:30] didrocks, BTW I just hit a bug in radosgw on armhf - bug 1049582 [10:30] Launchpad bug 1049582 in ceph (Ubuntu) "radosgw crash on armhf architecture" [Undecided,New] https://launchpad.net/bugs/1049582 [10:31] it works just fine on x86 - I will raise this with upstream today - have a call later on [10:35] jamespage: ok, I don't block on that then, trusting you to keep track :) promoted === Phantomas1 is now known as Phantomas [10:35] jamespage: btw, looking at the python-ceph package, it can certainbly be arch: all (if you have another upload to do) [10:36] but no hurry :) [10:36] didrocks, ack [10:36] I'll put that on my list TODO [10:37] thanks === glebihan_ is now known as glebihan === doko_ is now known as doko === cpg is now known as cpg|away [10:58] jamespage, you did disable the openvswitch-datapath-dkms package in openvswitch, however xcp-networkd still depends on it. should the dependency just dropped? [10:59] doko, I did because its broken in quantal; however I think zul was looking at fixing it up again to work with the 3.5 kernel [11:00] jamespage, could you track this? it shows up in NBS [11:00] its provided by the kernel; so thats probably a reasonable course of action if we can't ressurect this [11:00] doko, sure - leave it with me [11:00] thanks [11:19] janimo, ping [11:19] doko, hi === MacSlow is now known as MacSlow|lunch === Quintasan_ is now known as Quintasan [11:58] jamespage, the 150 bytecode for 7 packages are no good. I assume these are all packages which don't use one of the helper tools for the build? [11:59] doko, I suspect so - maven stuff will be OK; javahelper to [11:59] they will probably all be ant/Make custom builds [11:59] doko, I have the list - will be raising bugs soon [11:59] like today [12:00] is there already a lintian check? [12:05] doko, yes - and experimental one "incompatible-java-bytecode-format" - thats what I've been checking for [12:08] doko, http://paste.ubuntu.com/1200436/ === MacSlow|lunch is now known as MacSlow [12:16] jamespage, sort by source/component would be nice [12:17] I think about 7 of those are in main [12:17] I will do that - just trying to finish something else first === _salem is now known as salem_ === Quintasan_ is now known as Quintasan === sagaci_ is now known as sagaci [13:08] meh - if there is one package that really benefits from -proposed uploads, it's eglibc.. [13:10] too late [13:10] didrocks: Hi, I don't understand why you marked bug 1040839 'Fix Released'. You comment makes it sound like it should be marked "WontFix". [13:10] Launchpad bug 1040839 in thunderbird-couchdb (Ubuntu Quantal) "Thunderbird hangs accessing eds on startup" [High,Fix released] https://launchpad.net/bugs/1040839 [13:13] smagoun: the hanging was because the protocols don't match, so it's either updating the API or removing the component (that is not supported) [13:13] smagoun: more a semantic discussion, if you prefer to set it won't fix, please do :) [13:14] didrocks: right. Have either of those changes happened in Q? If not, the fix is not released [13:14] It's a pretty bad bug....IMHO we at least need to remove thunderbird-couchdb [13:14] smagoun: that's what I did and hence I changed the status [13:15] cant you just add a Breaks: <= libedataserver-1.2-15 to thunderbird-couchdb ? [13:15] so that they cant be installed together [13:15] ogra_: well, there is no more upstream for it, nobody will maintain it and port to the new API [13:15] (which is quite an extensive change) [13:16] oh, you mean tb-couchdb [13:16] yep [13:16] didrocks: So thunderbird-couchdb will be removed during an upgrade from 12.04-12.10? That is good. It wasn't clear from your comment that you made that change [13:16] ah [13:16] will removing it from the archive guarantee that it's removed on upgrade? [13:16] smagoun: yeah, sorry, it will when people choose "remove obsolete packages" as part of the update-manager process [13:17] didrocks, hmmm, we probably want to guarantee that it gets removed [13:17] chrisccoulson: you can add a breaks to ensure people using apt-get dist-upgrade to have that done [13:17] s/to// [13:17] yeah, i don't mind [13:18] I think it will be best :) [13:19] +1 for guaranteeing removal === cjohnston_ is now known as cjohnston [14:02] Can someone tell me which channel is/are the best on fixing bugs, I need it to write Ubuntu Accomplishments [14:05] mterry: lightdm-set-defaults doesn't work as expected with your patch: show_remote_login is TRUE in lightdm by default but FALSE in lightdm-set-defaults [14:06] mr_pouit, ah, so it sets remote to false too easily? [14:06] mterry: also, lightdm-set-defaults --keep-old --show_remote_login=false/true doesn't do anything [14:07] mr_pouit, regarding the false-by-default in set-defaults, I thought set-defaults doesn't set anything unless it's specified by user? [14:09] mterry: yeah, my first statement is probably wrong because of the second one: --keep-old and --remove don't do anything with --show-remote-login (lightdm.cinf is never updated) [14:10] mr_pouit, is it broken with manual-login too? (I cargo-culted the manual login treatment, so I'm curious if this is a general error or something I did) [14:14] can someone make https://bugs.launchpad.net/bugs/1026164 public? [14:14] Error: malone bug 1026164 not found [14:14] i just got thrown there when trying to report a bg [14:15] tedg: please get someone to fix LP: #1049849 [14:16] bug 1049849 [14:16] Launchpad bug 1049849 in lightdm (Ubuntu) ""Remote Login" account not confined by guest AppArmor profile" [Undecided,New] https://launchpad.net/bugs/1049849 [14:16] mdeslaur, Okay, how do I test that? [14:16] tedg: hold on, I'll add steps to reproduce in the bug [14:18] mdeslaur, Thanks! [14:21] tedg: ok, steps added. thanks! [14:26] mterry: it's a general error for booleans apparently (update_boolean() doesn't do what's needed compared to update_string()) [14:28] mr_pouit, yeah, good point. It's noticably not caring whether an existing value is there [14:29] thanks xnox for replying to that tweet [14:29] dholbach: your welcome. It's not "true" LDAP integration, but it does at least work these days. [14:30] great [14:30] thanks [14:56] anyone aware of this: http://paste.ubuntu.com/1200691/ [14:56] python-twisted is currently uninstallable [14:57] doko, you apparently copied that from debian recently? [15:00] smoser, working on it [15:01] thank you. [15:05] slangasek: Bug #1049840 is broke since precise-updates is higher than quantal for nspr [15:05] Launchpad bug 1049840 in ia32-libs (Ubuntu Quantal) "ia32-libs-multiarch wrong dependancies on quantal 64bit" [Undecided,Incomplete] https://launchpad.net/bugs/1049840 [15:06] micahg: should that be a pocket copy? [15:06] idk, I haven't reviewed the changes [15:06] either a pocket copy or a no change rebuild if the changes don't apply [15:09] hrm, either way it should probably be rebuilt on quantal though [15:12] slangasek: looks like no change rebuild is the way to go, are you already doing it, or should I? [15:14] micahg: I'm uploading [15:14] ok, thanks === ken__ is now known as kenvandine === dpm is now known as dpm-afk [15:46] tjaalton: *poke* [15:47] infinity: *dodge* [15:47] tjaalton: Feel an urge to limit intel-gpu-tools to "amd64 i386"? [15:48] infinity: probably makes sense [15:48] (I was about to do that for the Ubuntu package, and noticed you're just releasing from Debian git anyway) [15:48] tjaalton: "any-amd64 any-i386" might also make sense, except that it doesn't appear to love non-linux arches anyway, from what the Debian build logs are showing me. [15:49] tjaalton: So, yeah, "amd64 i386" is probably right. [15:49] yeah I'll add just those [15:49] tjaalton: Danke. [15:52] infinity: dunno if you saw, but the hotkey issue was with acpi-support. bug 804109 has the details [15:52] Launchpad bug 804109 in acpi-support (Ubuntu) "remove/edit racy /etc/acpi/asus-touchpad.sh" [Medium,Triaged] https://launchpad.net/bugs/804109 [15:52] tjaalton: Fun, fun. [15:53] it shouldn't do anything for synaptics devices, ok to keep the hack for evdev using touchpads until g-s-d handles them === jacky is now known as jalcine [15:55] tjaalton: Maybe I'll fix it (the intel-gpu-tools thing) in Ubuntu right now for my own sanity on the FTBFS/dep-wait list, and you can just commit to Debian git later. [15:57] I've done the commit already [15:57] and merge [15:58] slangasek, ping [15:58] uploaded too :) [15:58] tjaalton: Oh, shiny. Thanks. [16:02] slangasek, ever have one of those days with a package? I can't seem to get samba right [16:02] so --upstart-only should only be used when the upstart configuration is NOT replacing a init script with the same name? [16:03] I did not get that from the man page [16:04] smoser: hey there [16:04] jamespage: correct - sorry for the bad documentation :) [16:05] slangasek, i'll get you access to a system to poke around if you dont mind [16:05] for bug 1031065 [16:05] Launchpad bug 1031065 in cloud-init (Ubuntu) "cloud-init-nonet runs 'start networking' explicitly" [Medium,Triaged] https://launchpad.net/bugs/1031065 [16:05] * jamespage goes todo another samba upload [16:05] jamespage: in a cycle or two it'll be obsolete anyway [16:05] smoser: I have very little time to look at it right now due to the management sprint, but if you can give me a system that'll be up for a few days that I can poke at when I get a chance, that'd be great [16:05] sure [16:06] i'll send you info [16:06] well actually that will be tomorrow now... [16:10] hit bug 983543 while trying to dist-upgrade to quantal [16:10] Launchpad bug 983543 in eglibc (Ubuntu) "Internal Error, No file name for libc6" [Undecided,Confirmed] https://launchpad.net/bugs/983543 [16:23] mpt, bdmurray: so we don't have a "link to an existing bug" link [16:23] as bdmurray has noticed [16:23] I'm wondering if we can get away with just telling people to dup whatever they've done to the errors created bug [16:23] tjaalton: Hrm. I've seen that once (thought it was libstdc++, not libc) on an aborted upgrade. Rest of the system was fine, apt was in a tizzy. Not entirely sure where to reassign it, or even how to reproduce it (and almost certain it's not glibc's fault). [16:24] tjaalton: If you have any meaningful way to actually make it happen reliably, I'd love a reproducer. [16:24] or if we need to provide a pair of "create / link to existing" links [16:24] infinity: yeah it's misfiled [16:24] ev, I can suggest how to present either of those, but which one of them to do is out of my ambit [16:24] ev: well we need a link that takes it to ~ page as apport does where you can search or file new. [16:25] ev: that doesn't help with linking up though =( [16:25] ev, because I don't know how noisy auto-generated bug reports would be. [16:25] (And therefore how good an idea it is to auto-generate them.) [16:25] ev: there is also the issue regarding traceback and line numbers for source code changing. so there may already be an existing bug in launchpad just with different line numbers that is already triaged / assigned/ fixed. [16:25] xnox: please rephrase - I don't follow [16:26] mpt: you indirectly raise an interesting point [16:26] and marking that as a duplicate of the errors created bug seems less efficient [16:26] we're going to be autogenerating bugs for the top X crashes [16:26] I've never really understood how I'm supposed to take an existing errors report and arrange for there to be a bug for it, if I'm not actually encountering it myself [16:26] so how does that play in? Are they just forced to dup when one exists, but provided with a "create / link" links otherwise? [16:26] I don't know about the linking bit, but I would find a creation-on-request facility extremely helpful [16:26] cjwatson: that just landed - there are "create" links in the bug columns [16:26] as of today [16:27] it wont show up for failed to retrace bugs - marked with "failed:" on the front of the signature [16:27] Ah [16:27] There are no create links in the page I have loaded [16:28] But trying to write 40GB to USB means my entire system is rather slow so it's hard to chec [16:28] k [16:28] Oh yes, I see them now, thanks [16:28] ev: I'm talking about bug 1048830 [16:28] Launchpad bug 1048830 in Errors "error report without a bug link" [Undecided,New] https://launchpad.net/bugs/1048830 [16:29] So I'm interested in the logic of not presenting that for failed-to-retrace bugs [16:29] Because that implies you (consciously or otherwise) think developers can't do anything about them [16:29] cjwatson: I do === deryck is now known as deryck[lunch] [16:29] ev, I don't see the "create" links -- is that because I'm not in the appropriate team? [16:29] Which raises the question of why we're bothering to show them [16:29] (not that I want to be) [16:30] cjwatson: to raise awareness of how much we need to fix ddebs [16:30] ev: But that isn't true, I've certainly fixed failed-to-retrace bugs in the past because the problem was obvious from the top of the stacktrace [16:30] and how much I need to feed things back through the retracer [16:30] This is an invalid assumption [16:30] cjwatson: fair enough [16:30] it's somewhat complex to fix === dpm-afk is now known as dpm [16:30] Now admittedly it's a hell of a lot easier with a stacktrace, but ... [16:30] as if we do work out a process to feed things back through the retracer [16:30] we'll need to clean up the bug links too [16:31] Yes, true [16:31] and we might have multiple stacktrace address signatures with "failed:" on the front [16:31] that map to a single crash signature [16:31] and need some way of determining which bug is the master - or just dup them all to it [16:31] * ev digs up the bug number for this re-retracing [16:31] I'm certainly *aware* of how much we need to fix ddebs, but realistically I think the answer is more LP development time in UE [16:31] cjwatson: https://bugs.launchpad.net/daisy/+bug/1044418 [16:32] Yeah, I know what you mean [16:32] cjwatson: oh absolutely [16:32] Launchpad bug 1044418 in Daisy "Reprocess failed retraces" [Undecided,New] [16:32] and it's as much to remind me as anything else [16:32] I have no doubt that I'll have to play a role in fixing it [16:32] I just want to make sure I'm reminded of the importance of this vs starting up other subprojects on errors [16:33] if we can't see the failed to retrace crashes, then the problem might as well not exist to me [16:33] (it actually used to be this way) [16:33] but I grew worried that it wasn't clear that this was not the entire picture [16:33] at the very least I need to better tag them as such [16:33] as people easily miss "failed:" in the signature [16:34] and I don't mean by putting more text in that line [16:34] Numbers on Ubuntu-specific vs. not in the last day of 12.10 error reports: about 70% Ubuntu-specific vs. 30% not [16:34] hmm? [16:34] Of course that probably needs to be compared with usage to be meaningful [16:34] Sorry, I mean on Ubuntu-specific packages [16:34] oh, vs debian? [16:35] mpt: you're not signed in [16:35] No, as in 70% of reports from the top 100 were in packages developed specifically for Ubuntu [16:35] mpt: you need to click off to a problem page first [16:35] mpt: feel free to provide UI for a login link or a better approach for this [16:35] ahhh [16:35] go us [16:35] ev: go us.... *sigh* [16:36] cjwatson: I'm entirely happy with being proven wrong on all my points, so long as it's done using data as you've done here :) [16:36] This was roughly my point in the meeting - it suggests that fixing our own problems should be the priority, not worrying about the long tail which is basically absent from errors [16:36] cjwatson: indeed [16:36] that whole thing went off the rails [16:36] I just want us to focus on QA in the immediate moment [16:37] It's probably a bit different for different time periods, but it's unfortunately laborious to count [16:37] not go, "oh, well we're not at feature freeze yet, we can fix this later" [16:37] and never do [16:37] because it's not a LTS [16:37] I don't think that's really what people were saying as such, but anyway [16:37] cjwatson: we do have an API for this... [16:37] ev: Not for "was this package developed specifically for Ubuntu?" [16:38] oh indeed not [16:38] sorry about that [16:38] so before we get too sidetracked [16:39] bug links [16:39] we currently provide create bug links [16:39] do we also provide the ability to manually enter a number [16:39] rather than one being autocreated [16:39] err in addition to [16:39] if one is not already set, that is [16:39] or [16:40] do we rely on duping to the errors created bug [16:40] I say yes and provide bug 1048830 as a reason why [16:40] Launchpad bug 1048830 in Errors "error report without a bug link" [Undecided,New] https://launchpad.net/bugs/1048830 [16:40] and https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fshare%2Fapport%2Fapport-gtk%3Aconfigparser.DuplicateOptionError%3A%3Cmodule%3E%3Arun_argv%3Arun_crashes%3Arun_crash%3Aui_present_report_details%3Aget_desktop_entry%3Aread%3A_read which should be linked to bug 1048834 [16:40] Launchpad bug 1048834 in indicator-datetime (Ubuntu Quantal) "configparser crash with indicator-datetime-preferences.desktop" [Medium,Fix released] https://launchpad.net/bugs/1048834 [16:41] both of the bugs that I would linke to are already fixed or have lots of work done on them [16:41] and duping those bugs to one created by errors seems silly [16:41] so are these generating different signatures? [16:42] barry: Any progress on bug 1035869? I noticed it showing up on errors [16:42] Launchpad bug 1035869 in computer-janitor (Ubuntu) "computer-janitor crashed with ImportError in /usr/share/computerjanitor/computerjanitord/errors.py: No module named computerjanitor" [High,Triaged] https://launchpad.net/bugs/1035869 [16:43] ev: the tracebacks for the software-properties-gtk bug have different signatures yes because the line number in the source code changed [16:43] bdmurray: I'm really weary of moving to launchpad bugs to manage the linkage between problems [16:44] so I'm wondering if we should instead make it possible to merge problems together in the database [16:45] or maybe a combination of the two [16:45] People still use computer-janitor? Wow. [16:45] that's unfortunate for them [16:45] bdmurray: sorry - I know that's really vague [16:46] my brain is somewhat melted after the meeting [16:46] but suddenly keying the problems we're seeing on something other than the crash signature would be a massive change [16:46] and indeed, something external to the database [16:47] but now we have errors listed that are fixed and don't require more work [16:47] well they're not fixed [16:47] if they were fixed they wouldn't be appearing [16:48] Or they're multiple bugs with the same signature [16:52] I kind of think this goes into the server-side hooks [16:53] we should be able to write code that says, when encountering a signature with data in the report that matches this pattern, put it in this bucket instead [16:53] rather than just into a bucket IDed by the regular crash signature === mcclurmc is now known as mcclurmc_away [16:56] like bugpatterns but for errors.u.c [16:56] micahg: right, we're moving all that server side [16:56] https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-bucketing-improvements [16:57] I don't think that sort of thing should be pushed via apt or include lots of silly "choose a door for punishment" dialogs === jtechidna is now known as JontheEchidna [17:05] mpt: thanks to askubuntu.com I now can have rounded corners & joined up buttons with transparent background http://askubuntu.com/questions/185284/how-to-get-rid-of-the-background-gradient-of-the-inline-gtktoolbar/187039#187039 [17:06] win [17:06] mpt: I had to spend 500 askubuntu reputation points, as only the bounty attracted answers.... [17:07] pitti: can you explain the giant upload of translations into the precise-proposed queue? Are we just supposed to wave those through? [17:07] slangasek: ^^ [17:07] cjwatson: ^^ [17:07] * SpamapS hoping one of those 3 minds will have the answer [17:08] * SpamapS also hoping to clear it up on https://wiki.ubuntu.com/ArchiveAdministration once he knows [17:09] SpamapS: I was about to mass-accept them. [17:09] * xnox wonders if SpamapS has to click tickboxes 400 times [17:09] * SpamapS will pay $0.01/click .. ;) [17:11] SpamapS: (accepting now) [17:15] Anyone here happen to be an expert in dmraid? [17:15] I'm trying to re-create Robert's setup in bug 803658 in a VM, using dmraid -C [17:15] Launchpad bug 803658 in grub2 (Ubuntu) "grub-install /dev/mapper/isw_$UUID_$NAME0 failing with ICH10R raid 1+0" [High,Fix released] https://launchpad.net/bugs/803658 [17:15] cjwatson: not yet, but i have a browser tab open on it :/ [17:16] I'm using variations on 'dmraid -f isw -C ARRAY0 --type 01 --disk /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd' [17:16] This ostensibly succeeds, and indeed (reasonably) complains if I give it fewer than four disks [17:17] However, it's evidently written garbage, because 'dmraid -ay' says 'ERROR: isw: wrong number of devices in RAID set "isw_cjehcgig_ARRAY0-1" [4/2] on /dev/sda' (and so on for the other three disks) [17:17] infinity: ok, thanks. So to confirm, thats always just a wave-through? [17:17] SpamapS: To -proposed, yes. There's some level of verification that happens before they get to migrate. === dpm is now known as dpm-afk === deryck[lunch] is now known as deryck [17:53] hallyn, maybe this is expected. [17:53] but i do an lxc-clone -o source -n new [17:53] and new has in its config a reference to source's fstab [17:54] smoser: no that's a bug [17:56] after dist-upgrade, dnsmasq was listening on 127.0.1.1 but resolv.conf points to 127.0.0.1 === henrix is now known as henrix_ [18:01] barry: reading through the discussion on http://bugs.python.org/issue15906 ... oh what fun! [18:03] cjohnston, Hi Colin, what version of live-build do you use for precise/quantal builds? I'e been fiddling with it and run into issues even with a vanilla build [18:03] :-( [18:03] smoser: well, actually, i'm not 100% sure [18:03] iamfuzz: You wanted cjwatson. ;) [18:03] smoser: i think it was left like that for now bc there's a limit to what we can do [18:03] iamfuzz: And we use the version that's in the archive for each release. [18:04] tab failure ftw [18:04] cyphermox, ^ i think you helped me with issues like tjaalton has [18:04] hallyn, really? [18:04] infinity, interesting, I had to patch the one in precise just to get it to build anything [18:04] live-build | 3.0~a24-1ubuntu32.5 | precise-updates | source, all [18:04] live-build | 3.0~a57-1ubuntu4 | quantal | source, all [18:04] i.e. if we copy over the fstab, then do we also process it? but if we do that, then we may have to copy over the direcotires mounted in the fstab [18:04] trying quantal now [18:05] iamfuzz: It might help to realise that we use the auto/{config,build} scripts from livecd-rootfs (also from the appropriate release). [18:05] smoser: i'd almost want to say 'if anything is in there other than proc and sys, refuse' [18:05] infinity, many thanks, I'll take a look at that, I had been generating mine with lb config [18:05] stgraber: ^ did you ahve thoughts on handling of /var/lib/lxc/c1/fstab when it's being cloned? [18:06] hallyn, sorry [18:06] bad explanation [18:06] $ grep $SRCNAME /var/lib/lxc/xm/config [18:06] lxc.mount = /var/lib/lxc/source-quantal-amd64/fstab [18:06] err.. [18:07] well, i didn't mean to paste that [18:07] SpamapS: indeed! i think we've converged on a plan though, and i'll be landing a followup patch in 2.7, 3.2, and 3.3.1 (won't affect 3.3.0) as soon as the test suites finish [18:07] but, that is what i opened a bug about [18:07]