=== synapt is now known as nate === cpaelzer_ is now known as cpaelzer === lan3y is now known as Laney === Laney is now known as laney [18:43] is launchpad using an enforcing proxy during snap builds? [18:43] a package builds fine locally [18:44] farm build fails: https://launchpadlibrarian.net/610289005/buildlog_snap_ubuntu_jammy_amd64_hare_BUILDING.txt.gz [18:44] Failed to pull source: command ['git', 'clone', '--recursive', 'git://c9x.me/qbe.git', PosixPath('/build/hare/parts/qbe/src')] exited with code 128. [18:45] I've created this package using lp api directly, perhaps I'm missing an attribute somewhere? [18:45] Looking at the API the "allow_internet" attribute is true [18:56] ah, the repo uses git:// [18:56] and not https:// [18:56] in fact upstream has no https support [18:56] oh fun [20:22] zyga[m]: yes, the only way to get external network access is through the proxy. Your build is apparently using the proxy (as evidenced by '"CONNECT c9x.me:9418 HTTP/1.0" 200 534 "-" "-"' in the log) but for some reason failing anyway [20:23] could be a proxy bug since use of unencrypted git:// is kind of uncommon nowadays, not sure [20:23] yes, I've solved it by mirroring the git:// repo on gitlab [20:23] fair enough [20:23] I don't know which is it [20:23] but meh :) [20:23] it works [20:23] (allow_internet means "permit use of the proxy" BTW) [20:23] right [20:24] I was wondering about one more thing [20:24] in my case, snapcraft.yaml is in a small repo [20:24] that pulls in other repos [20:24] is this something that auto-building is meant to work with as well? [20:24] since my small repo won't change all that often [20:24] but the other repos do [20:24] afraid not really, LP doesn't know enough to follow the links [20:24] I can build manually but I was wondering if I'm holding it wrong or if there's a setting I'm missing somewhere [20:25] (and in general it's a pretty hard problem) [20:25] okay, I'll script a periodic build [20:25] yeah, that seems best [20:25] I was looking for "build daily" kind of thing