[00:44] <wolfy1339> how do i create a local branch to later upload it to launchpad?
[00:46] <benonsoftware> wolfy1339: 'bzr init' will create a local branch.
[00:46] <wolfy1339> ok
[00:49] <wolfy1339> i get this error:  [Errno 38] Function not implemented: '/media/wolfy1339/SDXC/Programming/<projectname>/.bzr'
[00:53] <wgrant> wolfy1339: What's the traceback?
[00:53] <wgrant> Also, given the path I'm assuming that's on some weird filesystem like exFAT.
[00:54] <wolfy1339> traceback: http://pastebin.com/U9Syczxk
[00:54] <wolfy1339> and yes it's exfat
[00:55] <wgrant> I don't know how good the exFAT FUSE driver is nowadays...
[01:00] <wgrant> The driver doesn't implement chmod
[01:01] <wgrant> Other filesystems that don't support UNIX file modes usually EPERM, EACCES, or just do nothing
[01:01] <wgrant> bzr handles those cases, but it doesn't expect an ENOSYS.
[01:01] <wgrant> You can probably hack around it by adding ENOSYS to the list with EPERM and EACCESS in bzrlib/osutils.py's chmod_if_possible function
[01:08] <wgrant> wolfy1339: https://groups.google.com/forum/#!topic/exfat/vqPCwJnA_Fo suggests that the next release of exfat-fuse fixes this.
[01:14] <ekristen> why can’t I copy packages from here into a PPA? https://launchpad.net/ubuntu/+source/volatility/2.3.1-1
[01:22] <wgrant> ekristen: You can use the copy-package tool from lp:ubuntu-archive-tools to do that.
[01:22] <wgrant> But there's no web UI for it.
[01:23] <ekristen> wgrant: I’m ok with that
[01:23] <ekristen> any docs you can point me to?
[01:24] <wgrant> The --help is quite usable.
[01:24] <ekristen> trying to find and install it
[01:25] <wgrant> But something like 'copy-package -s trusty --to-ppa=wgrant --to-ppa-name=experimental -b --to-suite=saucy volatility'
[01:25] <ekristen> wgrant: I’ll definitely use the help as soon as I can figure out how to install the tool
[01:26] <wgrant> ekristen: I just have a checkout of lp:ubuntu-archive-tools and symlink relevant bits into ~/bin
[01:26] <ekristen> ah
[03:36] <olly> hi, i have a question about translation imports in launchpad
[03:37] <olly> the pot files gets imported automatically, but all the po files end up in the queue in "Needs Review" state - is that expected?
[03:37] <olly> there's only one possible template in the dropdown, so it seems it should be able to see where to import them to without having to be told
[03:38] <olly> I mean "pot file" (there's just one template)
[03:38] <olly> this is for "survex" BTW
[12:48] <Delfino1983> hello can you delete my key gpg my personal accoun
[12:50] <tsimpson> Delfino1983: you can deactivate it from https://launchpad.net/~/+editpgpkeys
[12:50] <Delfino1983> tsimpson ok thanks
[12:56] <Delfino1983> delete keys gpg!?
[12:57] <tsimpson> if you want them really deleted from launchpad, you're probably going to have to ask in https://answers.launchpad.net/launchpad
[13:44] <wgrant> Delfino1983: Why do you want to delete them?
[13:46] <Delfino1983> change S.O.Linux
[13:46] <wgrant> I don't quite understand what you mean.
[13:50] <Delfino1983> because I do not want more work cn ubuntu
[13:50] <wgrant> You can remove your Launchpad account at the bottom of https://launchpad.net/~/+edit.
[22:16] <pohutukawa> wgrant: thumper just told me to ping you on a package build problem on launchpad
[23:12] <wgrant> pohutukawa: Hi
[23:13] <pohutukawa> wgrant: Hi
[23:13] <pohutukawa> thumper has told me that you might be able to help
[23:14] <pohutukawa> a package build on launchpad fails
[23:14] <pohutukawa> https://launchpadlibrarian.net/162667429/buildlog_ubuntu-trusty-amd64.libsodium_0.4.5-0~trusty4_FAILEDTOBUILD.txt.gz
[23:14] <pohutukawa> somehow it seems like the pkg-config files do not get installed
[23:15] <pohutukawa> is that something where you could potentially help in finding out how to fix it?
[23:15] <pohutukawa> it builds fine on local machine
[23:15] <wgrant> pohutukawa: How were you building it locally?
[23:16] <pohutukawa> wait a sec ...
[23:17] <pohutukawa> wgrant: sudo dpkg-buildpackage -rfakeroot -b
[23:17] <pohutukawa> after apt-get source
[23:17] <wgrant> pohutukawa: Try with -B instead of -b
[23:17] <wgrant> -b builds both the architecture-dependent and architecture-independent binaries
[23:17] <wgrant> But Launchpad builds on multiple architectures, so it only builds the architecture-indepdendent binaries on one: i386.
[23:17] <wgrant> So the amd64 builds run with -B, not -b.
[23:18] <pohutukawa> let me try locally
[23:21] <pohutukawa> wgrant: well, it did build again fine on my own machine with -B
[23:21] <pohutukawa> the problem is that it won't run through on launchpad
[23:21] <pohutukawa> so there seems to be something different
[23:22] <wgrant> pohutukawa: Are you building in a clean chroot?
[23:22] <wgrant> Using pbuilder or sbuild
[23:22] <pohutukawa> no, just on the vanilla machine
[23:22] <wgrant> You're probably missing some build dependencies.
[23:22] <wgrant> Try using pbuilder or sbuild to get a clean environment.
[23:22] <wgrant> "checking for pkg-config... no"
[23:22] <pohutukawa> It's just that the package in the PPA didn't get built, and I've provided a patch that I thought should fix it
[23:22] <pohutukawa> but the maintainer can't get it to build himself
[23:23] <wgrant> pkg-config isn't being installed, because you're not Build-Depending on it.
[23:24] <pohutukawa> so do you reckon it could be "easily" fixed when just adding "pkg-config" to the dependencies of the package?
[23:24] <wgrant> Probably if you add it to the Build-Depends field, yeah
[23:24] <wgrant> But you should be test building locally
[23:24] <wgrant> In a clean environment.
[23:27] <pohutukawa> wgrant: thanks for the input
[23:27] <pohutukawa> I'll radio it on to the maintainer
[23:28] <pohutukawa> so I guess if it's in the Build-Depends field, then the launchpad builder will provide for it ...
[23:31] <wgrant> pohutukawa: The Build-Depends field tells the build infrastructure what to install before building the package.
[23:32] <pohutukawa> that's what I thought. thanks for confirming.