[00:11] HI, I have a quick question - how to integrate openvpn (client) into a snap? [08:25] hey! [09:29] Hi, What does this mean?$ sudo snap refresherror: cannot refresh []: Post https://search.apps.ubuntu.com/api/v1/snaps/metadata: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) [10:09] the package index is timing out; I've contacted IS. === __chip__ is now known as Chipaca [10:50] PR core#37 opened: install keyring (LP: #1670475), update pkglists [10:55] PR core-build#10 opened: make /etc/environment writable [11:00] ogra_: will that work with atomic writes? [11:00] Chipaca, no [11:01] ogra_: what needs doing so it does? [11:01] like any ontgher single file we make writable like this [11:01] unionfs ... aufs, overlayfs ? [11:01] ogra_: so this bind-mounts instead of being a symlink? [11:01] yes [11:01] ogra_: how do you say "make it a symlink"? [11:01] NicolinoCuralli: you're making me wish i disabled join/part notifications [11:02] you create a file in /etc/writable and link to it ... [11:02] problem is ... [11:02] ogra_: any reason not to do that? [11:02] /etc/environment is hardcoded in half the world ... so that wont work here [11:02] why? [11:02] they won't follow a symlink? [11:02] because i highly dbout anything reading it follows symlinks [11:03] we could try ... but i really doubt it [11:03] people have to do extra work to not follow symlinks [11:05] why is atomic so important for you ? we wont allow more than a proxy setting ... writing to a tmp file and mv is close to atomic [11:05] it isnt like we could make the system unbootable or something if that fails [11:06] (and i will surely fight adding other random stuff to that file that might make it break the boot) [11:07] ogra_: because if we don't, the file will get corrupted (most likely being zero'd out) [11:07] how ? [11:07] we dont open it [11:08] you cp it to /tmp ... change the file in tmp and then you mv ... [11:08] ogra_: /tmp is a different filesystem, so mv is a cp, is an open and write [11:08] (you could add an additional check between editing and mv if that makes you feel safer) [11:09] well, then /var/tmp or whatnot ... you knwo waht i mean :) [11:09] _as far as i know_ (but we can test if you want) they're all different filesystems as far as rename is concerned [11:09] i mean, try it with python, easy enough to do [11:10] well, i dont really want to add all the problems we have with /etc/writable to that file [11:10] then i'll rather keep it readonly and have whatever adds the proxy add it differently [11:11] ogra_: every time we come to this area I'm closer to thinking we need to reverse the logic [11:11] ogra_: and make /etc writable except for [11:12] Chipaca, we need to change it ... weather it is by reversing the logic, i dont know .... it was on the "to discuss" list for the sprint ... lets see what came out of it [11:12] ok [11:13] /etc/writable is an ugly wart [11:13] lower your voice! don't want it to hear and throw a hissy fit [11:13] lol [11:30] is snap store down? [11:34] I can't install snaps [11:35] Client.Timeout exceeded while awaiting headers [11:35] network is working ok [11:35] maybe the server? [11:35] anybody with problems also? [11:45] jfcastroluis: yes, the store is down, people are working on it [11:47] Chipaca: ok, thank you! :) [11:47] where is hosted snap store? aws? [11:48] jfcastroluis: I think it's in one of canonical's DCs [11:49] how you know is down? is there a status page? for next times (hope not many :) [11:51] jfcastroluis: I know the URL to the store? [11:52] and it times out [11:52] ok, ok! :) [15:09] hellu [15:09] i hear du guys liked feedback [15:09] so i just wanted to say that on my fresh manjaro xfce install, it hangs right after you install it [15:10] i've run both systemctl start/enable snapd.socket and systemctl start/enable snapd.refresh.timer [15:10] running "sudo snap install discord" makes it hang at "[-] Run configure hook of "core" snap if present" [15:12] force stopping it, and running it a second time gives the issue: [15:12] "INFO snap "core" has bad plugs or slots: core-support-plug (unknown interface)" [15:13] is this chat dead? xD [15:17] sciencefyll, you are better off to post to the forum onn weekends (see the channel topic) === JanC is now known as Guest57282 === JanC_ is now known as JanC [18:06] PR snapcraft#1300 opened: tools: add a script to install autopkgtest dependencies [18:46] hi. i made a sigrok snap ages ago but it never worked outside dev mode because it needs raw usb access. should i just make it use classic mode and put it in the store? [18:46] and does anyone want to help me clean it up and do that? [18:47] its here: https://github.com/ali1234/mysnaps/tree/master/sigrok [18:47] upstream showed interest in it too [18:50] oh there's a raw-usb interface now === AdamH__ is now known as adamh__ [19:13] i built my snap to use the raw-usb interface and connected it but i still get "sr: backend: libusb_init() returned LIBUSB_ERROR_OTHER." [19:13] type=1400 audit(1494097705.817:107): apparmor="DENIED" operation="create" profile="snap.sigrok.sigrok-cli" pid=8274 comm="sigrok-cli" family="netlink" sock_type="raw" protocol=15 requested_mask="create" denied_mask="create" [19:21] PR snapcraft#1301 opened: recording: record global build-packages installed on the host [19:26] it still works in devmode [19:42] ok [19:43] now, please tell me [19:55] qt5 apps aren't themed correctly, not even in the store [19:56] also "snapcraft cleanbuild" still fails: HTTPSConnectionPool(host='parts.snapcraft.io', port=443): Max retries exceeded with url: /v1/parts.yaml (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))