[14:31] <pmatulis> can a team set up a private PPA out of the box?
[14:31] <bigjools> pmatulis: no, an admin has to do it
[14:31] <pmatulis> bigjools: thx, anyone in particular?  what is the process?
[14:31] <bigjools> you create the PPA yourself and before using it get the admin to flip the flag
[14:32] <bigjools> just "ping losa" and they'll come a-runnin' :)
[14:32] <pmatulis> bigjools: nice!
[14:32] <bigjools> pmatulis: beware, once private always private though
[14:33] <pmatulis> bigjools: alright
[14:58] <zul> hi guys I am doing the canonical-application-support spec (https://blueprints.edge.launchpad.net/ubuntu/+spec/server-lucid-canonical-application-support) and was wondering if someone could answer a question for me regarding python-svn
[15:00] <mattions> after how long a package uploaded to a personal PPA will show up?
[15:01] <maxb> 5 minutes from upload to initial appearance, usually
[15:01] <bigjools-afk> mattions: usually about 5 minutes at most
[15:01] <jldupont> I keep getting "Unexpected error while decorating: xxx.yyy" when using Bazaar Plugin for Eclipse... any clue?
[15:01] <beuno> verterok, ^
[15:02] <jldupont> anyone?
[15:02] <maxb> This sounds more #bzr than #launchpad territory
[15:02] <noodles775> jldupont: #bzr might have more people...
[15:03] <jldupont> oh yes... sorry guys!
[15:03] <mattions> bigjools-afk: ok thanks. The upload finished like: "Successfully uploaded packages. Not running dinstall." It looks allright no?
[15:03] <bigjools> mattions: it depends, if you didn't sign it or used a key not known to LP it will be ignored
[15:07] <mattions> bigjools: this is the dput output
[15:07] <mattions> http://pastebin.ubuntu.com/329432/
[15:08] <mattions> the key should be ok
[15:09] <bigjools> mattions: it looks ok to me too
[15:09] <mattions> this is the PPA page: https://launchpad.net/~mattions/+archive/neuronvisio
[15:10] <bigjools> yeah I found it
[15:10] <bigjools> let me see if I can find your upload in the logs, one moment
[15:11] <bigjools> mattions: can you paste your dput.cf
[15:12] <mattions> http://pastebin.ubuntu.com/329437/
[15:13] <bigjools> mattions: I can't see your upload in the logs at all
[15:14] <bigjools> but your output doesn't match your dput.cf
[15:15] <mattions> well
[15:15] <mattions> I have no clue
[15:16] <mattions> I prepare the package using stdeb
[15:16] <mattions> then going into the directory
[15:16] <mattions> and debuild -S -sa
[15:16] <bigjools> mattions: it says "Upload package to host ubuntu" but your dput section is called "neuronvisio-ppa"
[15:16] <bigjools> what dput command line are you using?
[15:16] <mattions> I ran two
[15:17] <mattions> the first one was wrong
[15:17] <mattions> didn't put the ppa)
[15:17] <mattions> this is the second one:
[15:17] <mattions> http://pastebin.ubuntu.com/329441/
[15:18] <mattions> if I re-run it now I'm getting this that is quite ok : http://pastebin.ubuntu.com/329442/
[15:18] <bigjools> mattions: ah I see the problem
[15:19] <mattions> enlight me
[15:19] <bigjools> ~mattions/neuronvisio/ubuntu/ should be ~mattions/ubuntu/neuronvisio
[15:19] <mattions> this guy here is wrong so: https://help.launchpad.net/Packaging/PPA/Uploading
[15:20] <bigjools> mattions: sorry I am wrong
[15:20] <mattions> some tool is lying us!
[15:21] <bigjools> hmmm
[15:21] <mattions> one thing: the mail used as manteiner in the package is different from the one used to sign the package
[15:21] <bigjools> that's ok
[15:21] <mattions> ok.
[15:23] <mattions> now I tried something new. I followed the instruction on the launchpad PPA http://pastebin.ubuntu.com/329447/
[15:24] <bigjools> mattions: ok I found your upload log
[15:24] <mattions> timestamp?
[15:24] <bigjools> 2009-11-27 15:10:17
[15:24] <bigjools> it was rejected
[15:24] <bigjools> Unable to find distroseries: unstable
[15:24] <mattions> ah here we go
[15:24] <bigjools> it sent email to your gmail
[15:25] <mattions> wow
[15:25] <mattions> didn't check
[15:25] <bigjools> the earlier upload has vanished though, how odd
[15:25] <mattions> my bad
[15:25] <bigjools> ok :)
[15:26] <mattions> bigjools: distribution can be only jaunty or karmic?
[15:26] <mattions> not ubuntu or debian?
[15:27] <bigjools> any PPA-supported series
[15:27] <bigjools> Ubuntu series, that is
[15:27] <bigjools> mattions: you can override the series with the upload path though
[15:27] <mattions> how?
[15:28] <bigjools> mattions: ~mattions/neuronvisio/ubuntu/karmic for example
[15:28] <mattions> how can I put more than one?
[15:28] <mattions> let's say karmic and jaunty?
[15:28] <bigjools> you can't do that
[15:29] <bigjools> you can use the copy-packages feature to copy between series
[15:29] <bigjools> but you can't rebuild for the other series if you do that
[15:29] <mattions> where I can read this stuff?
[15:29] <bigjools> if it's not in the same place you were already looking then it doesn't exist :(
[15:30] <mattions> how do you know so? did you write it?
[15:31] <bigjools> yes, I am a developer on the project
[15:31] <mattions> cool!
[15:32] <mattions> bigjools: got another problem. I change the upload path
[15:36] <mattions> bigjools: if the package was rejected
[15:36] <mattions> why dput things is nicely uploaded?
[15:37] <bigjools> mattions: because uploading is separate to the processing of the upload
[15:37] <bigjools> dput uses FTP
[15:38] <bigjools> at some point in the future we hope to use ssh-based uploads which will give more immediate feedback
[15:39] <mattions> Now what I can do next?
[15:39] <mattions> it says it happily uploaded the package
[15:39] <mattions> but the package was rejected
[15:39] <mattions> I modified the path so it should go on karmic
[15:40] <mattions> if I tried too upload it just doesn't do it.
[15:40] <mattions> Do you suggest delete the package and the reuploaded?
[15:42] <cocooncrash> Hi, I can't seem to create merge requests via email anymore
[15:43] <cocooncrash> I'm using Bazaar 2.0.0, and bzr send --no-bundle --no-patch to merge@code.launchpad.net
[15:43] <cocooncrash> I get an email response saying "Your email did not contain a merge directive. Please resend your email with
[15:43] <cocooncrash> the merge directive attached."
[15:44] <cocooncrash> My email definitely has an attachment, and is signed.
[15:45] <bigjools> mattions: dput -f to force the same upload
[15:45]  * popey wonders how far and wide tht mail to launchpad-users is to be spread
[15:45]  * bigjools 's email server blew up 2 days ago so hasn't seen it yet
[15:46] <popey> https://lists.launchpad.net/launchpad-users/msg05649.html
[15:46] <popey> free license for balsamiq mockups
[15:46] <bigjools> lol
[15:48] <jml> popey, damage control procedures have been engaged
[15:48] <popey> yanking the mail?
[15:48] <popey> or voiding the code?
[15:48] <popey> oh, i see
[15:48] <popey> the key has been removed from the archive
[15:48] <popey> nice
[15:48] <popey> :)
[15:49] <bigjools> poor old beuno
[15:51] <beuno> popey, :(
[15:51]  * popey hugs beuno 
[15:55] <mattions> bigjools: victory
[15:55] <bigjools> \o/
[15:55] <bigjools> congrats
[15:58] <mattions> thanks for the help
[15:59] <mattions> now I set the distro properly
[15:59] <mattions> however the copy distro is intriguing
[16:02] <bigjools> you have 2 options if you want the same package in multiple distro series
[16:02] <bigjools> 1. upload to the older series and copy with binaries to the newer
[16:02] <bigjools> 2. upload a different version to the newer series so it gets rebuilt on that series
[16:05] <mattions> older series of what?
[16:12] <bigjools> mattions: distro series, e.g. jaunty, karmic
[16:13] <mattions> but then I have to upload each time for each series
[16:14] <mattions> I just want to do one and have the support in all of them
[16:14] <bigjools> then you have the 2 options like I described
[16:14] <mattions> let's say to get starte I upload my package to jaunty and karmic in two go.
[16:14] <bigjools> your choice
[16:15] <mattions> so I upload version 2 in karmic
[16:15] <mattions> and also in jaunty the package is rebuilt?
[16:19] <bigjools> you need to decide whether you want the same compiled binary in both series, or whether you need to re-compile for each
[16:20] <bigjools> use option 1 for the former, 2 for the latter
[16:20] <bigjools> you can't have the same version re-compiled in each series
[16:21] <mattions> ok, thanks
[16:29] <pitti> hello all
[16:29] <pitti> any LOSA around? I was asked to rename a recently created project, but this requires some admin love
[16:30] <mthaddon> pitti: sure
[16:30] <pitti> in particular, https://launchpad.net/work-items-tracker should be lp-work-items-tracker or launchpad-work-items-tracker (whatever the naming convention is)
[16:30] <pitti> mthaddon: hey, how are you?
[16:30] <mthaddon> hi pitti
[16:31] <mthaddon> pitti: rename done
[16:33] <pitti> mthaddon: cool, thank you!
[16:33] <mthaddon> np
[17:37] <Imperion> why...
[17:37] <Imperion> is...
[17:37] <Imperion> launchpad...
[17:37] <Imperion> so...
[17:37] <Imperion> SLOW
[17:37] <Imperion> today?
[18:15] <Imperion> um, is there any way I can delete a bug?
[18:16] <beuno> Imperion, not really
[18:16] <Imperion> grumble
[20:31] <ripps> So, since ubuntu is dropping lpia support, will launchpad ppa's be dropping it soon too?
[20:34] <maxb> My guess would be that Launchpad PPAs will mirror the support of the corresponding distroseries - i.e. drop lucid, kept for earlier
[21:07] <Imperion> sigh
[21:07] <Imperion> it's been 5 minutes
[21:07] <Imperion> and I can't open the stupid branches page
[21:08] <Imperion> may $DEITY have mercy on me