[05:09] <cavedon> hi, is there any way to access the filesystem of a failed PPA build? the build is failing on trusty and saucy for *amd64 only* in something that is architecture independent. Also it is not failing in my trusty amd64 chroot.
[05:09] <wgrant> cavedon: How're you building it locally?
[05:10] <wgrant> If it's only failing on amd64 on Launchpad, chances are that it's a build-arch vs build-indep issue. Try building with 'dpkg-buildpackage -B' locally.
[05:11] <cavedon> hey wgrant: I built with dpkg-buildpackage -b -uc
[05:11] <cavedon> let me try
[05:11] <cavedon> thanks
[05:11] <wgrant> cavedon: -b builds both architecture-dependent and architecture-independent packages, -B builds just arch-dep, and -A just arch-indep.
[05:11] <wgrant> Launchpad builds the arch-indep packages once, on i386.
[05:11] <wgrant> So i386 builds are -b, amd64 builds are -B
[05:12] <cavedon> wgrant, that was it, I reproduced the error locally, thanks you, that explains it, I will fix it, thanks!
[05:12] <wgrant> Excellent
[07:51] <dickelbeck> Help please with git import of https://github.com/KiCAD/kicad-library into bzr repo https://code.launchpad.net/~kicad-testing-committers/kicad/library
[07:52] <dickelbeck> I'd like for it to be updated daily, but it cannot complete the initial import.  This branch started at bzr, went to git where it will be maintained, and now I'd like it mirrored in bzr.
[07:57] <StevenK> This branch is an import of the HEAD branch of the Git repository at https://KiCAD/kicad-library.git.
[07:58] <StevenK> I think you missed part of the URL
[08:03] <dickelbeck> Thanks StevenK, I think the missing ".git" is making the difference.  It is progressing now.  Bye.
[11:27] <dch> hi in a recipe file, I want to over-ride the existing ./debian file from the upstream branch with a custom one. Is this possible?
[11:27] <dch> merge lp~… didn’t seem to work out.
[11:49] <dobey> dch: no, you can't merge. nest might have an override option, but i don't think it does
[11:50] <dch> dobey: thanks, I tried nest-part previously. hmm  any other ideas?
[11:50] <dch> alternatively I can fork, delete the unwanted parts, but that kinda defeats the point of having a common upstream
[11:50] <dobey> dch: is your branch a branch of the upstream trunk, with modifications to debian/?
[11:51] <dobey> dch: or do you have a branch that only has the contents of debian?
[11:51] <dch> dobey: only debian
[11:51] <dch> i.e. just the package parts
[11:52] <dobey> if upstream already contains debian/ then you're really going have to maintain a "fork"  :-/
[11:52] <dobey> or just fix upstream to do the right thing :)
[11:54] <dch> that has been …. problematic
[11:54] <dch> long delays, lots of pushing, then a flurry of grumpy work, then again nothing for months.
[11:55] <wgrant> dch: Why doesn't merge work?
[11:55] <wgrant> You'd need the branch to be an actual branch of trunk, with the changes made to debian/, but that would work.
[11:55] <dch> wgrant: probably because I am completely new to .deb files & lp & bzr. the upstream has a ./debian folder too.
[11:55] <wgrant> But nest-part should also work to replace debian/, IIRC.
[11:56] <wgrant> dch: Right, and I'd consider creating my own branch of the upstream branch, with the relevant changes to debian/ in that branch
[11:56] <wgrant> Then merge that in the recipe.
[11:56] <dch> what a mess ...
[11:56] <wgrant> Howso?
[11:57] <wgrant> But if you don't want to do that, you can probably use nest-part.
[11:57] <wgrant> Ah, apparently not directly.
[11:57] <dch> well the underlying issue is an unresponsive maintainer who needs to be kicked to do stuff, never submits patches upstream, and doesn’t understand what’s being packaged.
[11:58] <dch> I also tried `run rm -rf debian` in between but that isnt going to work on lp anyway.
[11:58] <wgrant> dch: I'm not sure I understand what the problem is with just maintaining a full-tree packaging branch.
[12:01] <dobey> wgrant: maintaining a fork s a pain, epsecially when upstream already has debian/ and does things wrong
[12:02] <dch> well I will log some bugs for the maintainer, and start a new package from scratch.
[12:02] <wgrant> dobey: You have to maintain debian/ whether you use a full-tree or packaging-only branch.
[12:02] <wgrant> There's very little difference in overhead.
[12:03] <wgrant> Full-tree branches just happen to have a lot more files that you never need to touch.
[16:42] <philsf> hi, I have a local bzr branch I created in 2008, and I pushed to launchpad before I found out the format had changed. I bzr upgrad'ed the local branch, but pushing does not upgrade the remote branch, and now I can't build using LP recipes because of format mismatch. How can I upgrade the LP branch?
[17:16] <lfaraone> Is there a way for me to find a user's Launchpad ID given an email address?
[17:18] <lfaraone> nevermind, right.
[17:19] <lfaraone> I want to sync some Launchpad teams with an external database, that is, sync from the database to Launchpad. Would a patch to make this a Launchpad-run cronjob be accepted, or should I just create a role user who is an admin on the relevant projects?
[19:52] <ekristen> I've followed the instructions to upload a .deb to my ppa, dput says it successfully uploaded the packages, but I cannot see it on my ppa
[20:48] <dobey> ekristen: it must be gpg signed with the same key as you have uploaded to launchpad
[20:48] <ekristen> dobey: yeah, it looks like launchpad.net doesn't support uploading .deb files directly
[20:49] <dobey> you can only upload source packages, right
[20:59] <skinkitten_> hi guys I was told menulibre can help me create an icon for the launcher.
[21:00] <skinkitten_> I'm on ubuntu and I'm trying to get eclipse locked in the dock but haven't succeded. can you guys help?
[21:06] <dobey> skinkitten_: #ubuntu is the channel for help about ubuntu
[21:42] <ekristen> I managed to upload a source package, but I needed to change the control file to have some additional dependencies, now when I try and upload it it says "uploaded version has different contents"
[21:50] <StevenK> ekristen: You must bump the version number.
[21:50] <ekristen> ugh
[21:50] <ekristen> ok
[21:52] <ekristen> StevenK: thanks
[21:54] <ekristen> StevenK: that did it, thanks, trying to get it to build properly
[21:54] <StevenK> ekristen: You're welcome
[22:08] <AnnaTrumble> I am looking to purchase a domain that seems to be owned by you guys. How do I go about doing that?
[22:11] <AnnaTrumble> A few of us from my company have been attempting contact with you guys... Is this an effective way to chat?
[22:12] <lifeless> AnnaTrumble: which guys ?
[22:13] <AnnaTrumble> Brittney Roberts and Ross Trumble
[22:16] <AnnaTrumble> Wait, which guys have we attempted contacting? We've been emailing help@launchpad.com
[22:16] <wgrant> We own launchpad.net, but not launchpad.com.
[22:16] <AnnaTrumble> The emails would have been coming from my associates, Ross and Brittney. We haven't received a reply from anyone.
[22:16] <AnnaTrumble> Yes, .net
[22:17] <AnnaTrumble> we've been contacting launchpad.net
[22:18] <AnnaTrumble> Damn, I see that the domain is owned by launchpad.com
[22:19] <AnnaTrumble> Sorry! Wish my employees would have caught that previous
[22:19] <AnnaTrumble> Thanks for your time.
[22:37] <saiarcot895> Not sure if it is just me or what, but are Trusty build logs for Ubuntu packages not accessible? https://launchpad.net/ubuntu/+source/chromium-browser
[22:39] <wgrant> saiarcot895: The trusty packages were copied from saucy, so have no build logs of their own
[22:39] <wgrant> Look for the saucy ones instead.
[22:39] <saiarcot895> wgrant: ah, didn't think about that
[22:39] <StevenK> wgrant: There's a proposed upload with no build logs
[22:39] <StevenK> Oh, which was also copied. Handy.
[22:39] <wgrant> StevenK: That's the saucy security update