[00:29] <zooko> Folks I'm upgrading my trac and I want to keep my trac<->launchpad integration working.
[00:29] <zooko> Should I upgrade XmlRpcPlugin and TracLaunchpadPlugin?
[00:29] <zooko> From http://trac-hacks.org/wiki/XmlRpcPlugin and https://launchpad.net/trac-launchpad ?
[00:30] <lifeless> noooo idea sorry.
[00:31] <lifeless> I think you should have a test trac install
[00:31] <lifeless> and do upgrades there first, to make sure it works.
[00:31] <zooko> That sounds like so much work.
[00:31] <zooko> Anyway it is too late. I've upgraded my trac.
[00:31] <lifeless> hah
[00:31] <lifeless> so 'Folks I've upgraded'... :P
[01:41] <Meths> Can you link a bug to a revision/commit it is fixed in?
[01:42] <spiv> Meths: just to a branch.  You can leave a comment with the revno or revision ID or tag if you like.
[01:43] <Meths> Okay, thanks.
[06:12] <mtaylor> any launchpad admins around? friend of mine has lost his password and access to the email account it's sending reset mails to...
[06:19] <jhesketh> When reporting a bug and assigning it to a person (who is not me), that person doesn't get any email notifications? Does anybody know why?
[06:19] <neurodamage> I'm locked out of my launchpad account that's linked to drizzle development, been a week now since I've tried sending my account emails for password reset with no luck? any admins in the  house possibly take a look :)
[06:19] <jhesketh> He does get emails about subsequent comments and changes to the bugs... just not the bug creation
[06:44] <mtaylor> thumper: ping
[06:45] <spm> mtaylor: sure (on a maybe, if you ken), which account?
[06:46] <mtaylor> spm: it's for neurodamage here ... account is ~sahil-cooner
[06:46] <spm> np, one sec
[06:46] <mtaylor> thanks!
[06:48] <neurodamage> spm: awesome, thanks
[06:48] <spm> neurodamage: ok, that looks sane, what's an email I can set?
[06:48] <spm> tho how you lost control of your own named domain is ... amusing ;-)
[06:49] <neurodamage> spm: indeed :)
[06:49] <spm> neurodamage: you should get a 'please confirm' email rsn. ??
[06:49] <neurodamage> spm: yes sir, all set, thanks :)
[06:50] <spm> sweet, I'll leave it with you. cheers!
[06:51]  * neurodamage nods
[07:34] <thumper> mtaylor: whazzup?
[07:35]  * thumper reads back and figures it is probably sorted
[07:41] <mneptok> thumper: don't help mtaylor. i did a few times, and ten found him outside my bedroom window with a mandolin. although romatic, my wife was unimpressed.
[07:41] <mneptok> *then
[07:48] <spm> thumper: almost; we've been in personal chat; but is sorted now.
[09:32] <lool> Hi
[14:11] <bdrung_> the code import of audacious failed (https://code.launchpad.net/~vcs-imports/audacious/trunk - http://launchpadlibrarian.net/50376457/vcs-imports-audacious-trunk.log). which project should i file the bug against?
[14:13] <mwhudson> bdrung_: bzr-hg, although i think that particular bug is already reported
[14:13] <mwhudson> (bzr-hg isn't very good :()
[14:13] <bdrung_> second question: which project is responsible for linking to other bug tracker? JIRA (http://www.atlassian.com/software/jira/) is not supported.
[14:14] <mwhudson> malone
[14:14] <mwhudson> i bet there's a bug for that too :-)
[14:14] <mwhudson> bdrung_: https://bugs.edge.launchpad.net/malone/+bug/157488
[14:15] <jpds> bug #157488
[14:16] <bdrung_> thx
[14:17] <bdrung_> back to the first one: https://bugs.launchpad.net/bzr-hg/+bugs doesn't look like my problem
[14:26] <maxb> bdrung_: It appears to be evilly conflated in https://bugs.edge.launchpad.net/bzr-hg/+bug/516758
[14:26] <maxb> If you were feeling particularly helpful you could split apart that bug for the two separate issues
[14:27] <jcastro> jml: http://blog.launchpad.net/bug-tracking/getting-patches-upstream
[14:27] <jcastro> jml: I believe those images were on kfogel's people account
[14:27] <maxb> Actually, meh, I've looked at it now, I might as well split it myself
[14:28] <jml> jcastro, ah.
[14:28] <jml> mrevell, could you please look into that? http://blog.launchpad.net/bug-tracking/getting-patches-upstream
[14:29] <mrevell> Sure will do
[14:36] <jml> mrevell, thanks.
[15:22] <jcastro> abentley: how are things coming along?
[15:23] <abentley> jcastro, I'm pleased with the results of the stress-test, and the UI, but not builders, is available on staging.
[15:23] <jcastro> nice!
[18:05] <leoquant> are spam/scam attacks daily routine these days regarding launchpad accounts?
[18:05] <leoquant> content:
[18:05] <leoquant> This e-mail was send by ubuntu.com to notify you that we have temporanly prevented access to your account.
[18:06] <leoquant> via ccheney
[18:07] <leoquant> Please click on the link below or copy and paste the URL into your browser:
[18:10] <jpds> sinzui: ^--.
[18:11] <leoquant> nevermind
[20:37] <kees> hi! how do I configure a project so that all merge requests are emailed to a specific mailing list?
[20:39] <maxb> kees: I think that configuration is per branch, and is called "default review team"
[20:40] <kees> maxb: so a lp user needs to be created that has the mailing list as an email address?
[20:40] <maxb> Yes
[20:40] <kees> okay, thanks.
[20:41] <maxb> And then you want the "Set branch reviewer" link on the branch web page
[21:02] <lifeless> kees: if the group of people that you want mailed is already modelled in launchpad
[21:02] <lifeless> kees: then it is better to just make that group (or groups) be reviewers.
[21:02] <lifeless> kees: as launchpad can't honour custom notification rules for external lists (e.g. some people want more detail)
[21:02] <lifeless> kees: with the result that people get mailed twice and so on
[21:22] <MTecknology> Any ideas why I can't propose ~ubuntu-drupal-devs/ubuntu-drupal-theme/6.x-2010 for merging into ~ubuntu-website-community/ubuntu-website/light-drupal-theme ?
[21:25] <beuno> MTecknology, my guess would be that those branches are on different projects
[21:26] <beuno> you should push your branch to ubuntu-website
[21:26] <MTecknology> beuno: oh- I didn't know you couldn't merge across projects
[21:26] <MTecknology> alrighty- thanks
[21:26] <beuno> MTecknology, I'm not 100% sure you can't but that would be my guess
[21:27] <lifeless> MTecknology: when you say you can't
[21:27] <lifeless> MTecknology: do you mean 'launchpad issues an error' ?
[21:27] <MTecknology> This branch is not mergeable into lp:ubuntu-website/light-drupal-theme.
[21:27] <MTecknology> I'm just trying to do the proposal
[21:27] <lifeless> well, thats both clear an uninformative.
[21:27] <lifeless> please file a bug asking for it to be more informative ;)
[21:28] <lifeless> MTecknology: meanwhile, if you grab bzr 2.2b3 or so
[21:28] <MTecknology> ok- is it exactly what beuno said?
[21:28] <lifeless> MTecknology: I have no idea.
[21:28] <lifeless> I'm just noting a rough edge, that the lp-code team will want to polish
[21:28] <MTecknology> ok, will do
[21:29] <lifeless> MTecknology: bzr 2.2ish should be able to propose it, if the API's permit it.
[21:29] <lifeless> sit in in the 6.x-2010 branch on your disk, run bzr lp-propose lp:~ubuntu-website-community/ubuntu-website/light-drupal-theme
[21:30] <MTecknology> aight, I'll get the ppa and try that
[21:31] <MTecknology> lifeless: the package is qbzr?
[21:31] <MTecknology> no..
[21:32] <lifeless> bzr
[21:32] <MTecknology> lifeless: I was looking at https://edge.launchpad.net/~bzr-beta-ppa/+archive/ppa
[21:36] <MTecknology> lifeless: where's the right ppa?
[21:36] <lifeless> ppa:bzr I think
[21:37] <lifeless> actually thats releases only
[21:37] <lifeless> uhm
[21:37] <lifeless> the beta ppa should have a bzr in it
[21:37] <MTecknology> I added bzr-beta-ppa:ppa but bzr doesn't seem to be an available update
[21:39] <lifeless> hmm
[21:40] <lifeless> MTecknology: for this test, just grab the 2.2b3 tarball, unpack in /tmp and then from your branch run /tmp/bzr-2.2b3/bzr lp-propose ....
[21:41] <MTecknology> ok
[21:43] <MTecknology> oops
[21:46] <MTecknology> lifeless: bzr: ERROR: No reviewer specified
[21:46] <MTecknology> also get this bzr: warning: some compiled extensions could not be loaded; see <https://answers.launchpad.net/bzr/+faq/703>
[21:47] <kees> lifeless: yeah, the issue is that we want a non-entity (a mailing list) to get all the merge requests.
[21:47] <lifeless> MTecknology: ignore the extensions thing
[21:47] <kees> lifeless: I'll make it work.  :)
[21:47] <lifeless> kees: why though?
[21:47] <lifeless> kees: I ask for input into launchpads needs
[21:48] <lifeless> MTecknology: add -R ubuntu-website-community
[21:49] <MTecknology> lifeless: :P - I actually managed to press enter the second you said that
[21:50] <kees> lifeless: upstream AppArmor wants to have merge requests to go to the devel mailing list so they can be discussed there.
[21:50] <MTecknology> lifeless: http://dpaste.com/208132/
[21:51] <lifeless> kees: ok
[21:51] <lifeless> kees: so I suggest you do the following to model it in lp
[21:51] <lifeless> kees: I'm just checking the UI - 2 secs - so that I offer the right suggestion :)
[21:52] <lifeless> ok
[21:52] <lifeless> make a team for reviews of apparmour
[21:52] <lifeless> in that team put two sub teams
[21:52] <lifeless> one which is the mailing list forwarder
[21:52] <lifeless> and one which contains actual people that should be able to click the 'this is approved' button in launchpad.
[21:52] <lifeless> e.g. apparmour committers
[21:53] <lifeless> thats just a suggestion, you might prefer one team with a contact address over on the apparmour lists
[21:53] <lifeless> however
[21:53] <lifeless> remember that launchpad only allows *one* team to have that contact address
[21:54] <lifeless> and if you were to ever need it again elsewhere in LP you'd be faced with a team that proxies the list *also* being a list of commit approvers.
[21:54] <lifeless> which is wrong - thus my suggesting a separation
[21:54] <lifeless> the subscription of the people containing team to the branch would be set to 'no mail'
[21:55] <lifeless> and thus only the list proxy team would get mail sent to it.
[21:55]  * lifeless ends handwaving
[21:55] <lifeless> MTecknology: ok, definitely not permitted ;)
[21:55] <lifeless> MTecknology: 2 bugs : the UI wasn't clear about *why*; the proposal wasn't *permitted*
[21:56] <MTecknology> lifeless: can you tell from that if it's just because it's across projects?
[21:56] <MTecknology> I can easily enough clone this in that project
[21:57] <lifeless> I can't tell no, but sure do that.
[21:57] <lifeless> MTecknology: please do file the bugs though!
[21:57] <lifeless> MTecknology: including a third on that I will file, that lp-propose doesn't show the detailed rendering of the LP error.
[21:57] <MTecknology> alrighty
[21:57] <MTecknology> yay bugs
[21:58] <MTecknology> lifeless: what project should this go in?
[21:58] <lifeless> launchpad-code
[22:03] <lifeless> MTecknology: I filed bug 595271 for you
[22:04] <MTecknology> lifeless: I was just about to report that
[22:04] <MTecknology> lifeless: bug 595271
[22:04] <MTecknology> err..
[22:04] <MTecknology> bug 595269
[22:05] <lifeless> I suspect the linaro gcc folk are going to care about that one
[22:08] <MTecknology> lifeless: thanks
[22:11] <MTecknology> lifeless: I was just thinking... It could have something to do with the cross-project thing - considering branches are generally meant to be merged into that project
[22:12] <lifeless> MTecknology: it might
[22:12] <lifeless> MTecknology: but bzr can do it in this case, I assume
[22:12] <MTecknology> I copy/pasted (w/bzr) to that project and it worked like peaches.
[22:13] <MTecknology> lifeless: thanks again - im'a run off now
[22:13] <lifeless> at the db level, a simple double-join into BranchRevision would tell us.
[22:20] <MTecknology> lifeless: Launchpad encountered an internal error during the following operation: generating the diff for a merge proposal.  It was logged with id OOPS-1628MPJ1.  Sorry for the inconvenience.
[22:20] <MTecknology> I have OOPS-1628MPJ1 OOPS-1628MPJ2 OOPS-1628MPJ3 emails
[22:21] <lifeless> we need to wait a minute for them to sync
[22:21] <MTecknology> ok
[22:59] <kees> lifeless: sounds good; thanks!
[23:29] <lifeless> 09:20 < MTecknology> lifeless: Launchpad encountered an internal error during the following operation: generating the diff for a merge proposal.  It was logged with id OOPS-1628MPJ1.  Sorry for the inconvenience.
[23:29] <lifeless> 09:20 < ubot5> https://lp-oops.canonical.com/oops.py/?oopsid=1628MPJ1
[23:29] <lifeless> 09:20 < MTecknology> I have OOPS-1628MPJ1 OOPS-1628MPJ2 OOPS-1628MPJ3 emails
[23:29] <lifeless> bah