[01:04] <xorgnak> woud anyone know what the discover1 package has been moved to for 10.10?
[01:07] <xorgnak> nevermind... if anyone's curious for remixes, discover1 has been depreciated to discover
[01:14] <slangasek> SpamapS: hi; still around?
[01:29] <r3d2> hey you guys. i just downloaded my first source code so i can get an idea of how linux programs are written....i picked a relatively small program, mousepad. and after i "sudo apt-get source mousepad" it seems like everything worked out
[01:29] <r3d2> but now i have 1 folder and 3 files for it
[01:30] <r3d2> mousepad.diff.gz mousepad.tarr.gs and mousepad.dsc
[01:30] <r3d2> what are all those?
[01:31] <RAOF> mousepad.dsc is some metadata about the source package, mousepad.diff.gz is the difference between the upstream source and the Ubuntu source package, and mousepad.orig.tar.gz is the original source.
[01:31] <r3d2> ah nice
[01:31] <r3d2> thank you
[01:31] <r3d2> that explains it all lol
[04:45] <YokoZar> what are the ways that Universe might be unchecked?
[04:45] <YokoZar> Is there an option at install, for instance?
[04:49]  * micahg thought it was disabled by default
[05:05] <vish> there is an option during which enables the restricted and multiverse repos but as micahg says nothing enables universe until user selects it
[07:21] <pitti> Good morning
[07:23] <pitti> cody-somerville: no, it isn't; apport doesn't use notifications at all; also, web browser should be opened as user indeed
[07:24] <cody-somerville> pitti, if you click links in dialogues, they open as root
[07:24] <cody-somerville> pitti, for example, the link to trying out upstream kernel
[07:24] <pitti> cody-somerville: you mean in the kernel dialogs?
[07:25] <pitti> right, that's GTK itself
[07:25] <pitti> perhaps there's a way I can override the default URL handler in GTK
[07:25] <pitti> when apport opens the browser for bug filing, it uses some tricks to go "back" to the user's account
[07:26]  * cody-somerville nods.
[07:30] <alkisg> Hi, can someone re-open LP bug #580961, as it's not fixed yet?
[07:32] <maco> alkisg: you tried it with version 6.0-4ubuntu1 in 11.04 alpha 2?
[07:33] <alkisg> maco: yes, I posted why it's broken in the bug report
[07:33] <alkisg> It looks like part of the patch is missing
[07:34] <maco> alkisg: ok, reverted to triaged
[07:35] <maco> or well...as soon as my web browser goes as bit faster....
[07:36] <alkisg> Thank you. To clarify, it's still not working, i.e. a regression from previous Ubuntu versions, I'm not asking for anything new like autodetection (like others in that bug report do ask).
[07:39] <dholbach> good morning!
[08:06] <didrocks> good morning
[08:09] <pitti> hey dholbach, bonjour didrocks
[08:12] <didrocks> hey pitti
[08:23] <dholbach> hey pitti
[08:23] <kklimonda> jdstrand: btw, the other thing you thought I was talking about is still important, but it just wasn't as important to me ;)
[08:39] <cjwatson> vish: not true, universe has been enabled by default since feisty
[08:39] <cjwatson> (not on the live CD though, but in installs)
[09:00] <vish> cjwatson: odd.. the last time i installed with natty cd it made me choose universe to install banshee..
[09:00]  * vish will check but trusts cjwatson more ;)
[09:03] <seb128> hum
[09:03] <seb128> does anybody has any clue about bug #717516?
[09:04] <seb128> slangasek, pitti, cjwatson: ^ not sure who is tracking plymouth issues nowadays, seems something to check but I'm not sure what to ask on the bug
[09:05] <cjwatson> there was a plymouth bug that soren fixed yesterday
[09:05] <cjwatson> haven't actually read that report but make sure that the user isn't using plymouth 0.8.2-2ubuntu15 or 0.8.2-2ubuntu16
[09:05] <seb128> cjwatson, he says he still get the issue on 17 in the bug
[09:06] <cjwatson> soren: did you commit your patch anywhere?  I don't see it in lp:ubuntu/plymouth
[09:12] <seb128> cjwatson, thanks, I've added a comment pointing to the bug fixed in ubuntu17 and asked some details
[09:15] <Riddell> @pilot in
[09:15] <pitti> whee, Scottish airpatchlines!
[09:17]  * dholbach hugs Riddell
[09:34] <apw> cjwatson, can you remind me  when we enabled the grub graphical handoff at the grub level?  was that after A1 ?
[09:35] <cjwatson> apw: Wed, 24 Nov 2010 13:59:55 +0000
[10:24] <soren> cjwatson: Gah, sorry.
[10:24] <soren> cjwatson: I wanted to wait until it was accepted into the archive, but got sidetracked.
[10:25] <soren> cjwatson: Pushed.
[10:31] <seb128> dholbach, did someone point already that the sponsoring queue have wrong urls for merge requests today?
[10:31] <dholbach> seb128, no, not yet
[10:31] <seb128> dholbach, it has api.launchpad.net/1.0/.... instead of "code.launchpad.net"
[10:31] <dholbach> ah yes
[10:32] <seb128> dholbach, it's likely a side effect of the fix they did yesterday after breaking things still using "edge" in their code
[10:32] <seb128> dholbach, you should probably port your code to use "production" rather than edge
[10:32] <seb128> should be trivial
[10:32] <dholbach> yes part of it was, yesterday
[10:32] <seb128> dholbach, well yesterday it just crashed, they did online patching to fix the redirect
[10:32] <seb128> but seems it's not perfect
[10:33] <dholbach> yes, I know
[10:33] <dholbach> working on it
[10:33] <seb128> dholbach, danke
[10:33] <dholbach> that's why I said "part"
[10:33] <seb128> ;-)
[10:34] <dholbach> nice, bdrung already fixed it
[10:34] <dholbach> seb128, should be fixed with next cron run
[10:35] <seb128> dholbach, excellent
[10:35] <seb128> bdrung, dholbach: thanks
[10:53] <Riddell> zul: python-django-nova packaging is GPL 2, I think canonical policy is for GPL 3
[10:54] <Riddell> zul: I've accepted but you should check that
[10:54] <soren> \o/
[11:17] <\sh> moins
[11:23] <siretart> hi \sh!
[11:30] <\sh> hey siretart...how's life?
[11:30] <siretart> \sh: not too bad, a bit stressful, but otherwise making progress. how are you and family?
[11:31] <nigelb> g40
[11:31] <nigelb> ugh, sorry
[11:35] <\sh> siretart: fine..wife is waiting in belgium, that our nice and nephew are born...and I'm still at KA and merging from netviewer to citrix online ;)
[11:36] <siretart> \sh: :-)
[11:36] <\sh> siretart: means our company just reported the closing of the deal between citrix and netviewer ;) so we are now a 100% division of them ;)
[11:38] <siretart> wow. does this relate in any way to your dc^2 project?
[11:39] <\sh> siretart: dunno...but I still have some weeks of time to think about staying with this company or to change to another company or to just leave all that behind and become self-employed (or in the worst case, hartz IV ;))
[11:40] <siretart> \sh: don't make (bad) jokes about that
[11:41] <siretart> \sh: but while I have you here, is there some installation guide or something available for dc2? I'm considering to deploy it.
[11:41] <\sh> siretart: no..I mean that...well, I have some nice job proposals
[11:41] <siretart> :-)
[11:42] <\sh> siretart: nope...but I can guide you if you want...I have to push another branch to trunk to make especially the qooxdoo frontend more usable with self deployed installations
[11:43] <\sh> and there are two other branches to switch dc² from mysql to couchdb, and to integrate some amazon ec2 management to it...it's still work in progress but hey :)
[11:43] <siretart> sure, I imagine. for a starter, the precise installation requirements would help me
[11:44] <siretart> but perhaps we should move that to a more appropriate channel ;-)
[11:44] <\sh> siretart: #dc2 ;)
[11:44] <siretart> oftc or freenode?
[11:44] <\sh> freenode
[12:15] <Riddell> cjwatson: thanks for fixing bug 705917 :)
[12:20] <cjwatson> np
[13:21] <zyga> doko_, ping
[13:31] <MadCow108> hi, when I want to backport a bugfix in a debian native package (format 3) for ubuntu, do I still use the debian/patches method or do I just directly patch the source as I would do it for debian?
[13:33] <MadCow108> the former would additionally require to add quilt to the build depends
[13:34] <cjwatson> er, a *native* package?
[13:35] <cjwatson> what does 'cat debian/source/format' say?
[13:35] <pitti> MadCow108: I'd apply inline for native packages
[13:35] <cjwatson> Debian and Ubuntu are just the same in this regard, but your question is confusingly phrased in a way which makes me think one of us is misunderstanding something
[13:36] <pitti> ITHM "3.0 (native)"?
[13:36] <MadCow108> 3.0 (native)
[13:36] <cjwatson> it's not clear, that's why I asked
[13:36] <hallyn> anyone else seeing garbled gnome-terminal text with 2.6.38-3 ?
[13:36] <cjwatson> you don't use the debian/patches method in either Debian or Ubuntu for native packages
[13:36] <cjwatson> you apply it inline, and there is no need to build-depend on quilt
[13:36]  * hallyn figures kirkland will chime in
[13:36] <MadCow108> ok
[13:36] <cjwatson> because you wouldn't be using quilt
[13:37] <MadCow108> I was just wondering as the qult method would make it a bit easier to see the differences between the debian and ubuntu version
[13:37] <cjwatson> you can see that by just diffing the packages
[13:37] <cjwatson> but no, that would involve changing from native to quilt format and we try hard not to make that sort of fundamental change to a package's format in Ubuntu
[13:37] <MadCow108> ok thanks
[13:38] <Riddell> mvo: are you going to update natty for bug 556189 ?
[13:40] <mvo> Riddell: this is just a stale status, I fix that
[13:41] <doko_> zyga: pong
[13:42] <zyga> doko_, who should I ask to debug stale pymodules cache?
[13:44] <doko_> zyga: either barry or me. could you be a bit more specific?
[13:44] <zyga> doko_, drop in to #ubuntuone please
[13:49] <zyga> doko, ralsina and me are trying to understand and debug something that seems to be stale cache of pyc files after an older installation
[13:49] <zyga> doko_, we'll file a bug and I'll ping you about it if you don't mind
[13:51] <tumbleweed> zyga: which package? It's quite possible that there are stayle .pyc files in the python path, if it was uploaded inbetween python2.7 support and python-support being updated
[13:51] <zyga> tumbleweed, this is still on maverick, and seems to be reproducible
[13:52] <zyga> tumbleweed, ralsina on #ubuntone understands more
[14:07] <asac> didrocks: master ... how painful is it to backport the current unity stuff to maverick?
[14:07] <asac> or are you guys actually maintaining a backport somewhereß
[14:07] <asac> ?
[14:07] <didrocks> asac: we stopped backporting it because it's really painful
[14:08] <didrocks> asac: you need to backport compiz and all plugins + a lot of package from the unity and appmenu world
[14:08] <didrocks> and soon, you will need the latest glib
[14:08] <asac> grr
[14:08] <asac> why are folks always jumping on the latest crack :)
[14:09] <didrocks> asac: yeah, people are crazy… :)
[14:15] <sebner> asac: because old stuff is boring ;)
[14:17] <asac> its really dog style of development ;)
[14:56] <kirkland> hallyn: kirkland reading scrollback
[14:57] <kirkland> hallyn: garbled terminal text?  no....
[15:21] <ogra> could an archive admin promote unity-2d, libqtgconf, libqtbamf and libqtdee to main ? (MIR bugs are bug #708649, bug: #708661, bug: #708659 and bug: #708658
[15:47] <pitti> ogra: yup, doing
[15:48]  * ogra hugs pitti
[15:48] <pitti> kein Problem :) *hug*
[16:08] <kirkland> pitti: hey
[16:09] <pitti> kirkland: hey Dustin, how are you?
[16:09] <kirkland> pitti: fine thanks :-)
[16:09] <kirkland> pitti: okay, so ecryptfs-utils version in lucid and maverick were identical, hence that upload was rejected
[16:09] <kirkland> pitti: how does this look:
[16:09] <kirkland> ecryptfs-utils (83-0ubuntu3.1-maverick) maverick-proposed; urgency=low
[16:10] <pitti> kirkland: ah, usually we do somehting like x.10.04 and x.10.10, but as we already have lucid, "3.1maverick" works
[16:10] <pitti> kirkland: no dash, please, as this is the separator of upstream-revision
[16:10] <kirkland> pitti: cool
[16:10] <kirkland> ecryptfs-utils (83-0ubuntu3.1maverick) maverick-proposed; urgency=low
[16:10] <kirkland> pitti: done;  re-uploading now
[16:10] <pitti> kirkland: thanks!
[16:11] <kirkland> pitti: done
[16:11] <kirkland> pitti: thanks, mate!
[16:32] <smoser> geser, bug 715818 is fixed.
[16:32] <geser> smoser: thanks
[16:32] <smoser> thank you for your help. I irresponsibly failed to credit you in changelog. for that i am sorry.
[16:32] <geser> np
[16:35] <Riddell> mterry: could bug 676512 get some MIR assignment love?
[16:35] <mterry> Riddell, I'll check
[17:34] <ogra> pitti, hmm, unity-2d doesnt show up in main yet
[17:34] <ogra> (netbook-meta update tells me its unknown)
[17:35]  * ogra thinks after 
[17:35] <ogra> 3h it should be there
[17:36] <ogra> oh, its only 2h
[17:54] <RoAkSoAx> stgraber: http://iso.qa.ubuntu.com/qatracker/dllist is empty and there are ISO's available in the tracker
[17:54] <RoAkSoAx> any ideas why?
[17:56] <stgraber> RoAkSoAx: that's weird, let me check
[17:57] <stgraber> RoAkSoAx: http://iso.qa.ubuntu.com/qatracker/info/5015
[17:57] <stgraber> RoAkSoAx: seems to happen with all the builds
[17:58] <stgraber> so dllist doesn't return anything as it can't get the info from cdimage
[17:59] <stgraber> RoAkSoAx: I guess that the current magic to find the right file on cdimage doesn't cover the point releases
[17:59] <RoAkSoAx> stgraber: ah I see
[18:00] <stgraber> marjo: ^
[18:16] <RoAkSoAx> Riddell: till what time are you piloting?
[18:28] <Riddell> RoAkSoAx: until I sign off :)
[18:32] <RoAkSoAx> Riddell: lol ok :)/. Let me know cause I'm up next :)
[18:33] <Riddell> RoAkSoAx: oh you can add yourself too I'm sure
[18:33] <Riddell> just do @pilot in
[18:38] <gaurav_pawaskar> hi people, I want to know.. when bug is raised .. how do we identify, which all packages are related to that bug?
[18:39] <RoAkSoAx> @pilot in
[18:52] <mdeslaur> mvo: have you got a minute? I want to update flashplugin-nonfree in hardy from v9 to v10. There is another package that some people install called "libflashsupport" that ships a library that is incompatible with v10.
[18:52] <mdeslaur> mvo: of course, even if I try to conflicts/replaces it, update-manager in hardy won't remove it
[18:52] <mdeslaur> mvo: is my only hope to ship a dummy libflashsupport update that is empty?
[18:57]  * ogra glares at bug 9068
[18:57] <ogra> mandriva uses casper ?!?
[18:59] <mdeslaur> mvo: hmm..I'll try adding a transitional package to flashplugin-nonfree
[19:00] <marjo> stgraber: I noted same to jibel; will fix in future point releases
[19:04] <cjwatson> stgraber: in the case of http://iso.qa.ubuntu.com/qatracker/info/5015, that should be /lucid/dvd/...
[19:04] <cjwatson> stgraber: generally, put lucid/ before the "daily", "daily-live", or "dvd" bit
[19:05]  * ogra wonders how long main promotion takes nowadays
[19:05] <ogra> publisher should have run several times now
[19:05] <cjwatson> I probably forgot to release the lock after my manual work earlier today
[19:05] <ogra> oh
[19:06] <cjwatson> released, hopefully the next run will work
[19:06] <cjwatson> sorry about that
[19:06] <ogra> thanks
[19:06] <ogra> no problem
[19:34] <kees> pitti: is /etc/default/apport's "maxsize" actually used anywhere?
[19:42] <Riddell> @pilot out
[19:52] <ari-tczew> cjwatson: lilo 23 in Debian. what's the decision?
[19:56] <cjwatson> ari-tczew: I followed up to the bug
[19:56] <ari-tczew> cjwatson: stay with 22?
[19:56]  * cjwatson wonders why he is on the hook for lilo - I'm a grub developer, I'd rather not deal with lilo
[19:57] <cjwatson> ari-tczew: are you prepared to deal with all issues that arise from upgrading?
[19:58] <cjwatson> e.g. subscribe to all lilo and lilo-installer bugs until at least the natty release
[19:58] <ari-tczew> cjwatson: guess no
[19:58] <cjwatson> then I think we ought to merge up to what was released in squeeze, and let the new version shake out in Debian for a while
[19:58] <cjwatson> that seems like a reasonable course of action to me.  do you agree?
[19:59] <cjwatson> without somebody paying attention to it in Ubuntu, I think we should be fairly conservative and stick with what we would have done if it hadn't had Ubuntu modifications - sync up to Debian import freeze
[20:00] <cjwatson> it's different when somebody has taken active ownership
[20:02] <ari-tczew> cjwatson: I agree.
[20:06] <slangasek> SpamapS: ping
[20:12] <SpamapS> slangasek: pong hey. :)
[20:12] <SpamapS> slangasek: so, the restart action..
[20:12] <slangasek> yes!
[20:13] <SpamapS> slangasek: in discussing with keybuk, he made it clear that it is intended to restart the job *without* reloading the job file.
[20:13] <slangasek> SpamapS: "it is intended" under what circumstances?
[20:13] <slangasek> I mean, that's what the 'restart' command is designed to do, right?
[20:14] <slangasek> but those are not the defined semantics of the init script interfaces
[20:14] <SpamapS> slangasek: right, it is designed to restart the job, without reloading the job config...
[20:14] <slangasek> and /lib/init/upstart-job accounts for this by calling stop && start instead of calling restart
[20:15] <slangasek> *because* we need to make sure we're forcing a reload of the job
[20:15] <SpamapS> It does.. oook.. good.
[20:15] <SpamapS> For some reason I thought it used the restart action.
[20:15] <slangasek> nah - I had this conversation with Keybuk a while ago :-)
[20:17] <SpamapS> slangasek: well glad I could occupy some of your brain-space for a few minutes. Carry on then.
[20:17] <slangasek> SpamapS: glad to help :)
[21:01] <kees> ari-tczew: nvclock> sounds fine; much easier that way.
[21:02] <ari-tczew> kees: about nbd: OK, Agreed with sync in natty+1. However, probably natty is affected by CVE and I'll prepare debdiff in CVE's bug.
[21:03] <ari-tczew> kees: about openssl: I'll _TRY_ to update d/changelog, but it seems to be hardcore to do
[21:05] <ari-tczew> kees: and now we are entering in problem: developers prefer to upload changes to archive without describe changes in details like e.g. d/rules: foo bar
[21:05] <ari-tczew> just 'foo bar' without describing changes in which files done
[21:05] <cjwatson> and that's perfectly reasonable
[21:06] <ari-tczew> cjwatson: what?
[21:06] <cjwatson> people who need that level of detail can look in a VCS - changelogs are a little bit more user-focused
[21:06] <kees> ari-tczew: nbd> yeah, the CVE fix is appreciated. I'd like to know how far back it goes, though.
[21:06] <cjwatson> while I do sometimes mention individual files in debian/changelog, I normally only describe the functional change made
[21:06] <kees> ari-tczew: openssl> yup; that's why merging can be difficult. unless you can understand and explain each change, it's not a good idea to just cargo-cult them forward.
[21:07] <kees> cjwatson: for merges, I like having the mapping.
[21:07] <cjwatson> I don't usually object when people include it, but it is in no way a requirement
[21:07] <ari-tczew> cjwatson: very very good solution! (sarcasm), now while merging contributor wastes time to looking about information changes, congrats
[21:08]  * cjwatson ignores ari-tczew in order to avoid breaching the code of conduct.
[21:08] <kees> ari-tczew: there's no need for that tone. developers each have their own preferences and time constraints.
[21:08] <ari-tczew> what breaching? I'm just telling the true
[21:09] <ari-tczew> sometimes it might hurt, though
[21:09] <kees> ari-tczew: I happen to prefer verbose merge logs, as it helps me review the work since I'm rarely a primary maintainer for packages.
[21:09] <kees> it's not a waste of time to understand the changes in a package when doing a merge.
[21:09] <ari-tczew> kees: bullshit
[21:10] <ari-tczew> I call this way an egoism
[21:10] <ari-tczew> I won't describe changes in details because someone else will do it while merging.
[21:11] <kees> I think you misunderstand the motivation.
[21:12] <kees> I happen to disagree with cjwatson's opinion on the level of detail, but that doesn't mean either of us is wrong.
[21:13] <cjwatson> for example, here's one of my changelog entries:
[21:13] <cjwatson>   * Use a separate build directory, eliminating the requirement to preserve
[21:13] <cjwatson>     some files by hand.
[21:13] <cjwatson> I don't see that that would gain anything by enumerating all the little details, and it would be a lot of noise for users.
[21:14] <ari-tczew> cjwatson: normal uses usually don't understand that specific changes
[21:14] <cjwatson> (This was a changelog entry written for Debian, but I write Debian and Ubuntu changelog entries essentially the same way and I happen to think that that's a good thing.)
[21:15] <cjwatson> People who need to know the exact details can look in a VCS, which is more convenient for that anyway.
[21:16] <kees> and I'm saying I prefer details for when package deltas get large.  e.g. lvm2 mdadm
[21:16] <ari-tczew> anyway, it's egoism
[21:18] <cjwatson> In some cases it can be useful, certainly
[21:18] <cjwatson> I just don't agree with mandating it in all cases; I've found that the cases where I need it are rare
[21:20] <ari-tczew> kees: so I have to more time for update d/changelog and I'll do it at the weekend because someone else WAS LAZY to do it appropriate
[21:21]  * ari-tczew True hurts, not breaking Code of Conduct.
[21:22] <kees> ari-tczew: you're making a judgement about cjwatson's opinions. I don't recommend doing that for anyone.
[21:23] <ari-tczew> kees: I'm just pointing what is wrong in development flow of work.
[21:24] <kees> ari-tczew: this is not a black and white issue. it's not wrong, it just makes merging later somewhat more difficult if you're unfamiliar with the package.
[21:24] <ari-tczew> but what do I know, I'm not developer with 10 years expierence
[21:25] <cjwatson> and honestly, nobody who doesn't make themselves fairly familiar with, say, grub2 is going to be able to merge it correctly anyway
[21:25] <cjwatson> so I've deliberately gone for trying to be a bit more concise there, while still describing the changes adequately to explain the differences versus Debian
[21:26] <cjwatson> not every piece of explanation needs to live in the changelog; it can often quite reasonably live elsewheree
[21:27] <cjwatson> aiming for concision in changelogs doesn't imply (in the extreme) writing comment-free ultra-obscure code just because you like it that way
[21:27] <ari-tczew> cjwatson: do I like? kees as sponsor requires it from me
[21:32] <smoser> i guess i'm missing something.
[21:32] <kees> smoser: ?
[21:32] <smoser> i bzr branch lp:ubuntu/natty/udev
[21:32] <smoser> cd udev
[21:33] <smoser> bzr bd -S ... sbuild -d natty-amd64 --arch-all ../udev_165-0ubuntu3.dsc
[21:33] <smoser> build fails unable to find linux/videodev.h:
[21:33] <ari-tczew> smoser: v4l is dead.
[21:34] <ari-tczew> smoser: you have to port package to support v4l2
[21:34] <smoser> hm.. i see i'm out of date. maybe i need to try with 166-0ubuntu1  which isn't synced yet to bzr repo
[21:35] <smoser> ari-tczew, i just want to build it. should not the above basically rebuild ?
[21:35] <poolie> hi smoser
[21:35] <ari-tczew> smoser: probably rebuild will result in FTBFS
[21:36] <smoser> hi poolie
[21:36] <ari-tczew> since linux/videodev.h is no longer supplied by linux-libc-dev
[21:52] <ari-tczew> zul: you might be interested in comments on https://code.launchpad.net/~ssalley/ubuntu/natty/likewise-open/likewise-open-fix-716615/+merge/49458
[22:06] <jdong> cjwatson: what's your opinion on the suitability of the natty patch for bug 232557 for SRU?
[22:07] <jdong> I just happened to run across a particularly horrendous occurrence of this bug leading to console-kit-daemon using close to 6GB memory
[22:08] <jdong> looks like the git patch is http://cgit.freedesktop.org/ConsoleKit/commit/?id=7b9212fa6aff55420c58f2cacd0a941762920337 from andersk
[22:52] <cjwatson> jdong: I haven't looked at the patch (not at my laptop), but your description of the problem sounds SRUable to me
[22:58] <jdong> cjwatson: *nods* Indeed the bug itself is IMO SRU-able, just the FDO bugzilla discussion worried me in that andersk seems to still express a correctness concern over the patch (e.g. a potential use-after-free)
[22:59] <jdong> but seeing how upstream accepted it into their latest release.... *shrug*
[23:00] <broder> jdong: did upstream end up taking Anders' followup _ref/_deref patch?
[23:01] <jdong> broder: I couldn't find evidence of that in git :-/ and the FDO bug didn't have any comments after that one.
[23:01] <jdong> https://bugs.freedesktop.org//show_bug.cgi?id=26227
[23:01] <broder> ugh
[23:13] <RoAkSoAx> kirkland: do you want timestamp in the logging for testdrive?
[23:14] <kirkland> RoAkSoAx: sure!
[23:28] <andersk> I posted another comment to poke upstream about that potential use-after-free.
[23:34] <jdong> andersk: thanks
[23:52] <chrisccoulson> slangasek, re bug 439007 - the retracer doesn't run on any firefox crashes now, as they all go directly upstream since lucid (using breakpad)
[23:54] <slangasek> chrisccoulson: well, that was reported pre-lucid, and anyway having them sent upstream doesn't help us any with triaging that bug report...