[08:25] PR snapd#4701 opened: Release/2.31 === devil is now known as Guest77159 === Guest77159 is now known as devilz === devilz is now known as devil__ === devil__ is now known as devilz [13:55] * Son_Goku pokes niemeyer [13:56] Here [13:56] niemeyer: there doesn't appear to be any valid licensing for spread itself [13:56] could you look to license it properly under some kind of Free Software license? [13:57] Son_Goku: Ah, thanks for raising that.. yeah, there should be a license file there for sure [13:58] I was looking to package it for my use, and lo, no licensing [13:58] somehow we went 158 commits and two years without noticing this :P [14:00] Son_Goku: Done [14:00] :D [14:01] Son_Goku: Yeah, not too surprising.. this is more of a helper tool for us [14:02] niemeyer, also did you guys get a new person? [14:03] I saw a pull request open by some guy who has no meaningful profile in the snapd repo [14:03] https://github.com/snapcore/snapd/pull/4701 [14:03] PR #4701: Release/2.31 [14:03] when I first saw it, I thought you guys might have been hacked... [14:04] I'm not sure you haven't, tbh [14:29] Son_Goku: Why does that taste like hacking? [14:30] Son_Goku: I mean, anyone can push PRs, right? [14:30] niemeyer, the guy has no proper profile, it's the only thing he's actually done [14:30] and the doesn't even look right [14:30] err, the PR doesn't look right [14:31] maybe... [14:31] you know, I've never tried [14:31] Son_Goku: I know, but pushing a PR requires zero permissions [14:31] huh, you're right [14:31] so it's just a weird guy hitting buttons [14:31] * Son_Goku shrugs [14:31] carry on then [14:33] pushing a PR from a branch you don't control to another branch you don't control is apparently possible [14:33] Son_Goku: Yeah, proposing is open [17:13] Anyone know how to use version from git [17:15] https://github.com/snapcore/snapcraft/pull/1260 [17:15] PR snapcraft#1260: meta: version from git support [17:16] Yes, I have read through it [17:16] I get fatal error though, not a git repository [17:17] My part is git, snapcraft is not git [17:20] hurricanehrndz: Not sure I get what you mean.. would you mind to open a topic in the forum with more details? We have several eyes there and more chances of helping you out quickly [17:26] niemeyer: Thanks, I might have thought of away around the issue [17:53] hurricanehrndz: np, and please let us know if you need some info [18:06] PR snapd#4701 closed: Release/2.31 [18:46] Issue snapcraft#1939 opened: rust plugin: i386 multiarch linker error [19:04] niemeyer: okay so I found the issue, version: git only works when the snap files are part of the original projec [19:05] if you are building a snap from another dev's project and using source-type: git, it doesn't work === devil is now known as Guest49044 === devil is now known as Guest92838 [20:16] PR snapd#4702 opened: cmd/snap: also include tracking channel in list output [22:05] hurricanehrndz: correct. We sometimes have to jump through hoops to set the version number when the yaml isn't in the upstream source [22:06] hurricanehrndz: like this. https://github.com/snapcrafters/discord/blob/master/snap/snapcraft.yaml#L15 [22:44] popey: thank, I saw that in another one of your contributions. I think atom [23:55] Anyone have a dbus example?