[04:51] <sdn3rd> if I dput source.changes to my personal PPA
[04:51] <sdn3rd> how long before I see it/
[04:52] <sdn3rd> I got it signed and all that jazz in my name
[04:57] <wgrant> sdn3rd: You'll receive an email within a couple of minutes if it was correctly signed.
[05:22] <sdn3rd> mixed source/binary, I have to remove all .tar.gz's ?
[05:23] <wgrant> sdn3rd: You need to remove the .debs, by building with 'debuild -S'
[05:23] <wgrant> Launchpad does not permit binary uploads.
[05:24] <sdn3rd> oh
[05:32] <sdn3rd> wgrant: once it's accepted how long before its on my ppa?
[05:32] <sdn3rd> nvm
[11:17] <saiarcot895> I've had a few PPA builds fail within minutes with no build log; https://launchpad.net/~saiarcot895/+archive/chromium-dev/+build/5398378, https://launchpad.net/~saiarcot895/+archive/chromium-dev/+build/5398380, https://launchpad.net/~saiarcot895/+archive/chromium-dev/+build/5398386
[11:23] <cjwatson> wgrant: Is saiarcot895's problem above perhaps a bug in failure counting?  At least in the first case, buildd-manager tried to dispatch it to menkib, which failed to resume twice, and then buildd-manager apparently failed the build and tried a different one.
[13:53] <dobey> is internet in dallas really so bad right now?
[17:31] <sdn3rd> I added a PPA I made last night and now I can't seem to purge it, I have tried ppa-purge etc and apt is still trying to download it
[17:31] <sdn3rd> how do I manually delete out a PPA by hand?
[17:31] <cjwatson> You'll find it somewhere in /etc/apt/sources.list or /etc/apt/sources.list.d/*
[17:31] <sdn3rd> nvm
[17:31] <sdn3rd> yeah
[17:31] <sdn3rd> I justg found it
[17:31] <cjwatson> stick a # at the front of the relevant lines and sudo apt-get update
[17:32] <sdn3rd> cjwatson: question, since usage of Fork in expect requires tcl to not be built with threading enabled, is there a toggle switch for getting an a non-threaded tcl?
[17:33] <sdn3rd> you're actually the package maintainer for the TCL I built without threads :)
[17:33] <cjwatson> No I'm not
[17:33] <cjwatson> I may have uploaded it last for some minor change, but I don't maintain anything Tclish
[17:33] <sdn3rd> oh ok
[17:33] <cjwatson> I'm afraid I don't know much about Tcl; whatever change I made would have been a drive-by kind of thing
[17:34] <sdn3rd> hehe fair enough
[17:36] <sdn3rd> ok last question, how can I increment a build so my change in my PPA is prefered over the current package?
[17:41] <cjwatson> sdn3rd: https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#versioning
[19:47] <Eduard_Munteanu> Does bzr use secure transport, e.g. https/ssh, by default?
[19:59] <dobey> default is local, otherwise it's what you specify in the argument to the branch or push commands
[19:59] <dobey> and #bzr is the channel for bzr, this channel is about launchpad.net :)
[20:09] <saiarcot895> Another failed build lasting minutes without log: https://launchpad.net/~saiarcot895/+archive/flightgear-edge/+build/5417943
[20:11] <Eduard_Munteanu> dobey: yeah, I was wondering about lp: stuff
[20:12] <Eduard_Munteanu> I guess I should use bzr+ssh for getting stuff securely from Launchpad.
[20:14] <dobey> Eduard_Munteanu: lp: uses ssh if you have "logged in" with bzr lp-login and have your ssh key set on launchpad
[20:16] <dobey> Eduard_Munteanu: lp: falls back to http if you're not logged in (i don't recall if it's https or not), and it says so when it does
[20:16] <Eduard_Munteanu> dobey: I see. Can I just add a ssh key on my account, without login on the bzr side? I want to check out from a remote machine.
[20:17] <dobey> Eduard_Munteanu: you need bzr lp-login so it knows what your launchpad username is. you can set it in the config file instead, but that's all it does (ignore the command name being lp-login as it doesn't actually involve logging in to the server)
[20:17] <Eduard_Munteanu> Oh, ok, so I don't need to provide a password.
[20:17] <Eduard_Munteanu> Thanks.
[20:23] <Eduard_Munteanu> Can I just get a tarball from a code repository, through the web interface?
[20:24] <dobey> probably, but i'm not sure exactly how
[20:24] <Eduard_Munteanu> Oh, wait, I found it...
[20:25] <Eduard_Munteanu> view revision -> download tarball
[20:48] <Eduard_Munteanu> Are projects in a group vetted by the maintainer of the group?
[20:49] <Eduard_Munteanu> I'm looking at https://launchpad.net/openobject and I'm not sure all of those go through some minimal approval.
[20:53] <dobey> not initially. a project group owner might go through and weed out things that aren't part of the group if they want, but pretty much anyone can say their project is under any existing project group.
[20:54] <Eduard_Munteanu> I see, thanks.
[20:55] <Eduard_Munteanu> I can identify them by URL it seems, e.g. the tarball url: https://bazaar.launchpad.net/~openerp/openobject-addons/7.0/tarball/9739?start_revid=9739
[20:57] <Eduard_Munteanu> Nice, the archive contents mention the root project name too.
[21:05] <mibofra> hi guys, why I receive this: "The 'run' instruction is forbidden." when I try to add a run line on a recipe?
[21:07] <dobey> because the run instruction is forbidden in recipes on launchpad
[21:07] <dobey> you are not allowed to run arbitrary commands in the recipe
[21:12] <mibofra> oh fantastic
[21:13] <mibofra> dobey, a thing, I've in debian/source/format 3.0 (quilt)
[21:13] <mibofra> but the recipe build the packages with 3.0 (native)
[21:13] <mibofra> how I can set the recipe to build with the same format as indicated in the debian/source/format?
[21:13] <mibofra> *can I
[21:16] <dobey> it should build fine with 3.0 (quilt) assuming what you're building isn't actually native
[21:16] <TheLordOfTime> i htink he's asking how to force it to build with 3.0 (quilt)
[21:16] <TheLordOfTime> because it's creating 3.0 (native), dobey
[21:16] <TheLordOfTime> based on these lines:
[21:16] <TheLordOfTime> [14/01/07 16:13:01] <mibofra> dobey, a thing, I've in debian/source/format 3.0 (quilt)
[21:16] <TheLordOfTime> [14/01/07 16:13:22] <mibofra> but the recipe build the packages with 3.0 (native)
[21:17] <mibofra> yep TheLordOfTime that's my problem
[21:17] <dobey> i think he has 3.0 (quilt) in the tree, but it's actually a native package because it's not building it against an orig.tar.gz
[21:17] <dobey> ie, he's probably trying to build on trusty with the new dpkg which complains about such things by failing
[21:17] <mibofra> dobey, exactly
[21:17] <dobey> but debian/source/format doesn't get overwritten by launchpad
[21:18] <dobey> you can't force building with 3.0 (quilt)
[21:18] <mibofra> so do I have to dput the package?
[21:23] <mibofra> ok I think so
[21:23] <mibofra> see you
[21:48] <thomi> Is there any way to set the deftault target branch for any new MPs on a project to be something other than lp:<projectname> ?
[21:50] <dobey> thomi: not easily. i think it defaults to the branch that your branch is stacked on, and that defaults to the development target, when you do a bzr push under a project
[21:50] <thomi> :(
[21:50] <thomi> ok
[21:50] <thomi> thanks
[23:09] <wgrant> thomi: lp:foo is the development focus, which seems by definition to be where you'd want to merge.
[23:15] <thomi> wgrant: yeah, I agree. I was looking for a workaround for a bad process elsewhere, but I fixed it now, thanks