[02:01] <poolie> it would be nice if ppas actually gave you an estimate of "if you uploaded now, it would take N hours to build"
[02:01] <poolie> i realize it depends a bit on the package
[02:18] <bdrung> are the daily build turned on again?
[02:18] <bdrung> s/build/builds/
[02:19] <poolie> hi bdrung
[02:19] <bdrung> hi poolie
[02:19] <poolie> is it normal that the "build log" in https://edge.launchpad.net/~bzr/+archive/proposed/+build/1925839 is a small empty box?
[02:20] <bdrung> poolie: it's normal at the beginning. you will see some progress there soon.
[02:20] <bdrung> poolie: just keep pressing f5 :)
[02:22] <wgrant> poolie: That just means there's no log yet. Which means the build hasn't started yet, or buildd-manager is being a bit slow and hasn't retrieved the latest log tail yet.
[02:24] <bdrung> poolie: you can see now something there.
[02:37] <poolie> yep
[02:38] <poolie> there was just more lag than i expected
[02:47] <lifeless> wgrant: a bit slow as opposed to..
[02:48] <wgrant> lifeless: As opposed to what it will be in a few weeks.
[03:52] <poolie> hm, lvm locks up my system again
[04:07] <lifeless> :<
[05:38] <lfaraone> Is the Ubuntu SSO service compatible with launchpad? (if I create a Ubuntu SSO account, can I log in via Launchpad with it?)
[05:40] <spm> lfaraone: launchpad uses the Ubuntu SSO for sso
[05:41] <lfaraone> spm: so it's just branding?
[05:41] <spm> more like hysterical raisons
[05:41] <lfaraone> spm: an Ubuntu SSO account works via the Launchpad Login service?
[05:41] <spm> login.launchpad.net and login.ubuntu.com are the same servers/setup etc
[05:42] <lfaraone> spm: ah, mik
[05:42] <lfaraone> *mk
[05:42] <spm> :-)
[05:42] <spm> so yeah, same same basically.
[07:40] <charringtonjp> I am looking for help setting up a PPA on launchpad. I am experiencing a key related error.
[07:41] <noodles775> charringtonjp: Hi! What's the specific error?
[07:41] <charringtonjp> First the ppa is https://launchpad.net/~chris-harrington-jp/+archive/ppa-awaos
[07:42] <charringtonjp> Help documentation says I can find the key on the overview, but there is no key shown on the page
[07:42] <noodles775> charringtonjp: how recently did you create the PPA? (it takes a while after creating the PPA to generate the key).
[07:42] <charringtonjp> Specifically, documentation here: https://help.launchpad.net/Packaging/PPA#Your PPA's key
[07:42] <charringtonjp> I created it days ago.
[07:42] <noodles775> OK
[07:43] <charringtonjp> On my PC I tried  sudo add-apt-repository ppa:chris-harrington-jp/ppa-awaos
[07:43] <charringtonjp> and got
[07:43] <charringtonjp> Error: can't find signing_key_fingerprint at https://launchpad.net/api/1.0/~chris-harrington-jp/+archive/ppa-awaos
[07:44] <charringtonjp> Trying dput gives me the local success but no package after many hours, error without error or email message syndrome
[07:46] <charringtonjp> Though obviously I haven't signed .changes with the PPA key
[07:47] <noodles775> charringtonjp: it needs to be signed with your own key, not the PPAs.
[07:47] <charringtonjp> OK,
[07:47] <charringtonjp> then I've done that
[07:47] <noodles775> charringtonjp: when did you upload, and what was the package? (I'll check the logs)
[07:48] <charringtonjp> I used the registered key when running debuild -S -sa
[07:48] <charringtonjp> one sec.
[07:49] <charringtonjp> tint2_0.11-0ubuntu1.dsc
[07:49] <charringtonjp> osmo_0.2.10-0awaos1.dsc
[07:49] <charringtonjp> lxlauncher_0.2.1-2.ubuntu3.dsc
[07:50] <charringtonjp> Tried those three. Perhaps a name conflict on two of them?
[07:50] <noodles775> charringtonjp: sorry, hrm, the logs are out of sync... I'll try to get them updated.
[07:51] <charringtonjp> thanks
[07:51] <noodles775> charringtonjp: ok, I can't see those packages mentioned in the logs :/
[07:51] <charringtonjp> OK
[07:51] <charringtonjp> Was running debuild and pbuilder in a VM....network problem?
[07:52] <noodles775> If you saw dput success, should be fine. Just to confirm:
[07:52] <charringtonjp> Actually, I used the -d flag because I got a signing error.....
[07:52] <charringtonjp> but that gave me a success message
[07:52] <noodles775> On your PPA, you can see the "Adding this PPA to your system" section, but when you expand the 'Technical details about this PPA' there is no Signing Key/Fingerprint listed?
[07:53] <charringtonjp> 1 sec
[07:53] <noodles775> Ah, what was the signing error?
[07:53] <charringtonjp> Did not write that down. I'll try again, 1 sec
[07:53] <charringtonjp> was days ago
[07:53] <noodles775> And are you certain you've got the correct key on your VM (ie. the one that is linked with your LP account)?
[07:54] <charringtonjp> Well, I am pretty sure.
[07:54] <charringtonjp> I copied the key from my main (parent) machine to the VM
[07:54] <charringtonjp> exporting and then importing with gpg
[07:55] <charringtonjp> and then setting DEBSIGN_KEYID in ~/.devscripts
[07:55] <noodles775> OK - I'm just asking as 99% of the time, that's the reason for not receiving an email (https://help.launchpad.net/Packaging/UploadErrors), but yeah, that should be fine.
[07:56] <charringtonjp> I am new at this though, so I could be missing something important and basic but less documented
[07:56] <charringtonjp> I do not see  'Technical details about this PPA'
[07:57] <charringtonjp> Under Adding this PPA to your system, it just says "This PPA does not contain any packages yet..."
[07:58] <noodles775> Right.
[08:00] <charringtonjp> Packages install fine locally by the way. Just getting them on Launchpad as the last step is not working.
[08:02] <noodles775> charringtonjp: I'll need to pop out for a bit, but just to summarise: either your PPA hasn't yet had its signing key automatically generated (normally only takes a few hours), or there is something wrong with the upload (I can't see any mention of your packages or PPA in the recent upload logs).
[08:02] <noodles775> StevenK: Could you look a bit further for charringtonjp while I'm afk for a bit? ^^
[08:02] <charringtonjp> Actually I will be afk for about an hour or so, so I'll log back in later.
[08:03] <charringtonjp> And post the error I get without the -d flag on dput
[08:03] <noodles775> Perfect, I'll be back then too.
[08:03] <charringtonjp> Great, thanks for the help.
[08:23] <poolie> fwiw I get "server error" with no oops number trying to update a mp
[09:14] <charringtonjp> noodles775: could not reproduce the dput with -d option error
[09:14] <charringtonjp> Instead I got "Package has already been uploaded to ppa on ppa.launchpad.net"
[09:17] <noodles775> charringtonjp: can you use the -f option with dput (to force the upload again)
[09:18] <charringtonjp> will do, 1 sec
[09:18] <charringtonjp> OK, error reproduced
[09:18] <charringtonjp> Unfortunately most of the error message is in Japanese ;)
[09:19] <noodles775> can you paste it to paste.ubuntu.com (or similar)?
[09:19] <charringtonjp> basically that gpg cannot find "appropriate OpenPGP data"
[09:19] <charringtonjp> last line is
[09:19] <noodles775> OK, so I'd say your package is not being signed correctly...
[09:19] <charringtonjp> "No signature on /var/cache/pbuilder/result/osmo_0.2.10-0awaos1_i386.changes
[09:20] <noodles775> Right
[09:20] <charringtonjp> Copying the gpg key seems to work fine,
[09:21] <noodles775> charringtonjp: did you see https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage (it's hard to find, specifically the options when building).
[09:21] <noodles775> It has a note about explicitly identifying the key id.
[09:22] <charringtonjp> That's why I defined DEBSIGN_KEYID in ~/.devscripts
[09:23] <charringtonjp> and the same key as is registered with my Launchpad account is the only key on the VM.
[09:23] <noodles775> Yes, I know, but that leaves me very puzzled as to why you see "No signature on /var/cache/pbuilder/result/osmo_0.2.10-0awaos1_i386.changes" when running dput.
[09:23] <charringtonjp> yes, it is strange.
[09:23] <charringtonjp> I guess I could try building again with -k
[09:23] <charringtonjp> although the process did work, asked for my passphrase twice etc.
[09:24] <noodles775> charringtonjp: you definitely used -S -sa (and were....
[09:24] <noodles775> right.
[09:24] <charringtonjp> The only thing I can think of
[09:24] <charringtonjp> is that DEBFULLNAME and the name of the key after import are different
[09:25] <charringtonjp> DEBFULLNAME being my name, and the name of the key having "(main key)" in the name.
[09:25] <charringtonjp> That is the reason I had to specificy DEBSIGN_KEYID in the first place
[09:26] <charringtonjp> (DEBFULLNAME as defined in ~/.bashrc)
[09:26] <noodles775> Yes, afaik that shouldn't stop the package from being signed... Hangon, thought:
[09:27] <noodles775> The "/var/cache/pbuilder/result/osmo_0.2.10-0awaos1_i386.changes" is the result of *building* the source package... I should have seen that earlier.
[09:27] <charringtonjp> Aha
[09:27] <noodles775> You should be dput'ing the changes file created by dbuild (ie. the source package)
[09:27] <charringtonjp> I see
[09:28] <noodles775> OK, give that a go and let me know how it goes.
[09:28] <charringtonjp> OK I get it. Launchpad does the building, so why would I try to upload the .changes file created by pbuilder. right.
[09:28] <charringtonjp> I'll give it a go.
[09:28] <noodles775> Exactly.
[09:29] <noodles775> Running it through pbuilder first is a great thing to do... it ensures that you know it builds locally in an environment very similar to that used by Launchpad, so saves you hassle when something is wrong with your package.
[09:30] <charringtonjp> OK, I got a success message
[09:30] <charringtonjp> I tried it with one of the other packages
[09:30] <charringtonjp> One I'm sure I used debuild on because I changed source
[09:31] <noodles775> Great... now wait a few minutes and see if you get an email. If you don't have one in 10 or 15mins, let me know.
[09:31] <charringtonjp> Will do, thanks a bunch!
[09:31] <noodles775> Any time :)
[09:32] <charringtonjp> I'm documenting my experience in a blog. Is it OK if I mention your nick as the one who gave advice?
[09:32] <charringtonjp> ( assuming it works)
[09:33] <charringtonjp> http://awaos.awanowa.jp/en/
[09:33] <noodles775> Sure :)
[09:34] <charringtonjp> Thanks.
[09:36] <charringtonjp> Package is up. Looks like it worked
[09:36] <charringtonjp> Thanks again!
[09:36] <noodles775> Great :D
[12:35] <nigelb> Is there a way to get cia-clients only use report the pushed commits?
[12:36] <nigelb> there seems to be no man page or instructions....
[12:37] <nigelb> jelmer: around?
[12:38] <jelmer> nigelb, hi
[12:38] <nigelb> jelmer: seeing that you wrote the cia plugin, can you help me with my query?
[12:40] <jelmer> nigelb: the help can be found with 'bzr help cia'
[12:40] <jelmer> nigelb: Though to answer your question, there's no way to only report pushed commits.
[12:40] <nigelb> Ah, thanks
[12:40]  * nigelb headdesks.
[12:40] <nigelb> I shoulda thought of bzr hep cia :/
[12:40] <nigelb> I tried every other combination :D
[12:41] <jelmer> nigelb: The problem would be that every time you do a push a revision you generate a new notification; you only commit once.
[12:41] <nigelb> jelmer: true.  I wish LP had something at the server end.
[12:46] <jml> nigelb, me too!
[12:46] <nigelb> jml: is it very hard to do? Or just way down on the list that you folks have?
[12:46] <nigelb> (or both?)
[12:48] <jml> nigelb, getting Launchpad to push real-time computer-readable notifications is non-trivial.
[12:48] <jml> nigelb, but reasonably high up on the list.
[12:48] <nigelb> jml: lack of hands?
[12:48] <nigelb> If so, I don't mind getting my hands dirty if I have to.
[12:49] <nigelb> (but I only know PHP and very little python.  You folks would stab me at the mention of PHP :p)
[12:49] <jml> nigelb, we wouldn't stab you
[12:49] <nigelb> ok, good to know :D
[12:49] <jml> after all, then you'd have *two* problems.
[12:49] <nigelb> hahah
[12:51] <jml> nigelb, lifeless is a better person to ask about the implementation details (he keeps longish NZ hours)
[12:51] <nigelb> yeah, I run into him often.  I'll ask him in his a.m.
[12:51] <jml> nigelb, cool.
[12:52] <nigelb> jml: thanks :)
[12:52] <nigelb> It would be so cool to get cia working :)
[13:29] <seb128> hi
[13:29] <seb128> did any recent launchpad update added restriction on downloads?
[13:30] <seb128> ignore that I think that was a authentification token issue
[13:32] <Laibsch> Hi, I just stumbled across something I felt was interesting.  Take a look at the latest release of gnucash 2.2.9-6 to maverick
[13:32] <Laibsch> https://launchpad.net/ubuntu/+source/gnucash
[13:33] <Laibsch> the changelog and Debian agree this release was made by Micha Lenk, but Launchpad attributes it to Ahmed El-Mahmoudy?
[13:33] <Laibsch> How can that be?
[13:34] <wgrant> Laibsch: He requested the sync.
[13:35] <Laibsch> I see
[13:36] <Laibsch> is that how LP does things now?
[13:36] <wgrant> It's done that for roughtly four and a half years, since Ubuntu started using it.
[13:36] <Laibsch> IIRC it used to be attributed to the one mentioned in the changelog?
[13:36] <Laibsch> really?
[13:36] <Laibsch> Wow
[13:36] <Laibsch> must have been half-asleep, I guess
[13:36] <Laibsch> but something isn't right
[13:37] <Laibsch> the time mentioned is the time of the upload made to Debian
[13:37] <wgrant> Yeha, the way it constructs that line is a little... off.
[13:37] <geser> it probably uses the Changed-By value which gets probably modified when building the .changes file for the sync with the sync requester
[13:37] <wgrant> Well, actually, it's more because sycning is a hack.
[13:38] <wgrant> geser is correct.
[13:38] <wgrant> sync-source.py overrides Changed-By.
[13:38] <Laibsch> OK
[13:38] <Laibsch> just wanted to make sure you know about it
[13:38] <Laibsch> but it seems to have be me not paying attention earlier ;-)
[13:39] <Laibsch> been
[13:42] <askhl> Hi.  Is the keyserver down?
[13:42] <askhl> The PPA key server, that is
[13:44] <noodles775> askhl: the server itself seems fine to me? That is:
[13:44] <noodles775> http://keyserver.ubuntu.com:11371/pks/lookup?search=0x0E83E39A9F811449B50FA6DE9746C699E2A280CD&op=index
[13:44] <noodles775> responds as expected.
[13:44] <noodles775> askhl: or do you mean the script that generates the signing keys for PPAs? What's the issue you're seeing?
[13:45] <askhl> noodles775, trying to add a PPA, and there's an error
[13:45] <askhl> Hang on, I'll take a look again
[15:30] <nessita> good morning! quick question, I have releases 0.98 and 0.99 for this project https://launchpad.net/ubuntu-sso-client, yet the 0.98 is the one offered in the front page. Any ideas why?
[15:32] <salgado> sinzui, can you help nessita?
[15:32] <salgado> I can't see why that's happening
[15:34] <sinzui> nessita, 98 may have a newer timestamp. I do not think it uses debversion
[15:34]  * sinzui looks
[15:34] <nessita> sinzui: I've uploaded 0.98 before than 0.99
[15:35] <nessita> sinzui: so, I would expect timestamp for 0.98 to be older than the one for 0.99
[15:36] <sinzui> https://edge.launchpad.net/ubuntu-sso-client/+download also favours 98
[15:37] <nessita> yeah... any idea why?
[15:37] <nessita> both uploads were made the same day, but 0.98 early in the morning, and 0.99 late in the afternoon
[15:39] <sinzui> nessita, I needs to read the code to see what is happening here. I'll be a few minutes
[15:39] <nessita> sinzui: no problem, I have no rush. Thanks!
[15:45] <sinzui> nessita, I have a suspicion. The date field only accepts a date, and it adds 00:00:00 as the time. So Lp may think both releases happened at the same time. We are getting the first one back
[15:45]  * sinzui peaks at staging db
[15:45] <nessita> sinzui: ouch!
[15:45] <nessita> shall I fill a bug for this?
[15:46] <sinzui> If this is true, I think the fix is easy by adding a sort on version
[15:51] <sinzui> nessita, the time is 00:00:00. I will report a bug to improve the sorting mechanism. This is a trivial change we can get fixed in a few days
[15:51]  * sinzui looks to existing bug first
[15:51] <askhl> noodles775, apologies for running away previously.  As it turned out, a funny proxy was used on the computer in question, and I was confusing it with some previous trouble with timeouts due to the keyserver
[15:52] <askhl> (which hasn't been a problem now otherwise)
[15:52] <noodles775> askhl: ah, thanks for letting me know.
[15:53] <nessita> sinzui: awesome! thanks
[16:46] <shadeslayer> erm are daily builds for maverick turned off?
[16:50] <jml> shadeslayer, https://bugs.edge.launchpad.net/launchpad-code/+bug/617072
[16:50] <shadeslayer> oic
[16:51] <shadeslayer> too bad :(
[16:51] <shadeslayer> btw, i need to add more stuff into commit log of bzr, how do i do that?
[16:52] <shadeslayer> i already closed the commit editor
[17:22] <maxb> shadeslayer: Once a commit has been created, it is immutable.
[17:22] <shadeslayer> hmm
[17:22] <maxb> However, if the commit has not been pushed or merged anywhere else, an option is to uncommit it and commit again
[17:23] <shadeslayer> maxb: how would i do that? bzr uncommit?
[17:23] <maxb> yes
[17:24] <shadeslayer> alright
[18:43] <hexmode> rockstar: got this from one of my daily ppa builds:
[18:43] <hexmode> [ ! -f Makefile ] || /usr/bin/make maintainer-clean
[18:43] <hexmode>  
[18:43] <hexmode> Makefile:358: *** multiple target patterns.  Stop.
[18:43] <hexmode> rockstar: looks like that is sometimes caused by colons in the make-deps
[18:44] <hexmode> and, looking at my copy of the checkout, I don't see that
[18:44] <hexmode> rockstar: finally "bzr build" WORKSFORME on my local machine
[18:44] <hexmode> anyway to find out what is in the Makefile on the build bot?
[18:45] <hexmode> http://launchpadlibrarian.net/54000112/buildlog.txt.gz
[19:25] <infinity0> is it possible to host packages for debian on your launchpad ppa?
[19:27] <lifeless> theres usually an ubuntu version which packages built on will work on Debian, but we don't have Debian specific buildds, sorry.
[19:31] <infinity0> hm, ok well i'm on debian, my dput doesn't support sftp, is there anything else that launchpad supports?
[19:31] <infinity0> i tried https/rsync/scp, none of them worked ("not allowed to execute commands on this server")
[19:32] <infinity0> also, 405 method not allowed
[19:39] <alex88> if i have created a deb file, and want to upload to ppa for the first time..what should i do?
[19:39] <alex88> i've already created the package and added ssh key
[19:42] <nigelb> lifeless: morning.  I see you start early :)
[19:42] <infinity0> alex88, there's instructions on your ppa page
[19:42] <nigelb> lifeless: I was asking earlier about having CIA hook into LP.  How hard would that be?
[19:43]  * nigelb would like to help with that effort if possible.
[19:43] <alex88> well, i have only to rename deb to deb.changes?
[19:43] <lifeless> nigelb: what do you mean
[19:44] <lifeless> and yeah, I am an early riser; today was exceptionally early even for me - 5am.
[19:45] <nigelb> lifeless: I'm talking about CIA bots (CIA.sv), right now we only have it at client side which isn't very ideal.
[19:45] <lifeless> nigelb: go on; I know what cia is etc, but there are many ways they good hook together, so I need to know what one you're thinking of
[19:46] <nigelb> lifeless: I'm thinking of being able to ping cia everytime a trunk branch is updated
[19:46] <nigelb> it would be very useful for projects
[19:46] <nigelb> the client side thingy is irritating because they may never turn up in the trunk anyway
[19:47] <nigelb> while the whole idea is to keep track of commits to the main project repo
[19:47] <lifeless> I'd like us to support a pubsub model for lp
[19:47] <lifeless> which would naturally cover this
[19:47] <lifeless> but you could just use the rss feed today
[19:48] <nigelb> and hook that to a bot? hm, not bad.
[19:48] <lifeless> ask cia.* to subscribe to the rss feed; done.
[19:49] <nigelb> Oh. That's helpful :)
[19:49] <lifeless> of course that won't be instant until we get pubsub in place
[19:49] <lifeless> if you wanted to work on that that would be awesome, but I rather fear its a large stack
[19:49] <nigelb> hm, I remember some conversation about this
[19:49] <nigelb> but at that time I didn't care about it.
[19:50] <lifeless> )
[19:50] <nigelb> I will run rocketfuel on my vm and see how much I can wrap my head around LP
[19:50] <lifeless> ok
[19:51] <nigelb> probably need to first figure out how the thing works :D
[19:52] <lifeless> you've seen the wiki about getting started ?
[19:52] <nigelb> I have it in my bookmarks, yes
[19:58] <alex88> wtf, but to public a package i have to make a change from ubuntu package?
[20:01] <infinity0> alex88: it looks like you don't understand the debian build system
[20:01] <infinity0> there's the original source package, a .orig.tar.gz, a .diff.gz or .debian.tar.gz to apply debian-specific patches, and a .dsc file
[20:02] <infinity0> the .changes  and .deb files are created when you run dpkg-buildpackage over the source package
[20:02] <infinity0> if you don't have the source package you won't have the .changes file
[20:02] <infinity0> so you can't just pick up a deb from somewhere and upload it to your ppa
[20:02] <infinity0> you have to have built it yourself, and got a .changes file
[20:03] <alex88> thank you..i'll have a look
[20:04] <nigelb> lifeless: we don't have the rss feeds yet, do we?
[20:05] <lifeless> yes
[20:05] <nigelb> (I only see rss feeds for announcements and not commits)
[20:05] <lifeless> branch feeds
[20:05]  * nigelb goes to look again
[20:05] <lifeless> "http://feeds.edge.launchpad.net/~lifeless/launchpad/registry/branch.atom"
[20:05] <lifeless> for instance
[20:06] <lifeless> well
[20:06] <nigelb> cant see that from the UI can I?
[20:06] <lifeless> get rid of edge from that url
[20:06] <lifeless> nigelb: depends on your browser
[20:06] <nigelb> hrm, on Firefox?
[20:06] <nigelb> I'm talking about the link
[20:07] <nigelb> I don't see an rss button on the UI for the branch...
[20:08] <lifeless> the link is a rel tag in the page
[20:08] <lifeless> which rss aware browsers show as a 'subscribe' button
[20:10] <nigelb> Ah
[20:11] <nigelb> I see it now :)
[20:20] <alex88> when i delete a ppa, or deactivate pgp key, does them disappear after some time?
[20:35] <lifeless> no
[20:35] <jenkins> hi everyone how do I remove all revisions and the history of a branch? I would like to make the latest revision of https://code.edge.launchpad.net/~ubuntu-manual/ubuntu-manual/maverick to be revision 1. As the branch is getting very bigged as it is derived from previous versions of the manual ?
[20:43] <jenkins> I can't delete the branch as one other branch has shared revisions how do i work out what the linked branch is?
[20:49] <lifeless> jenkins: thats a pretty harmful thing to do
[20:49] <lifeless> jenkins: you'll make it hard for everyone collaborating on it.
[20:50] <infinity0> hey, https://help.launchpad.net/Packaging/PPA#Activating%20a%20PPA tells me i need to active my ppa, but no such link exists on my overview page
[20:51] <jenkins> lifeless:  noone is doing anything on it at the moment, its mostly because we have people with slow internet and we made the mistake of setting it up early on
[21:32] <Eruantalon> Is it normal to have a delay of around 10-15 minutes from new stuff happening in a bug to me getting the e-mail?
[21:38] <mtaylor> the windows bzr explorer walkthrough has no information on how to tell it where/what your ssh key is
[21:38] <thumper> pagent is your friend
[21:39] <thumper> ssh on windows kinda blows
[21:39] <mtaylor> well yeah
[21:39] <mtaylor> ok. so putty set up will get used properly?
[21:41] <mtaylor> thumper: speaking of - it would be great if the first time I logged in on a new box and it redirects me to edge if I didn't have to click login again
[21:41] <mtaylor> just saying
[21:45] <lifeless> mtaylor: we're deleting edge.
[21:45] <lifeless> mtaylor: problem solved
[21:46] <mtaylor> lifeless: woot
[21:48] <jcastro> lifeless: what can I do to get lp #596931 implemented?
[21:48] <jcastro> lifeless: we've wanted it for a long time
[21:48] <lifeless> jcastro: let me have a look
[21:49] <jcastro> lifeless: even if it was one big upstream, like either gnome or debian or something would be a tremendous help
[21:49] <james_w> jcastro: talk to marjo about requesting it through the stakeholder process
[21:51] <jcastro> good idea
[21:53] <lifeless> jcastro: this is huge
[21:54] <lifeless> jcastro: as defined its extremely complicated
[21:54] <lifeless> jcastro: asking in the stakeholder process would make sense.
[21:54] <lifeless> what we need for this is:
[21:54] <lifeless>  - defined API for searching upstreams
[21:54] <lifeless>  - glue into +filebug to make that work
[21:54] <lifeless> the first step needs to be time capped. E.g. searching upstreams in < 0.5sec per query
[21:55] <lifeless> thats going to be nearly impossible given many upstreams bugtrackers
[21:55] <james_w> as a first cut search the tasks on the upstream /in launchpad/ would work
[21:55] <jcastro> in the past we've done an entire import of like, the BTS in lp.
[21:55] <lifeless> so I'd redefine this as
[21:55] <jcastro> if it did that say, once a night
[21:55] <lifeless> search in the matching product on LP for dups
[21:55] <lifeless> which is *easy*
[21:55] <jcastro> then who cares about remotely queuing the remote tracker?
[21:55] <lifeless> and separately we can work on better prepopulation of the upstream products in LP
[21:56] <lifeless> jcastro: james_w: we're saying the same thing. I'm saying though that the bug *as defined* is going to be hard to do well if at all.
[21:56] <lifeless> whomever is the stakeholder should redefine it;)
[21:57]  * jcastro does that
[21:57] <lifeless> its a very small patch to make +filebug look both upstream-in-LP *and* downstream-in-LP.
[21:58] <lifeless> so that bugs on bzr find the ubuntu bugs for it, and vice verca.
[21:58] <lifeless> jcastro: I think you want two bugs.
[21:58] <lifeless> one, search upstream-in-LP in +filebug.
[21:58] <lifeless> two, which is likely a dup, populate-upsream-in-LP
[21:58] <jcastro> right, I swear we've been talking about  this idea for like 3 years
[21:59] <jcastro> I want #2 way more
[22:00] <lifeless> jcastro: so, separate the concerns out. Shove em in the stakeholder process.
[22:01] <lifeless> now, you could do a patch for 1 yourself :) its pretty easy [as such things go :(]
[22:01] <lifeless> for 2, I haven't looked into the bug federation logic yet.
[22:01] <lifeless> so I can't comment. I don't see why it would be harder than 'for bug in X; add-bug-watch' on a given product.