[06:18] <mup> PR snapcraft#1594 opened: code style: remove the extra quotes in the dedent example <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1594>
[06:58] <mup> PR snapcraft#1595 opened: tests: fix the skip of snapd integration tests in armhf <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1595>
[07:07] <mup> PR core#60 closed: Fix handling of secondary addresses <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/core/pull/60>
[07:10] <mup> PR snapcraft#1596 opened: tests: move ruby demo test to snapd integration suite <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1596>
[17:47] <mup> PR snapcraft#1594 closed: code style: remove the extra quotes in the dedent example <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1594>
[19:52] <ekkis> I'm setting up to publish a snap but need to select a "developer namespace".  can anyone explain to me what this is?
[19:52] <ekkis> I can, apparently, only set it once and I don't want to get it wrong
[19:54] <ekkis> the docs state: "This namespace will represent you as a publisher in the Snap Store and you won’t be able to change it afterwards"
[19:54] <ekkis> represent me? how?
[19:54] <ekkis> I have an account name.  so can I have my account name the same as the namespace?
[20:25] <kyrofa> ekkis, yes
[20:25] <kyrofa> ekkis, your namespace will show up in `snap list` as the publisher of the snap
[20:27] <zyga-solus> ekkis: right
[20:27] <zyga-solus> ekkis: so essentially this is your publisher nickname
[20:27] <zyga-solus> ekkis: if you say "my namespace is ekkis"
[20:27] <ekkis> oh... I see.  it's because my "account" doesn't have an account name, like in most other systems
[20:27] <zyga-solus> ekkis: then if someone "snap install thatfancyapp"
[20:27] <zyga-solus> ekkis: then they will get it from "ekkis"
[20:27] <zyga-solus> ekkis: I agree the word namespace is not clear here
[20:28] <ekkis> so they don't have to run `snap install ekkis/thatfancyapp`?
[20:31] <zyga-solus> ekkis: that's right
[20:31] <zyga-solus> ekkis: users install snaps
[20:31] <zyga-solus> ekkis: snaps have names
[20:31] <zyga-solus> ekkis: and users search by name, not by developer IDs or similar things
[20:31] <ekkis> thanks mate
[20:31] <zyga-solus> my pleasure :)
[20:31] <sergiusens> kyrofa is the time off getting too boring? :-P
[20:31] <ekkis> I'm building my first
[20:32] <kyrofa> sergiusens, haha, no, I just tend to idle here even when I'm not working and noticed a question :)
[20:32] <zyga-solus> nothing like the feeling of building one's first snap :)
[20:33] <ekkis> I can specify the `source` field as a url to a tarball.  can I also point it to a github repo?
[20:33] <zyga-solus> ekkis: snaps give developers the power to publish to users
[20:33] <zyga-solus> ekkis: yes
[20:33] <ekkis> do I use the .git url?
[20:33] <zyga-solus> ekkis: there are lots of possible schemes, sergiusens and kyrofa can tell you all about that
[20:34] <ekkis> for example, for Einsteinium (which I'm trying to package), the Clone or Download button indicates: https://github.com/emc2foundation/einsteinium.git
[20:34] <ekkis> can I use this url?
[20:34] <kyrofa> ekkis, indeed you can
[20:34] <sergiusens> zyga-solus does content interface work with classic snaps?
[20:35] <ekkis> kyrofa++
[20:39] <ekkis> suppose that my project has a bunch of dependencies.  the build doc indicates I should install them using apt-get.  how do I express these in the `parts:` section?
[20:39] <ekkis> I presume these parts are snaps?
[20:39] <ekkis> so I have to find the equivalent snaps? or?
[20:40] <ekkis> which also begs the question, do I have to declare all the building tools?
[20:40] <ekkis> most of the dependencies are developer-level
[20:42] <ekkis> in other words there are dependence packages that don't need to be included in the snap
[20:44] <kyrofa> ekkis, there are three keywords that will be of interest: build-packages, stage-packages, and build-snaps
[20:44] <ekkis> oh... let me read up on those then
[20:44] <kyrofa> build-packages are debs that are installed on the host (builder). Build tools might fit into this section
[20:44] <kyrofa> stage-packages are debs that are fetched from the archive and unpacked into the snap
[20:45] <kyrofa> build-snaps are snaps that are installed on the host (e.g. perhaps your build tools are snapped)
[20:45] <ekkis> it's not part of the `parts` section I see
[20:46] <kyrofa> ekkis, I'm not sure which docs you're reading
[20:46] <kyrofa> Link?
[20:46] <ekkis> I see in the different part of the docs it talks about these 3 keywords
[20:47] <ekkis> so for example, the command `sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` in the instructions requires I have all those tools for building
[20:47] <ekkis> that means I have to find snaps of them correct?
[20:47] <kyrofa> ekkis, no, those would be build-packages
[20:48] <ekkis> so do I just declare `build-packages: build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` ?
[20:49] <kyrofa> Something like that. It needs to be a YAML list, but you have the right idea
[20:49] <ekkis> ah.  ok
[20:49] <ekkis> and Snapcraft knows to do an apt-get for each
[20:49] <ekkis> and if snap is running on Fedora it will do a `yum install`? (or whatever it is now)
[20:50] <kyrofa> ekkis, not yet, support for other distros in snapcraft is coming
[20:51] <ekkis> ah, but at least theoreticallly
[20:51] <ekkis> at present I'm only concerned with Ubuntu
[20:51] <ekkis> I used to package stuff in RPM form for Redhat and later Fedora
[20:51] <ekkis> so having a cross-distro packager is great!
[20:55] <kyrofa> ekkis, note that, while Snapcraft currently only runs on Ubuntu, the snaps it produces should run everywhere
[20:58] <ekkis> oh.  anywhere so long as `snap` is available on the platform
[21:01] <kyrofa> ekkis, you got it
[21:01] <kyrofa> ekkis, fedora has snapd, for example
[21:04] <sergiusens> ekkis support for rpm distros is coming through dnf support, you can probably get more detailed information from Son_Goku on that aspect
[21:05]  * Son_Goku waves
[21:06] <sergiusens> kyrofa since you are here, mind quickly glancing at snapcraft#1597 ?
[21:06] <mup> PR snapcraft#1597: pluginhandler: warn about migrated system libraries <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1597>
[21:08] <Son_Goku> ekkis: if you want to build RPM-based snaps, you can do it by hand right now
[21:08] <Son_Goku> though it's a pain to do
[21:08] <Son_Goku> kyrofa and kalikiana have been helping me with getting different aspects of Snapcraft running on Fedora
[21:08] <mup> PR snapcraft#1597 opened: pluginhandler: warn about migrated system libraries <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1597>
[21:14] <ekkis> Son_Goku: I may want to.  I'm building my first snap so I'll stick to the Ubuntu variant but I may come back to you
[21:14] <ekkis> Son_Goku: I was a redhat/fedora guy for a decade years ago
[21:17] <Son_Goku> the main problem is describing the security stuff
[21:17] <Son_Goku> otherwise, it's really easy
[21:23]  * Son_Goku grumbles
[21:24] <Son_Goku> crap Wi-Fi sucks
[21:24] <ekkis> does it matter what I call parts? I think I only have one part so I could just call it `main`?
[21:27] <ekkis> kyrofa: "A set of Ubuntu packages to be downloaded and unpacked to join the part before it’s built" -- what does "join" mean?
[21:30] <ekkis> guys, I've looked through the docs but it's not at all clear to me where I actually run the commands to build my app
[21:31] <ekkis> I need to run autogen, configure, make and make install
[21:32] <ekkis> oh.... I can use `plugin: autotools`
[21:32] <mup> PR snapcraft#1574 closed: Add Dotnet plugin and a sample snap for integration test <enhancement> <Created by rakeshsinghranchi> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1574>
[21:32] <ekkis> so I just need to figure out how to configure the plugin
[21:43] <zyga-solus> ekkis: part names don't matter
[21:43] <ekkis> ok, cool
[21:43] <zyga-solus> ekkis: snapcraft has nice built in help I think
[21:43] <zyga-solus> including help for particular plugins
[21:44] <ekkis> # snapcraft --help autotools?
[21:44] <sergiusens> snapcraft help autotools
[21:44] <zyga-solus> not quite I think, try snapcraft help and look from there
[21:44] <zyga-solus> I think snapcraft help plugins or something like that talks about it but I don't remember
[21:45] <zyga-solus> thank you sergiusens
[21:46] <ekkis> the help is for commands to snapcraft
[21:47] <ekkis> but I'm looking at the web for help.  the docs are not very clear
[21:49] <sergiusens> ekkis https://docs.snapcraft.io/build-snaps/your-first-snap
[21:50] <ekkis> yes, I'm reading through that doc
[21:51] <sergiusens> my network is wonky, so I cannot verify what I am sending over your way ekkis but this might be useful https://tutorials.ubuntu.com/tutorial/create-your-first-snap
[23:58] <buzz_> Hello
[23:59] <Guest93864> Hello
[23:59] <Guest93864> Anyone hoe
[23:59] <Guest93864> Anyone home