[00:21] <mup> PR snapcraft#1937 opened: store: support pushing snap with no architectures <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1937>
[03:01] <mup> PR snapcraft#1933 closed: schema: remove underscore from version pattern <bug> <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1933>
[03:10] <mup> PR snapcraft#1931 closed: No plainbox <bug> <Created by yphus> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1931>
[12:00] <mup> PR snapcraft#1937 closed: store: support pushing snap with no architectures <bug> <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1937>
[12:21] <mup> PR snapcraft#1938 opened: tests: improvements to demos <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1938>
[17:00] <mup> PR snapd#4700 opened: interfaces/builtin: add the dvb-video interface <Created by ThyMYthOS> <https://github.com/snapcore/snapd/pull/4700>
[17:16] <niemeyer> nacc: Thanks for the report, and yeah, that's definitely a bug because even if you have no snap around at all, it should still not report anything
[17:23]  * zyga starts to see failures on     - linode:ubuntu-14.04-64:tests/main/security-device-cgroups:uinput
[17:32] <hurricanehrndz> how do you audit snaps, where can you find the yaml build files
[17:32] <zyga> hurricanehrndz not all snaps publish source files and build instructions
[17:36] <hurricanehrndz> Ah...
[17:36] <hurricanehrndz> got it
[17:37] <hurricanehrndz> So it would be a good way for someone to distribute or install a malicious app without really knowing
[17:37] <hurricanehrndz> That's sad
[17:39] <zyga> not better than all the other ways that already exist
[17:41] <diddledan> hurricanehrndz: it's better than a PPA or direct download because of the confinement
[17:42] <hurricanehrndz> zyga: true, but at least with debs you can audit, diddledan: very true although some are classic
[17:42] <zyga> hurricanehrndz how can you audit skype.deb from microsoft?
[17:43] <hurricanehrndz> zyga: Point taken
[17:43] <zyga> all the old ways of being nasty are there, nothing is new, it's slightly safer as people will, over time, look for random packages less and less and will use the store
[17:43] <hurricanehrndz> I guess I learn a lot from example, so what I was trying to find is the source yaml files from the qt team since I have heard they have done a good job on making it easier
[17:44] <zyga> where we have more confinement than usual, we can stop nasty apps once they are know, etc
[17:44] <zyga> I think one think we ought to improve is to point the way to the source for FOSS snaps
[17:44] <hurricanehrndz> I'm just having a hard time finding the source files, I have stumble on a couple on lauchpad
[17:44] <hurricanehrndz> zyga: Yes, that would be awesome
[17:44] <hurricanehrndz> zyga: that way other devs could contribute
[17:45] <zyga> I'll check if that's on the roadmap, it's very sensible and should be easy to add
[17:45] <hurricanehrndz> zyga: Thank you.
[17:45] <diddledan> for snaps built by the build service the source git repo should be automatically added to metadata IMO
[17:46] <zyga> I cannot find anything quickly, I will check with snapcraft devs next week
[17:50] <hurricanehrndz> Is there anyway right now for me to find that source for foss projects in the snapstore online
[17:51] <diddledan> for all the snapcrafters ones they're at github.com/snapcrafters, to begin with
[17:52] <diddledan> others are either under individual user accounts for community maintained ones, so those you'll possibly need to contact the author, and others are maintained directly by upstream so it's likely wherever they usually keep their source
[17:52] <zyga> hurricanehrndz you can also search for snapcraft.yaml on github
[17:53] <hurricanehrndz> lol
[17:53] <hurricanehrndz> of course
[17:54] <hurricanehrndz> Thanks zyga, and thanks for passing that onto to devs, I think having a pointer listed in the output of info would be helpful to foster greater collaboration
[17:54] <hurricanehrndz> zyga: or a support url in order to submit bugs as well
[17:54] <zyga> yeah, I think that's some great feedback, thank you
[17:54] <zyga> I think we have that one already
[17:54] <zyga> AFAIR
[17:54] <hurricanehrndz> Let me check
[17:55] <diddledan> support url already exists
[17:55] <hurricanehrndz> How do I get it, sorry very new to snaps
[17:55] <zyga> snap info $snapname
[17:55] <diddledan> run `snap info corebird` for example
[17:56] <diddledan> it points to the snapcrafters repo's issue tracker
[17:56] <hurricanehrndz> Yup, got it, I was checking vscode and that only has an email
[17:57] <diddledan> flexiondotorg is idling here :-p he's out to curry right now though so you'll not get a reply :-D
[17:58] <ahayzen> diddledan, github.com/snapcrafters seems to be what is in edge not stable ? Is there a place for the stable snapcraft.yaml ?
[17:58] <zyga> ahayzen interesting point!
[17:58] <diddledan> hmm?
[17:59] <diddledan> I don't understand
[17:59] <ahayzen> eg mattermost-desktop is 3.7.1 in the store, 4.0 on github/snapcrafters, mumble is 1.2.17 in the store, 1.3.0 in github/snapcrafters
[18:00] <ahayzen> i haven't been able to find the snapcraft.yaml that is for the stable builds
[18:00] <diddledan> the repos have a history you can go through
[18:01] <ahayzen> that's not really useful, they aren't even tagged
[18:01] <ahayzen> i can't create a reproducible build with that as i don't know which commit was used
[18:04] <zyga> I think this is all valid feedback, we're just getting started with that aspect of snaps
[18:04] <zyga> but I think there are some low hanging fruit there
[20:56] <mup> PR snapcraft#1936 closed: storeapi: handle errors even for >400 responses <bug> <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1936>