[11:04] <cjwatson> popey: hey, do you have any examples of electron-builder snaps that fail to build for networky sorts of reasons on BSI?
[11:04] <cjwatson> popey: elopio filed a bug about one of those a while back, but the GH repository for it is gone
[11:44] <popey> cjwatson: we generally don't hook e-b apps to bsi. Because it doesn't build with a yaml in the root
[12:43] <cjwatson> popey: Can you explain that a bit further?
[13:16] <popey_> cjwatson: sorry for the delay, irccloud-desktop from edge is segfaulting and I'm on 50K/s wifi
[13:16] <popey_> cjwatson: so, electron-builder knows how to build snaps. A single line in the package.json in the root of an electron-builder based project is often enough to spit out a valid snap
[13:16] <popey_> cjwatson: sometimes you need extra stuff like interfaces listed, or stage-packages, but often not.
[13:17] <popey_> cjwatson: internally e-b will build the application with npm/yarn or whatever, and then bundle the built assets into a snap (I think using snapcraft)
[13:18] <popey_> cjwatson: so e-b projects don't actually have a snapcraft.yaml anywhere in their source tree, it gets generated (I think) at build time, and then thrown away.
[13:21] <cjwatson> popey_: Ah, so https://bugs.launchpad.net/launchpad-buildd/+bug/1732811 was an anomaly?
[13:22] <mup> Bug #1732811: glowing-bear fails to build, but it works on container build <launchpad-buildd:Incomplete> <https://launchpad.net/bugs/1732811>
[13:22] <cjwatson> I assumed from that bug that there was some kind of wrapper boilerplate in snapcraft.yaml that called electron-builder.
[13:24] <popey_> yeah, i dunno what it did, we nuked it because it was all broken
[13:24] <popey_> so it could well be an anomoly, I'd close it and we can re-open if we see it again
[13:25] <cjwatson> popey_: OK, would you mind doing that?  Always good to have the user('s team) withdraw rather than the nasty evil maintainer wontfixing :)
[13:25] <cjwatson> popey_: I think my proxy work will likely take care of the specific download problem there in any case
[13:26] <popey> :D
[13:26] <cjwatson> (well, maybe; or else it'll require the same kind of more heroic measures that bloody maven-ant-tasks will)
[13:26] <popey> oh. you've fixed maven? :)
[13:26] <cjwatson> ... sort of, in some cases
[13:27] <cjwatson> maven-ant-tasks is a special snowflake
[13:27] <popey> ah okay.
[13:27] <cjwatson> I have a fix for the general case of stuff that doesn't work with authed proxies
[13:27] <cjwatson> but maven-ant-tasks is terrible and is just ignoring me no matter what I try
[13:27] <cjwatson> I think I must have insulted its ancestors or something
[13:27] <popey> More free software developers should have to live behind proxy servers. This stuff would happen less often.
[13:28] <cjwatson> I do find it astonishing that Java stuff doesn't work right, given the corporate world
[13:28] <popey> yeah
[13:28] <cjwatson> the internet is full of half-complete threads to the effect of "how do I get maven to work behind my proxy" that sort of tail off
[13:28] <popey> :(
[13:28] <cjwatson> anyway, I have an evil plan
[13:29] <cjwatson> it may involve iptables and redsocks
[13:30] <popey> evil plans are best plans
[13:31] <cjwatson> http://grokbase.com/t/ant/user/166fc12046/maven-ant-tasks-proxy-issue is one of the threads I mentioned and is somebody with essentially the same requirements we do
[13:31] <cjwatson> i.e. put a proxy in place without changing the actual project's build config
[17:02] <vidal72[m]> is something like this ok to be allowed on snapstore? https://snapcraft.io/juan-test-number-1
[19:40] <Luke> hey guys. is there a comprehensive doc on the $SNAP variables available for snapcraft?
[19:43] <Luke> hey guys. is there a comprehensive doc on the $SNAP variables available for snapcraft?
[19:44] <Luke> (sorry if I sent that twice, wasn't sure if I was online yet)
[19:49] <Luke> ah I found it!
[19:49] <Luke> https://docs.snapcraft.io/reference/env
[20:35] <Luke> how do I just copy a file form src into the install dir?
[20:37] <binarycreations> Hello there
[20:37] <Luke> hey
[20:38] <binarycreations> For better or worse I am running on Arch atm, trying to create my first snap. Followed the wiki to symlink /snap to the right location and read the same on the forum. However still can't install snapcraft as I am getting the --classic isn't supported error.
[20:40] <binarycreations> Listing snap --version gives me an Unknown version but the installed package is 2.26.1-3
[20:41] <binarycreations> Sorry I can't provide any more information.
[20:49] <binarycreations> Is there any way I can get more detailed logging or output from the snap command? More than happy to spend a bit of time walking through this a bit more
[21:00] <binarycreations> Okay, I have rebuilt the latest package from the AUR manually. The same error still exists
[21:09] <binarycreations> Okay... so re-installed the snap again, deleted existing snaps first and now that appears to have worked. Output from snap --version looks much better. snap and snapd report version 2.32.9-1, I will assume stupidity but perhaps there was an issue with older installation.
[21:09] <binarycreations> snap aur*