[02:14] <micahg> is it a soyuz bug if the build score is based on all the entries in teh changelog and not just the top entry?
[02:16] <wgrant> micahg: No. It's based on the Urgency field in the changes file.
[02:16] <wgrant> micahg: That should be the maximum urgency from all included changelog entries, I believe.
[02:17] <wgrant> But regardless it is not a Soyuz bug.
[02:17] <micahg> wgrant: ah, ok, so it's not a bug
[02:18]  * micahg will just skip the -v on the PPA next time then
[06:37] <spiv> Hmm.  I just did 'resubmit proposal' on a merge proposal without realising that it would have been better (in terms of the email produced at least) to update the description *first*.
[06:37] <spiv> I was expecting it to prompt me to update it, maybe show me a form along the lines of the original form used to file the MP.
[06:41] <StevenK> spiv: Yes, that would be nice.
[06:41] <StevenK> spiv: I've been tripped up with that myself
[07:45] <paddy_> With the ssh key it says paddy@paddy-desktop should it be <launchpad username>@launchpad.net. bzr is not working for me
[07:49] <spiv> paddy_: the name in the key doesn't matter at all
[07:49] <spiv> paddy_: what does 'ssh -v -l <launchpad username> bazaar.launchpad.net' output?  (pastebin it)
[07:51] <paddy_> http://pastebin.com/8K7xrsQn spiv
[07:55] <spiv> paddy_: "#
[07:55] <spiv> Agent admitted failure to sign using the key."
[07:56] <spiv> That's your problem.
[07:56] <spiv> You probably need to run 'ssh-add' or something like that.
[07:59] <paddy_> spiv that worked, thanks
[09:28] <neeraj> Hi, while uploading my package in ppa, I am getting this error msg again and again or two/six packages which I am packaging. Rejected Unable to find sugar-presence-service-0.90_0.90.1.orig.tar.bz2 in upload or distribution. Files specified in DSC are broken or missing, skipping package unpack verification.
[09:28] <neeraj> anyhelp?
[09:28] <bigjools> neeraj: it means you're not uploading the .orig file and it can't find the one you're referencing in the dsc file in the distro or your ppa
[09:30] <neeraj> but the orig file is present in the folder alongside dsc file named sugar-presence-service-0.90_0.90.1.orig.tar.bz2
[09:31] <neeraj>  debuild -S command asked me for it. So I am sure while building the package this orig file was used.
[09:33] <wgrant> neeraj: debuild uses it, but it won't upload it unless you give it the '-sa' option.
[09:37] <neeraj> I can't believe how on earth I didn't tried -sa and keep using -s flag. Wasted hours trying to solve this error. :(
[09:37] <neeraj> wgrant: bigjools thanks :)
[09:43] <neeraj> with -sa flag , I got this msg Source/binary (i.e. mixed) uploads are not allowed.
[09:43] <neeraj> Rejected ^
[09:46] <wgrant> neeraj: You need both -S and -sa
[09:53] <neeraj> Ohh.. wgrant thanks gain. So whenever I will use .orig file while building I have to use both -S and -sa and If I don't then only -S will work.?
[09:54] <glen> hi. can i somehow search for translations for my language across any projects?
[09:55] <glen> i mean i want to know how "somesentence" is translated in rosetta, as i know launchpad has hundreds or project translations
[09:55] <glen> yet i don't have myself a project so it would suggest me
[09:56] <henninge> glen: I am sorry, we don't have that option.
[09:57] <henninge> Also, even if you had a project, you would not see them atm because global suggestions have been deactivated to avoid page timeouts.
[10:18] <glen> yet it does sometimes suggest me translations from other projects, that is disabled now? or it just limits the result by some range?
[12:06] <neeraj> is there a anyway so that we can reduce build time on launchpad. I don't get much time for packaging and can't move ahead without verifying initial packages.
[12:07] <neeraj> *?
[12:07] <wgrant> neeraj: Have you tried using pbuilder locally?
[12:07] <wgrant> You should be testing on your own machine before you upload to Launchpad.
[12:08] <neeraj> I have tested on my own machine but build was failing on launchpad due to some error.
[12:08] <wgrant> Tested with pbuilder, or something else?
[12:09] <wgrant> pbuilder and sbuild ensure a clean build environment, so you can be sure you've got all the right build dependencies set.
[12:09] <neeraj> cbds version unmet denpendency. I build the package using debuild and installed the deb file.
[12:09] <neeraj> Ok reading about pbuilder
[14:47] <berco> Hi
[14:47] <cake_> i cant create a test project, i get an error which says i should reload the page after some time. now after the reload it tells me that url is taken BUT im 100% sure its not, ive picked serveral loong random ones
[14:47] <ogra_ac> hey, any LOSA around ?
[14:48] <berco> Can anyone help me enable "natty" on our PPA?
[14:48] <ogra_ac> berco (TI) has a prob with the TI ppa
[14:48]  * ogra_ac would expect natty to happen automatically there, but apparently it doesnt
[14:50] <berco> TI PPA @ https://launchpad.net/~tiomap-dev
[14:50] <bigjools> berco: just upload to natty
[14:50] <zyga> are natty chroots for package buildin expect to fail?
[14:50] <berco> bigjools: nothing needed? I remember my package got rejected last week
[14:51] <bigjools> berco: I was not around last week, what was the rejection?
[14:51] <bigjools> AFAIK it should work
[14:51] <berco> bigjools: I need to try again as I deleted the email...
[14:52] <bigjools> ok let me know
[14:54] <berco> bigjools: one other question I had last week was if I can list the distributions that I support in my changelog or if only one is allowed.
[14:54] <berco> for instance, is this allowed in the debian/changelog: titiler-memmgr (0.24.11-0ubuntu1) maverick natty; urgency=low
[14:55] <bigjools> berco: no, LP only supports a single target series
[14:55] <bigjools> but once it's built you can copy it between series if you don't need to rebuild
[14:55] <bigjools> otherwise you need to upload different versions to different series
[14:56] <berco> ok, thanks
[14:56] <bigjools> let me know if this FAQ explains it adequately: https://answers.launchpad.net/soyuz/+faq/1371
[14:59] <berco> bigjools: I think the FAQ is clear enough, maybe just need to add "distro series" in the title as when I was looking at the debian policy they call this field "distribution".
[15:00] <bigjools> berco: ok thanks for the feedback
[15:00] <berco> bigjools: np
[15:00] <bigjools> fixed :)
[15:43] <berco> bigjools: looks like I have an issue uploading to the PPA. Might be related to our internal network, I'm checking
[15:44] <bigjools> berco: what happens?
[15:46] <berco> bigjools: when I do the dput, I have "write failed: Broken pipe" message
[15:46] <bigjools> berco: ftp or sftp?
[15:47] <berco> bigjools: sftp
[15:47] <bigjools> berco: are you using maverick?
[15:47] <berco> bigjools: I'm still on Lucid on my PC machine
[15:47] <berco> can it explain?
[15:47] <bigjools> ok that should be ok - there's a known problem with the maverick dput over sftp
[15:48] <bigjools> have you used sftp before?
[15:48] <bigjools> and is your public key on your account and your account referenced in the "login" dput conf?
[15:48] <berco> bigjools: yes, all the time when uploading to our PPA on Launchpad
[15:49] <berco> bigjools: however, this is first time I try on this particular PPA (ti-omap-private)
[15:50] <bigjools> not sure what's up then
[15:50] <berco> bigjools: I just verified my dput.cf file and it has my login
[15:50] <berco> what about the public key, I forgot what I need to check here
[15:50] <berco> ?
[15:50] <bigjools> the service is up and I can ssh it (although it correctly says I can't get a shell)
[15:51] <bigjools> your ssh key needs to be associated with the account you're sftp-ing to
[15:53] <berco> bigjools: can you help me verify this latter item please?
[15:54] <berco> I'mnot confident I have it right
[15:54] <bigjools> berco: you can do it yourself, just visit the account page in Launchpad
[15:54] <berco> bigjools: on my account I can see the PPA subscription
[15:54] <berco> bigjools: so is that mean it's all good?
[15:55] <bigjools> there's a section mid-right of the page "SSH keys"
[15:55] <berco> yep, I see this section
[15:55] <bigjools> https://edge.launchpad.net/people/+me/+sshkeys
[15:55] <bigjools> should show the keys
[15:55] <bigjools> make sure the account is the same as the one in the "login =" section of the dput.cf you're using
[16:02] <berco> bigjools: the information shown at https://edge.launchpad.net/people/+me/+sshkeys is exactly what I have in my ~/.ssh/id_rsa.pub
[16:07] <bigjools> berco: ok, what happens if you ssh <login-name-from-dput>@ppa.launchpad.net ?
[16:24] <maxb> Incidentally I think I've figured out the dput hang over sftp on maverick - I'll have a go at fixing bzrlib tonight
[16:31] <berco> bigjools: ssh berco@ppa.launchpad.net
[16:31] <berco> No shells on this server.
[16:31] <berco> Connection to ppa.launchpad.net closed.
[16:32] <berco> bigjools: sorry for the delay but I just tried on my colleague's machine and it worked. So I will try to restart my PC.
[16:33]  * berco going for a reboot
[16:56] <berco> bigjools: I've been able to upload. Package has been accepted on launchpad but my dput command never returns on my PC. I wonder if there's an issue with corscrew as I'm behind a firewall and killing it will allow the dput command to return
[17:04] <bigjools> berco: there's a known regression with sftp from maverick where it hangs at the end
[17:04] <bigjools> other than that I don't know of any issues
[17:04] <bigjools> (sorry was OTP)
[17:05] <berco> bigjools: ok, thanks for the update. So looks like everything looks as good as it can be :)
[17:05] <berco> bigjools: thanks for your precious help
[17:06] <bigjools> berco: no worries, glad to help
[19:02] <lifeless> fta: hi
[19:02] <fta> lifeless, hi
[19:02] <lifeless> when the dashboard script crashes
[19:02] <lifeless> what does it look like
[19:03] <lifeless> I mean, how can I tell if I've made it fall down go boom
[19:03] <fta> i get a py stack with an html page containing an oops
[19:03] <fta> let me see if i still have some logs
[19:03] <lifeless> on the console or in a log file or in one of the html outputs ?
[19:04] <lifeless> fta: I'm running it here to qa this patch
[19:04] <lifeless> fta: I'm up to batch size 50 without error
[19:04] <fta> good
[19:05] <fta> (if it lasts)
[19:05] <lifeless> well, its a code change to be more sensible
[19:06] <fta> lifeless, here is one: http://paste.ubuntu.com/528850/
[19:07] <lifeless> fta: so thats shown on the console that your shell script is running in ?
[19:07] <fta> yes, the py script is called by a shell script (several times as mentioned in the bug) itself run by cron
[19:08] <lifeless> ok
[19:08] <lifeless> thats what I was asking - where to look for errors :)
[19:08] <fta> i get errors in my mailbox
[19:08] <lifeless> (I know what the errors look like :P)
[19:08] <fta> i said in the bug nothing is expected on stdout
[19:08] <fta> except py or lp errors
[19:08] <paddy_> how do i unassign my self to a bug?
[19:09] <lifeless> paddy_: click the yellow icon to the right of your name in the table at the time - in the 'assignee' column. Then click 'unassign me'.
[19:09] <lifeless> fta: 100 works.
[19:09] <fta> lifeless, \o/
[19:13] <fta> try the xorg-edgers ppa too, it's quite big: http://sarvatt.com/xorg-edgers/
[19:13] <lifeless> 200 works
[19:14] <lifeless> so how does that look ? '$BIN $OPTS xorg-edgers' ?
[19:14] <fta> view source shows: <!-- args line: -g -r xorg-edgers/ppa ubuntu-x-swat/x-updates -->
[19:15] <lifeless> trying
[19:16] <fta> i don't know if anyone else is use it
[19:17] <fta> also, you should disable the cache, otherwise, there's not much to poll and you'll never hit your limit
[19:18] <lifeless> ahh
[19:18] <lifeless> 200 on xorg broke
[19:18] <lifeless> oh
[19:18] <fta> maybe for mine too (if you drop the cache)
[19:18] <lifeless> deploy
[19:19] <lifeless> HTTP Error 503: Service Unavailable
[19:19] <lifeless> new code landing on qastaging
[19:19] <fta> o
[19:19] <fta> h
[19:21] <lifeless> where does the cache get stored ?
[19:22] <lifeless> found it
[19:22] <lifeless> running a full run, all the ppas including xorg-edgers, empty cache
[19:31] <lifeless> ok the xorg-edgers one died with the 200 size query
[19:31] <lifeless> fta: however I think it will be tolerable for you for a while, and we can come back later and make it faster still.
[19:36] <lifeless> fta: its in rev 11888
[19:37] <lifeless> fta: so when launchpad.net shows that in the bottom right of the page, you should get a performance boost
[19:37] <fta> lifeless, ok, excellent. thanks!
[19:37] <fta> lifeless, which chunk size do you recommend?
[19:38] <lifeless> fta: the largest that works reliably :)
[19:38] <lifeless> I don't know what that figure will be
[22:07] <lifeless> fta: we're deploying the fix now
[22:07] <lifeless> fta: if you're around in a bit it should be usable
[22:22] <paultag> LP is ooping on me a whole lot, is this already been reported?
[22:23] <paultag> If not, I've been able to have it OOPS on me lots. Here's the error codes ( so far ) -- http://pastebin.com/JvmF6fwP
[22:23] <cody-somerville> paultag, Reported. I'm told the're working to fix it now.
[22:24] <paultag> cody-somerville, awesome. Thanks so much :)
[22:25] <lifeless> fixed
[22:26] <lifeless> fta: please be trying the slow api again now
[22:28] <fta> lifeless, ok. excellent. moved to batches of 50. i'll let you know.
[22:56] <lifeless> fta: how did it go ?
[22:58] <fta> lifeless, seems ok.
[22:59] <lifeless> \o/
[23:02] <barry> lifeless: https://launchpad.net/~pythoneers/+archive/py27stack4/+packages
[23:04] <lifeless> barry: large ppa ?
[23:05] <barry> it does have a lot of packages.  i was actually trying to cull them, but kept getting the oops
[23:05] <lifeless> barry: when did you start getting the oops
[23:05] <barry> an hour or so ago
[23:05] <lifeless> and it was working before that ?
[23:06] <lifeless> when did you last see it work ?
[23:06] <barry> lifeless: yesterday
[23:06] <lifeless> ok
[23:06] <lifeless> so its probably a regression in 11888
[23:06] <lifeless> hmm
[23:06] <lifeless> grumble.
[23:06] <barry> dang
[23:07] <lifeless> though https://bugs.edge.launchpad.net/soyuz/+bug/672371
[23:08] <lifeless> when the oops comes through I'll have a peek
[23:08] <lifeless> till then, lunch
[23:08] <barry> lifeless: thanks.  i'' be breaking for dinner soon, and i'll subscribe to that bug