=== pleia2_ is now known as pleia2 === salem_ is now known as _salem === chihchun_afk is now known as chihchun === JanC_ is now known as JanC === maclin1 is now known as maclin === _salem is now known as salem_ === chihchun is now known as chihchun_afk [13:49] trying to MP a git branch, but I'm not sure what to put into the 'target reference path' field... should it be the checksum of the commit on the target branch? (which doesn't seem to be working) [13:50] kdub, should be branch no? refs/heads/master ? [13:53] xnox, ah, I was just putting the checksum of refs/heads/master in there [13:53] but that seems to work, thanks [13:55] yeah if I ever get a couple of clear days I'm going to rework that [13:55] you can just write "master", although "refs/heads/master" is the full form [13:55] we always meant for that to be a proper picker UI rather than you having to type the branch name [14:01] cjwatson, yeah, might have been clearer, but I'm just happy to have git around [16:02] Hi. Can someone help me with something? Go here, and under Upstream Connections, hit "Register the upstream project" and "Link". Why does the next page say that name is already used? https://launchpad.net/ubuntu/+source/tor [16:04] qengho: there's an inactive project which is registered [16:05] Hrm. [16:05] qengho: you can register now though. [16:05] dobey: Ah! Wow, thanks! [16:05] the inactive project wasn't for tor, i renamed it [17:10] cjwatson: hey, I'm getting build failures for a snap package in https://code.launchpad.net/~3v1n0/+snap/remmina [17:10] cjwatson: the reason is fatal: unable to connect to git.libssh.org: Name or service not known [17:10] looks weird... [17:12] Trevinho: use https:// rather than git:// [17:12] cjwatson: ok, let me see [17:20] cjwatson: also, would be possible to get some git hooks in order to execute scripts before the snapcraft in order, for example, to update the version: * parameter of the snap according to include infos such as the git commit? [17:23] cjwatson: finally... :-), Only https_proxy and http_proxy vars are exported... But also ftp_proxy is needed (to be set to the same value, it works fine if I set it manually on ftp fetching) [17:24] the https trick seems to work tho... although it's slower as I can't use depth 1.. [17:28] Trevinho: I'd rather that the snapcraft people defined that kind of thing [17:28] there's a bug about that [17:29] cjwatson: about the version thing? [17:29] cjwatson: yeah, true... [17:29] https://bugs.launchpad.net/launchpad/+bug/1594794 [17:29] Ubuntu bug 1594794 in Snapcraft "Embedded version required in snapcraft.yaml" [Wishlist,Triaged] [17:29] Trevinho: please file a bug report against launchpad-buildd for ftp_proxy; I believe you're the first person who's needed that [17:29] cjwatson: but also... For example in github + travis, I can have a repo that builds for both git HEAD and last tag, sending to different branches, in lp I've to maintain two repos... [17:30] err no you don't [17:30] you just need a different snap recipe pointing to a different ref in the same repo [17:33] cjwatson: can multiple recipes stay in the sam repo now? :o [17:33] like in different subfolders or what? [17:33] Trevinho: you can have different versions of snapcraft.yaml in different branches [17:36] ah, yeah... So that... It was the same i was thinking too, it's just that sometimes maintaing two versions can be annoying when a script can do things for you :-) [17:38] I don't want to get into LP maintaining its own language of things on top of snapcraft; if the process of building snaps is to become more dynamic then that needs to go in snapcraft itself [17:38] (and of course a script can commit things on multiple branches) [17:50] Hi there, I just ran into a problem building an OpenStack-related package on launchpad, wonder if someone can help? [17:52] Basically the package wants python-pbr>=1.8, but only 0.70 is available in Trusty, so the build fails. [17:52] If I do the build locally, it falls back to getting pbr>=1.8 from PyPI, but launchpad doesn't allow that, apparently. [17:53] so you'll need to backport the newer package into your ppa [17:53] So if I have the right version in my PPA, the build will be able to use that? [17:54] and you should have a build-depends of python-pbr (>= 1.0) (or python3-pbr) [17:54] yes [17:54] OK - and so presumably if I can find a python-pbr>=1.8 for Trusty somewhere else, I can just copy that in? [17:55] well, if the binary packages are arch independent, you could just binary copy the ones from xenial into trusty perhaps (assuming the paths that are installed to are also not version dependent) [17:56] OK, thanks very much for your quick help! [17:56] yeah, the packages are arch independent [17:57] so you can just do a copy of the binaries from the xenial ubuntu archive into your ppa, for trusty [17:58] or even the ones from zesty, which is a bit newer version [18:00] Thanks, I'll try that. [18:13] Sorry, more guidance needed :-) Do you know where I go to copy a binary package from the Ubuntu archive into my PPA? [18:16] i know there is a web page you can do it from. i do not recall the url :) [18:17] https://help.launchpad.net/Packaging/PPA/Copying ? [18:18] nacc, that certainly works when the source is another PPA. But I think not when the source is the Ubuntu archive. [18:18] i think copy-packages can copy from the archive [18:18] neiljerram: ah could be, sorry [18:18] dobey: i think you're right [18:19] Can dput upload a binary package? [18:19] no [18:21] This perhaps: http://askubuntu.com/questions/489564/launchpad-cli-copying-packages [18:21] and i can't recall how i got to the web page with the archive listing and copy option, that one time i actually managed to find it [18:28] It isn't well-advertised for copies from the primary archive because it's hideous with so many packages [18:29] https://launchpad.net/ubuntu/+archive/primary/+copy-packages [18:29] but you're better off using the 'copy-package' program from lp:ubuntu-archive-tools in that case, normally [18:29] (+copy-packages for primary is also rather liable to time out) [18:32] ah, that, yeah [18:41] Thanks cjwatson, I'll try that. === hrybacki is now known as hrybacki____ === salem_ is now known as _salem === JanC_ is now known as JanC [23:58] The last few times I've built snaps the armhf and arm64 seem to be having proxy issues: "Tunnel connection failed: 407 Proxy Authentication Required" [23:58] If I keep retrying eventually they work [23:58] How long do the builds in question take?