[00:22] <randomusername> hey wgrant
[00:25] <wgrant> Hi randomusername.
[00:25] <randomusername> hey
[00:26] <randomusername> did they find anything in my absence?
[00:26] <wgrant> Not that I saw.
[00:37] <maxb> Though, we found another user with the same issue
[00:38] <wgrant> We did.
[00:38] <wgrant> And it's broken on staging now.
[00:38] <wgrant> So we can get someone to poke easily.
[00:38] <wgrant> The thing is, the data migration patch looks fine.
[00:41] <wgrant> randomusername: Can you try logging into dogfood.launchpad.net? Do you have the same problem there?
[00:41] <randomusername> dogfood?
[00:42] <wgrant> It's a test server.
[00:42] <randomusername> do you want me to test it now?
[00:42] <wgrant> Ideally.
[00:42] <wgrant> Just see which account it logs you in as.
[00:43] <maxb> huh, odd. staging/~ddorda does not oops, but staging/~tiagosilva does, whilst both of those oops on lpnet
[00:44] <wgrant> Oh.
[00:44] <wgrant> I see the problem.
[00:44] <wgrant> randomusername: You've logged in on staging lately, haven't you?
[00:45] <randomusername> wgrant: dunno what you mean
[00:45] <randomusername> just tested it on dogfood and I'm tiagosilva29 ~_~
[00:45] <wgrant> randomusername: Have you visited and logged into staging.launchpad.net in the last few days?
[00:45] <randomusername> nope
[00:45] <wgrant> Hmm, odd.
[00:45] <wgrant> But I see the problem, anyway.
[00:46] <wgrant> So.
[00:47] <wgrant> Let's see...
[00:50] <wgrant> randomusername: Is your primary email address on https://login.launchpad.net/ shown on https://launchpad.net/~tiagosilva29?
[00:51] <randomusername> yes
[00:53] <randomusername> uhm
[00:53] <randomusername> actually no
[00:53] <randomusername> depends
[00:53] <wgrant> Hm?
[00:53] <randomusername> my openid login address was say XXX
[00:53] <randomusername> was = is
[00:54] <randomusername> but I later changed my _launchpad_ email address to XXX+floss
[00:54] <randomusername> about a couple of months ago, I think
[00:55] <wgrant> Around June, I suspect.
[00:55] <wgrant> What happened here is this:
[00:56] <randomusername> uhm
[00:56] <randomusername> XXX+launchpad , tbh
[00:56] <wgrant>  - You changed your Launchpad email address to have a +launchpad suffix.
[00:56] <randomusername> yes
[00:56] <wgrant>  - Something (a package upload or translation import, perhaps) came along with your old email address, saw it wasn't linked to an profile, so created a placeholder profile for that address.
[00:58] <randomusername> crap
[00:59] <wgrant> Now, Launchpad's login code changed last Thursday. Until then, it would use an internal string to identify your account. Now it looks up the email address and that identifying string, takes the profile that owns the email address, and confirms that the ID string is also associated with that profile.
[00:59] <wgrant> If they're not the same profile, it believes the email address, and moves the identifier onto the profile with that email address.
[00:59] <wgrant> So it saw your ~tiagosilva29 with the login.launchpad.net email address, and moved your authentication identifier over to that.
[01:00] <wgrant> So now ~tiagosilva has no means of authentication, which is why it's OOPSing.
[01:00] <wgrant> You can probably fix this by using the normal account merge functionality.
[01:00] <wgrant> But...
[01:00] <wgrant> We should probably see if a general fix is possible.
[01:00] <randomusername> what a mess
[01:00] <wgrant> Rather.
[01:00] <randomusername> (a package upload or translation import, perhaps) -> on my part?
[01:01] <randomusername> or something else, like another translator in the portuguese team with a .po file?
[01:01] <wgrant> It could have been a PO file.
[01:01] <wgrant> I can't see exactly what.
[01:02] <wgrant> For one of the other problematic users, it was a PO file.
[01:04] <randomusername> bloody hell
[01:05] <randomusername> so, should I use the account merge?
[01:07] <wgrant> Not yet.
[01:07] <wgrant> Need to check if there's anything else we can do first.
[01:13] <randomusername> okay
[01:13] <randomusername> wgrant: I have to go to sleep, I'll try to be here around the same time tomorrow, k?
[01:13] <randomusername> thanks for everything so far
[01:14] <wgrant> randomusername: With any luck we'll have a resolution by then.
[01:14] <randomusername> ;)
[03:03] <h00k> I'm having a problem reporting a bug :(
[03:04] <nhandler> h00k: What is the problem?
[03:04] <h00k> nhandler: Disclaimer: using edge
[03:04] <h00k> nhandler: Sorry, there was a problem connecting to the Launchpad server.
[03:04] <h00k> wait a minute and refresh, or let us know in #launchpad, etc.
[03:05] <h00k> I had a kernel oops on maverick and apport was trying to report it
[03:05] <nhandler> h00k: IIRC, there were some apport issues that they were working on earlier.
[03:06] <h00k> Alright
[03:16] <h00k> nhandler: It does a duplicate check, asks me for details, and when I hit 'Submit' is when I get this
[03:16] <h00k> to actually post the bug
[03:25] <humphreybc> Who should I talk to about team privacy?
[03:27] <lifeless> mrevell
[03:43] <wgrant> h00k: Bug 636801
[03:46] <h00k> I don't know that it necessarily has a lot of attachments
[03:46] <h00k> perhaps
[03:48] <wgrant> h00k: Kernel bugs normally do... what was the URL?
[03:55] <h00k> wgrant: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+filebug/5ca89d78-bfa3-11df-905e-0025b3df357a?field.title=WARNING:+at+/build/buildd/linux-2.6.35/net/wireless/core.c:633+wdev_cleanup_work%2B0xe1/0x110+[cfg80211]()
[03:55] <h00k> wgrant: does this help?
[03:57] <wgrant> h00k: Indeed.
[03:57] <wgrant> h00k: It has 21 attachments.
[03:57] <wgrant> == lots
[03:57] <h00k> wgrant: gotcha, okay. I marked that bug as affecting me
[03:58] <wgrant> Great.
[03:58] <h00k> I'm just not sure how to file it ;)
[03:58] <h00k> potentially just wait until it gets fixed? Will that link stay valid?
[03:58] <h00k> wgrant: ^
[03:58] <wgrant> The link will break soon :(
[03:59] <wgrant> I think it expires after around a day.
[03:59] <h00k> d'aw
[04:03] <h00k> Can I save those attachments somehow and report a bug and attach them one-by-one?
[04:05] <wgrant> h00k: If you can find the file locally, you can remove bits that look irrelevant and reupload.
[04:05] <wgrant> It's just a MIME document, from which you can remove files easily.
[04:06] <wgrant> (reupload to https://launchpad.net/+storeblob -- it will give you an ID to put in the +filebug URL)
[04:36] <h00k> wgrant: okay, thanks, I'll take a look when this movie is over
[05:03] <sensae> Hello. For some reason I can't push to a certain branch in launchpad. When I do a "bzr push lp:projectname" it hangs at console and never prints any output.
[05:05] <sensae> I just tried pushing to +junk and it was successful.
[05:07] <nigelb> sensae: does that project have a trunk defined?
[05:08] <sensae> nigelb: Yes. I just got it to successfully push, but only by deleting the defined trunk before pushing it. The trunk was defined and even said "This branch has no content. Bzr push lp:nbtparser to populate it" (a message to that effect)
[05:08] <sensae> nigelb: Also, I wasn't using the short name lp:nbtparser, I was trying to push to lp:~blainepace/nbtparser/trunk .
[05:09] <nigelb> sensae: That's strange
[05:10] <sensae> nigelb: I tried to recreate it by defining a 'testbranch', and then pushing to it and I got an error "Target directory already exists but does not have .bzr folder."
[05:11]  * thumper reads
[05:12] <thumper> sensae: which project?
[05:12] <sensae> thumper: nbtparser
[05:12] <sensae> ..Odd. I just got some errors about maximum recursion depth.
[05:13] <thumper> sensae: which version of bzr are you using?
[05:13] <sensae> thumper: 2.2.0
[05:13] <thumper> sensae: which OS?
[05:14] <sensae> thumper: OSX
[05:14] <thumper> sensae: did you delete the old branch or just move it?
[05:14] <sensae> thumper: Which branch are you referring to?
[05:15] <thumper> sensae: you don't have a trunk branch set right now
[05:15] <thumper> sensae: you should do a bzr whoami so it includes your email address
[05:16] <thumper> sensae: then launchpad can work out who you are and give you revision karma :)
[05:16] <sensae> thumper: is bzr launchpad-login my@email.com ?
[05:16] <sensae> *ie
[05:16] <thumper> no
[05:16] <thumper> bzr whoami "My name <email@example.com>"
[05:17] <thumper> your bzr launchpad-login should be your LP id
[05:17] <sensae> thumper: I see, set properly now. So that would effect my ability to push to ie lp:~blainepace/project/trunk ?
[05:18] <thumper> no
[05:18] <thumper> not at all
[05:18] <thumper> that is strange
[05:18] <thumper> although...
[05:18] <sensae> sensae: That's where I was trying to push, because I knew I hadn't linked the trunk branch as the main development focus
[05:18] <thumper> the bzr client does do an xmlrpc lookup
[05:18] <thumper> and we have some known issues right now with the xmlrpc server
[05:18] <thumper> sensae: :) as of Thursday last week
[05:19] <thumper> sensae: you can go bzr push lp:project and it will set dev focus for you :)
[05:19] <thumper> and create the branch
[05:20] <sensae> thumper: I got around it by actually deleting the branch on lp and then pushing to the nonexistent trunk branch.
[05:20] <thumper> sensae: there is something else strange going on
[05:20] <sensae> thumper: Though I'm still getting an error when I try pushing to a 'testbranch' I created. Just for playing with this strange behavior.
[05:20] <thumper> sensae: can I get you to try something for me?
[05:21] <thumper> sensae: what error?
[05:21] <sensae> thumper: Sure, and basically 'directory already exists, but .bzr does not exist.'
[05:21] <sensae> thumper: I just got it to push, but I had to use --use-existing-dir
[05:21]  * thumper nods
[05:21] <thumper> we are wanting to change the register branch page
[05:21] <thumper> to say "just push branches"
[05:21] <thumper> don't bother creating them first
[05:22] <thumper> the system gets a tad confused
[05:22] <sensae> -nods- Seems like it's easier anyway
[05:22] <thumper> it has been floating further up my todo list
[05:23] <thumper> sensae: just try 'bzr push lp:nbtparser'
[05:23] <thumper> sensae: and let me know what happens
[05:23] <sensae> thumper: Alright
[05:25] <sensae> thumper: It created a branch trunk-1 alongside my 'trunk' branch
[05:25] <thumper> sensae: expected since you had a branch called trunk already
[05:26] <sensae> thumper: That's because I didn't flag my trunk branch as the main line, correct?
[05:27] <thumper> sensae: that is because it creates a new branch for trunk, but cleverly avoids name conflicts
[05:28] <thumper> sensae: if you find yourself getting weird bzr errors again
[05:28] <thumper> sensae: can you run with -Dhpss
[05:28] <thumper> sensae: and file a bug with ~/.bzr.log attached?
[05:28] <sensae> thumper: Ah. Yeah, I deleted trunk-1 and then attached trunk to my 'trunk' series, and it attached it to lp:nbtparser
[05:28] <thumper> sensae: you may want to clense older info from the file
[05:28] <sensae> thumper: Sure.
[05:28] <thumper> sensae: thanks
[05:30] <sensae> I've got to say, even though there are some hiccups sometimes with using lp and it takes some getting used to, I'm enjoying it a lot more than github. It's a plus that this channel is so friendly and helpful :)
[05:30] <thumper> thanks
[05:41] <sensae> I had one other question. --fixes lp:bugnumber should do what exactly? Close the bug? I see no effect on my lp project page
[05:44] <mwhudson> sensae: it should link the branch to the bug
[05:44] <sensae> mwhudson: Ah, alright. It looks like it did that. As I said above, I'm a github convert so I'm used to "closes #2" automatically linking -and- closing an issue.
[05:46] <mwhudson> sensae: it's not necessarily appropriate to mark the bug as fixed until the --fixes revision makes it into trunk
[05:46] <mwhudson> if you made assumptions about workflow, we could do stuff automatically
[05:46] <mwhudson> but launchpad doesn't do that
[05:47] <sensae> mwhudson: I'm not meaning it as a detraction from launchpad, while it would make my particular workflow a bit easier I understand the reasoning behind just linking the branch. Marking it myself isn't a big deal and tbh the added flexibility and lack of assumptions is one of the reasons I moved to lp :)
[05:49] <mwhudson> sensae: heh, interesting
[05:49] <thumper> it has been on another todo list to at least add a fix committed to the appropriate bug task
[05:49] <thumper> but...
[05:50] <thumper> it hasn't reached the top :(
[08:25] <lucidfox> Is it possible to have the LP bug tracker monitor bzr commits for a project and update bug status based on commit messages?
[08:26] <poolie> lucidfox: it will link them to the bugs but at the moment not change the status
[08:26] <poolie> however there is a script that will update them
[08:26] <bilalakhtar> lucidfox: That's being planned, though
[08:26] <bilalakhtar> poolie: ^^
[08:26] <lucidfox> poolie> Okay, is it possible to automatically link commits to bugs then?
[08:27] <lucidfox> and if yes, how?
[08:27] <bilalakhtar> There's some bug about it, to set bug status to Fix Committed when the bug gets fixed in the main devel branch
[08:27] <poolie> lucidfox: 'bzr ci --fixes lp:397315'
[08:27] <bilalakhtar> lucidfox: just use this method:
[08:27] <bilalakhtar> bzr commit -m "foo message" --fixes lp:BUGNUMBER
[08:27] <lucidfox> Oh, thanks
[08:28] <lucidfox> I didn't even know about the shortned "bzr ci" syntax, always typed "bzr commit"
[08:30] <bilalakhtar> even I didn't know
[08:31] <bilalakhtar> What's the matter with LP? All pages are ugly now! No layout!
[08:31] <bilalakhtar> Anyone else over here?
[08:34] <wgrant> bilalakhtar: Known issue with edge.
[08:34] <wgrant> Investigation ongoing.
[08:34] <wgrant> Production is fine.
[08:35]  * bilalakhtar disables redirect
[08:36] <bilalakhtar> wgrant: hey! I am unable to disable redirect! What should I do?
[08:37] <wgrant> bilalakhtar: Wait a few minutes until it's fixed.
[08:40] <lucidfox> bilalakhtar> how does one disable the edge redirect?
[08:40] <bilalakhtar> lucidfox: At the bottom of an edge page there is a link 'Disable edge redirect'
[08:40] <bilalakhtar> lucidfox: but that isn't working now
[08:40] <lucidfox> yep :/
[08:41] <bilalakhtar> That usually disables redirection for 2 hours
[08:43] <wgrant> bilalakhtar, lucidfox: You could manually set an inhibit_beta_redirect=1 cookie on *.launchpad.net
[08:43] <bilalakhtar> wgrant: who cares :D I will wait
[08:44] <lucidfox> alas, Epiphany doesn't allow manually editing cookies
[08:44] <wgrant> Anyway, rollback is in progress.
[10:40] <lucidfox> What's the standard way to credit Launchpad translators in the about dialog?
[10:41] <lucidfox> I see that Transmission, for example, has a "Launchpad Contributions:" field in the about dialog
[10:41] <lucidfox> how is it maintained?
[10:42] <dpm> lucidfox, it depends on the toolkit you use. Generally there is a special string in translations called translator-credits that LP automatically fills in. Both GTK and KDE have facilities in their standard About dialogs to read that string and automatically show the translator credits
[10:43] <lucidfox> hmm
[10:43] <dpm> lucidfox, e.g. http://library.gnome.org/devel/gtk/unstable/GtkAboutDialog.html#gtk-about-dialog-get-translator-credits
[10:43] <lucidfox> so do I need to add msgid "translator-credits" to the .pot file?
[10:44] <dpm> yes
[10:44]  * lucidfox nods
[10:45] <dpm> in gtk you can do it so: http://library.gnome.org/devel/gtk/unstable/GtkAboutDialog.html#gtk-about-dialog-set-translator-credits
[10:47] <dpm> jtv, henninge, Launchpad does not add a 'translator-credits' msgid to translations, does it? It only fills it in automatically if the original template has such a string, if I'm not mistaken
[10:47] <jtv> dpm: that's right
[10:47] <dpm> ok, thanks jtv
[10:48]  * lucidfox adds N_("translator-credits") somewhere
[10:50] <dpm> lucidfox, _("translator credits") should be enough, there is no need for plurals (assuming you are using N_ as a macro for ngettext() )
[10:51] <lucidfox> ...oh, so *that's* what N_ is
[10:51] <lucidfox> What's the equivalent of Qt's QT_TR_NOOP?
[10:51] <lucidfox> as in "Mark this string as translatable, but return it verbatim"
[11:30] <lucidfox> hmm
[11:30] <lucidfox> so the Launchpad automatic export uses filenames in the format (langcode).po
[11:31] <lucidfox> but manual export uses (projectname)-(langcode).po
[11:31] <lucidfox> not very convenient for merging :(
[13:52] <joel`> Hi there, I can't push any changes to Launchpad
[13:52] <joel`> I'm concerned I have not set something up right on the project hosting end
[13:54] <joel`> I have logged in to launchpad using "bzr lp-login" and the branch.conf contains bzr+ssh urls
[13:54] <joel`> Do I need to set up a team, even though I am the owner of the branch?
[13:55] <joel`> The branch is simpleio/trunk
[13:55] <maxb> What is the exact command you are running and in what way does it error?
[13:56] <joel`>  
[13:56] <joel`> joel@chondestes: ~/Public/src/trunk > bzr push lp:~adamsonj/simpleio/trunk
[13:56] <joel`> bzr: ERROR: Cannot lock LockDir(lp-104002896:///~adamsonj/simpleio/trunk/.bzr/branchlock): Transport operation not possible: readonly transport
[13:56] <joel`> Every topic I've seen on the web the people were trying to use http
[13:57] <joel`> a simple "bzr push" results in the same error
[13:57] <joel`> I've also tried this from a checked-out branch
[13:58] <wgrant> joel`: What's your Launchpad username?
[13:58] <joel`> adamsonj
[13:58] <joel`> "Joel J. Adamson"
[13:58] <wgrant> Ah.
[13:58] <wgrant> That's an import branch you're trying to push to.
[13:58] <joel`> Oh?
[13:59] <joel`> Okay: that's what I was afraid of...
[13:59] <joel`> Am I not really hosting my code on Launchpad as I thought?
[14:00] <wgrant> You've set up a read-only code import. You'll need to create a new writable branch.
[14:00] <joel`> Okay, how do I do that? (thanks!)
[14:00] <wgrant> At https://edge.launchpad.net/simpleio/trunk/+edit, empty the Branch field.
[14:00] <wgrant> Then 'bzr push lp:simpleio' should work.
[14:01] <joel`> Do I have to checkout (branch) again?
[14:01] <wgrant> No.
[14:01] <joel`> I'm confused: what does "You haven't yet told Launchpad where your source code is for simpleio trunk series" mean?
[14:01] <wgrant> You'll push your existing branch up into a new trunk branch.
[14:01] <joel`> Is that not what I did?
[14:01] <wgrant> joel`: We just unset that.
[14:01] <joel`> okay
[14:01] <wgrant> Since it was set to a read-only import.
[14:02] <joel`> Oh, I get it, so now when I push _then_ the code will be there?
[14:02] <wgrant> Exactly.
[14:02] <joel`> okay let me try it...
[14:02] <wgrant> Pushing to lp:simpleio will create a new Launchpad-hosted branch.
[14:02] <joel`> "Created new branch." it says
[14:03] <joel`> Okay, now the reloaded project page says the right thing
[14:03] <wgrant> The branch is now named trunk-1, though.
[14:03] <wgrant> So you should probably rename the 'trunk' import to something else, or maybe even delete it.
[14:03] <joel`> okay...I suppose I can change that somewhere?
[14:03] <wgrant> Then rename trunk-1 to trunk.
[14:04] <wgrant> Use the 'Change branch details' link on the right of the branch page.
[14:16] <joel`> I seem to be all set up except that I'd like to delete a series and I can't figure out how to get to it (to delete it)
[14:17] <wgrant> You only have a trunk series.
[14:17] <wgrant> Why do you want to delete one?
[14:17] <joel`> There was another one
[14:17] <joel`> I tried to delete it, and I got an error saying I couldn't because it was the focus of development
[14:17] <joel`> so I created another one ("trunk") and made that the focus of development
[14:18] <joel`> Did launchpad read my mind ?
[14:18] <wgrant> Oh, right, there is another one.
[14:18] <wgrant> But marked as Experimental, so I couldn't see it.
[14:18] <wgrant> Click the 'View full history' link on the project page.
[14:19] <joel`> Okay, that worked
[14:19] <joel`> thanks
[14:20] <wgrant> Great.
[14:46] <joel`> Okay, I've finally gotten everything sorted out
[14:47] <joel`> I feel like a lot of things on the website are very well-hidden
[14:47] <joel`> Am I the only one who thinks the layout is confusing?
[14:47] <joel`> I'll spend more time reading the manual
[14:48] <jml> joel`, you aren't the only one.
[14:50] <mrevell> joel`, What in particular do you find confusing? I'd love to talk to you more about what's been confusing and what we can make better. Soon I'm going to be writing a report on how we can improve the experience for new users.
[14:51] <joel`> mrevell: I see a lot of empty space on the pages, and I can never seem to find what I'm looking for
[14:52] <joel`> For example, I'll read the manual about adding a release download file, but then I go to the page that *I think* the manual referred to and I can't find the link it referred to
[14:52] <joel`> I should have spent more time going over the general concepts, as once I have those the specifics are easy for me
[14:52] <joel`> I can't say whether that's a deficit in the manual or in my own patience
[15:08] <soren> It's been almost 15 minutes since I pushed this branch: https://code.edge.launchpad.net/~soren/nova/ec2-security-groups
[15:08] <soren> It still says "Updating branch...". Are there problems with the branch scanner thingy?
[15:23] <bilalakhtar> soren: yes there is
[15:24] <bilalakhtar> soren: Stacked branches take long time occasionally to get scanned
[15:41] <maxb> bilalakhtar: I don't think it's to do with stacking?
[15:41] <bilalakhtar> maxb: I think it is. Stacked branches take considerably more system resources in scanning/merging/committing
[15:42] <maxb> I am doubtful of "considerably". "slightly", perhaps
[15:49] <Andphe> Hi there, what time format should I use in a poll, if I want it close today at midnight GMT -5 ?
[15:56] <mrevell> Andphe, I *think* you can use a variety of time formats and Launchpad'll work out what you mean. So, as LP runs in UTC/GMT, you'd want to go for 5am tomorrow GMT, so try 05:00 15/09/2010 ... let me know if that works.
[15:57] <Andphe> mrevell, thanks
[15:57] <mrevell> np
[17:08] <screen-x> Hi all, is it possible to have a "latest version" download link?
[17:36] <sproaty> I own a project, have unsubscribed from being emailed about stuff that I report, yet I still get emails when I change descriptions/add comments/change tags etc. can I stop this, it's agitiating
[17:37] <sproaty> seems a bit silly from the code/logic side of things to be emailed about actions I perform
[17:38] <mrevell> sproaty,
[17:38] <sproaty> sorry, I meant in regards to bugs.
[17:39] <mrevell> sproaty, We're introducing improved configuration options for what email you receive. gmb or deryck will know when that's gonna be available
[17:39] <mrevell> either of you around?
[17:39] <sproaty> very nice :)
[17:40] <sproaty> it's cool to know it's in the making, it doesn't bother me that much (only a bit :P)
[17:51] <deryck> hi mrevell, sproaty.  Yes, this will be configurable for you, it should be live somewhere in the next 4-6 weeks.
[17:51] <mrevell> thanks deryck
[18:03]  * gmb EoDs. Night all.
[18:21] <sproaty> thanks deryck
[18:21] <deryck> np
[19:10] <shadeslayer> where should i contact if i have a question about paste.ubuntu.com ?
[19:11] <hyperair> jpds might know..
[19:11] <hyperair> is this about how you need to login with your launchpad account in order to download pastes?
[19:12] <shadeslayer> no
[19:12] <hyperair> ah well
[19:12] <hyperair> i'd like to ask that question, really. =)
[19:12] <shadeslayer> hyperair: theres a plasmoid in KDE that we can use to create pastese
[19:12] <shadeslayer> *pastes
[19:12] <hyperair> ah i see.
[19:12] <hyperair> that's nice.
[19:12] <hyperair> and?
[19:12] <shadeslayer> im writing a backend for paste.ubuntu
[19:12] <hyperair> there's a command line alternative pastebinit
[19:12] <shadeslayer> some of them are at : http://websvn.kde.org/trunk/KDE/kdebase/workspace/plasma/generic/dataengines/share/backends/
[19:12] <hyperair> it already uses paste.ubuntu.com
[19:13] <shadeslayer> hyperair: yes but with the plasmoid you can grab text from a irc client and drop it on the plasmoid and pastebin's it
[19:13] <shadeslayer> or drop a file and itll do the needfull
[19:13] <hyperair> i think you're missing my point.
[19:13] <hyperair> pastebinit is open source
[19:13] <shadeslayer> needful
[19:13] <hyperair> you can lift the implementation from there
[19:13] <shadeslayer> i was grepping the script too ;)
[19:14] <hyperair> =)
[19:14] <shadeslayer> but theres no mention of paste.ubuntu in the source.. ill have to look at the lp page
[19:15] <hyperair> shadeslayer: take a look at /etc/pastebin.d/
[19:15] <hyperair> specifically /etc/pastebin.d/paste.ubuntu.com.conf
[19:15] <shadeslayer> oh there..
[19:16] <hyperair> i believe it provides a mapping of pastebinit-specific keys to the form <input> fields
[19:16] <hyperair> and then does a POST request
[19:16] <hyperair> basically, hack open the form and post it?
[19:18] <shadeslayer> hyperair: um.. i lost track.. what are we talking about? plasmoid or script ?
[19:18] <hyperair> you're writing a backend for the plasmoid, right?
[19:18] <hyperair> i'm talking about the pastebinit's implementation, and how you could go about figuring out how to implement the said backend for your plasmoid
[19:19] <shadeslayer> oic
[19:19] <shadeslayer> well.. the backend can be written in ruby/JS/python i think... i chose JS
[19:19] <hyperair> could probably even do a bash script using curl to handle it, really.
[19:20] <hyperair> i dunno about js running out of the browser, but with python you could practically lift the entire pastebinit code and magically gain support for all of pastebinit's backends.
[19:21] <shadeslayer> hmm.... well.. IIRC the pastebin plasmoid dev said his data engines supported JS
[19:23] <shadeslayer> hyperair: http://blog.morpheuz.cc/28/08/2010/updates-on-plasma-land/
[19:24] <shadeslayer> 2nd para
[19:24]  * hyperair shrugs
[19:24] <hyperair> well if you choose to do it with js, good luck. i've never done js outside of a browser =)
[19:24] <shadeslayer> ive never done JS.. ever
[19:25] <hyperair> lol
[19:25] <hyperair> what languages have you done?
[19:25] <shadeslayer> i just learned some bits and pieces from w3schools :P
[19:25] <shadeslayer> hyperair: c++ and qt
[19:29] <hyperair> well time to learn a new language then ^_^
[19:32] <shadeslayer> hyperair: aye :D
[19:32] <shadeslayer> its quite easy tbh
[19:32] <shadeslayer> i mean.. easier after you learn C++ and Qt
[19:32] <hyperair> of course.
[19:33] <hyperair> especially C-like languages
[19:33] <shadeslayer> yep
[19:34] <shadeslayer> stgraber: pokes if your around
[19:34] <shadeslayer> hyperair: btw i couldnt get pastebinit to work with *.pastebin.com ...
[19:35] <shadeslayer> dunno whats the issue
[19:35] <shadeslayer> stgraber: is there a API for paste.ubuntu.com
[19:36] <hyperair> shadeslayer: it's likely that pastebin.com broke its API again.
[19:36] <shadeslayer> hmm
[19:36] <shadeslayer> could be..
[19:36] <hyperair> but really, the so called "API" is really just the form names
[19:36] <hyperair> take out firebug or chrome's something-or-other inspector
[19:36] <hyperair> or just view source
[19:37] <hyperair> and check the names of the fields
[19:37] <hyperair> it's really simple
[19:38] <shadeslayer> hyperair: ill looky tomorrow... sleep has taken over my brain right now :P
[19:38] <hyperair> =)
[19:38] <hyperair> time for me to sleep too
[20:06] <smoser> what happened here:
[20:06] <smoser> $ bzr push lp:~smoser/junk/editbp
[20:06] <smoser> Using default stacking branch /~sathishmanohar/junk/main at lp-74167632:///~smoser/junk
[20:06] <smoser> Created new stacked branch referring to /~sathishmanohar/junk/main.
[20:06] <smoser> that was a fresh bzr init'd repo
[20:07] <shadeslayer> smoser: and thats what the output says
[20:07] <shadeslayer> Created new stacked branch referring to /~sathishmanohar/junk/main. <<
[20:07] <shadeslayer> i should really go to sleep...
[20:07] <smoser> right. thats what confused me.
[20:08] <shadeslayer> smoser: also #bzr
[20:25] <dmpinheiro> hello
[20:28] <dmpinheiro> I lost my password, and the launchpad didn't send me a e-mail with instructions to change it
[20:28] <dmpinheiro> this is happening since yesterday
[20:28] <dmpinheiro> thoughts ?
[20:49] <bilalakhtar> Is there something wrong with malone not closing bugs automatically?
[20:50] <deryck> hi bilalakhtar.  Yes, there's a known bug about this, that's being worked on.  Let me see if I can find the bug number....
[20:53] <deryck> hmmm, maybe I'm thinking of something else.
[20:53] <lifeless> no it exists
[20:54] <lifeless> the fix landed on stable I think
[20:54] <deryck> ok, I couldn't find the bug.
[20:55] <deryck> Was this a malone bug?  Or Soyuz?
[20:55] <lifeless> bug 635524
[20:56] <deryck> ah, there.  thanks!  bilalakhtar ^^
[20:56] <bilalakhtar> Thanks deryck !
[20:56]  * bilalakhtar will leave now
[21:10] <aa_> hi everyone, I think there is an xmlrpc interface for filing bugs in malone (because I read the source) is this documented anywhere?
[21:11] <lifeless> ttps://help.launchpad.net/API
[21:12] <aa_> lifeless: thanks
[21:32] <maxb> Can someone with the necessary magic powers tell me why this project is deactivated? https://edge.launchpad.net/fun3compiler
[21:34] <lifeless> its bare bones
[21:34] <lifeless> fun 3 compiler / fun 3 compiler
[21:34] <lifeless> no driver, no branch on the series, no milestones
[21:34] <maxb> My only interest in it is that it's got a code import which is a testcase for an obscure bzr-svn bug :-)
[21:35] <lifeless> sinzui: oh all-knowing-about-CHR one
[21:35] <lifeless> sinzui: is ok to reactivate this, hand ownership to registry admins ?
[21:35] <lifeless> or even maxb ?
[21:35] <lifeless> there's nothing on the review whiteboard, sadly.
[21:36] <maxb> I am a bit confused why it's called "fun3compiler", given the upstream seems to be called "open64"
[21:36] <maxb> Maybe I should just delete the current import and reregister it under a properly named project record
[21:37] <lifeless> hell yeah
[21:37] <lifeless> sorry, let me express my enthusiasm for clean data in this area.
[21:40]  * sinzui looks
[21:41] <sinzui> lifeless, yes the project can be reactivated and given to anyone.
[21:41] <sinzui> I wish there was a note about why it was deactivated.
[21:42] <lifeless> me too
[21:43] <sinzui> maxb, do you want the project? I suppose the user asked for it to be disabled and no one updated the whiteboard. I paste the question or email into the subject when I disable a project
[21:43] <sinzui> looks like the user experimented with a branch and left
[21:44] <maxb> I think the project name is bogus. It needs to be renamed to "open64" or somesuch
[21:45] <maxb> I don't really care about it, other than it's a testcase for a bzr-svn bug which avoids needing to run bzr-svn on the KDE repo :-)
[21:49] <maxb> sinzui: I think the best thing to do would be to either rename the project to open64 , or leave it deactivated and I will move the import branch to a new project record
[21:50] <sinzui> I can rename it now
[21:52] <sinzui> this is no fun. mab, we need a real admin to change the owner. I can either rename it out of the way, or we precede and I wait for this to be given to ~registry
[21:52] <sinzui> ^maxb
[21:54] <maxb> OK, shall I file a question, then, for the maintainer change, and editing all instances of "fun 3" in the metadata to say "Open64" ?
[21:57] <lifeless> file a Q
[21:58] <sinzui> I really want a take control of this project button, but I think I would be over reaching my powers.
[21:59] <maxb> Doesn't seem unreasonable for that to be in the remit of a registry admin
[21:59] <lifeless> maxb: proprietary projects.
[21:59] <lifeless> maxb: commercial customers : registry admins are on the 'dev' side of our devops coin
[22:00] <lifeless> the set of people to be blamed for a breach/issue in that area is - by policy- as small as possible.
[22:04] <maxb> Should I directly assign my question to the losas?
[22:04] <maxb> oh, no, I can't. Launchpad was lying when it displayed an edit-pencil on that field
[22:04] <maxb> https://answers.edge.launchpad.net/launchpad-registry/+question/125431, anyway
[23:22] <sinzui> max: I think all is done for https://edge.launchpad.net/open64 if you needs any changes ping me or any lp engineer.
[23:29] <lifeless> maxb: ^
[23:29] <maxb> looks good, thanks