/srv/irclogs.ubuntu.com/2016/12/03/#snappy.txt

mupPR snapcraft#944 closed: Release changelog for 2.23 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/944>01:33
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
mupPR snapd#2403 opened: store: fix unhandled error from io.Copy() in download() <Created by mvo5> <https://github.com/snapcore/snapd/pull/2403>07:11
madprops__very excited about snap09:53
madprops__still dont understand it fully09:53
madprops__thinking about what would happen with big applications like DEs09:54
madprops__im guessing some of it will be global ... but temporarily?09:54
madprops__will it be snap and the normal global system in conjunction09:55
madprops__or will everything be snap09:55
madprops__i wonder09:55
madprops__but giving applications its jar and water to live is an idea ive always thought why it was not being implemented09:56
madprops__idk09:56
madpropsI saw a question that made me wonder, maybe someone can explain it to me "How do I verify that all 300 copies of libgnutls.so are patched and protected against the latest vulnerabilities?"19:15
ali1234madprops: there is no good answer to that question, in the general sense. it has always been a problem for any type of app bundling19:28
ali1234for highly important libraries involving encryption etc there will be platform snaps which will provide library sharing19:29
ali1234and of course the core platform19:30
ali1234but you can still get bitten by something obscure19:30
madpropsthat's what i feared19:32
madpropsmakes me think, this among other things, that maybe "snapifying" a system maybe not the way to go .. except for certain cases19:36
madpropslike video games make sense19:36
madpropsbut at the same time you can have something like steam19:36
madpropsbut on the other hand it does have some benefits, like less prone to dependency hell and quicker updates19:45
=== JanC_ is now known as JanC
qenghomadprops: I expect there will be a kind of scanner for out of date dependencies in packages, and shame as the major motivator for people to fix their bugs.19:57
qenghomadprops: The great thing about snaps is that a broken package can only harm the things it is allowed touch, which is not very much -- pretty much only what it makes.19:59
qenghomadprops: As always, you have to trust the person who makes the code. With snaps, there is no third person (a packager) who has to care enough also.20:01
madpropsqengho, how do snap hosting works? do developers make a snap and publish it in some centralized server or they host it themselves?20:06
qenghomadprops: There are central hosts, stores.20:09
qenghomadprops: Your "snap" system has one in mind when you install.20:09
qenghomadprops: And your machine ensures everything is up to date by checking its store every so often.20:10
madpropswho mantains these stores monetarily?20:10
qenghomadprops: You, if you develop a snap-using OS. Ubuntu has one. Probably others.20:12
qenghoI use Ubuntu Core, so my machines ask Ubuntu's store.20:12
qenghoI also upload a few packages to Ubuntu's store. I push to a Launchpad branch and it deposits compiled packages (for four architectures!) into my snap-package's Proposed channel in a few minutes. I make sure it looks right and then promote it to Stable channel in the store.20:15
qenghohttps://myapps.developer.ubuntu.com/20:15
madpropsnice20:19
ali1234what architectures do you build for?20:20
ali1234can snapcraft do cross-builds yet?20:20
qenghoali1234: Some parts have cross-build support, but not all. Some will be tricky. I build for x86, amd64, armhf, & amr6420:22
qenghoali1234: Now that there's a virtual-machine build process, I suspect the built-in cross-build will die and we'll just emulate the other arch and run "native" there.20:23
qenghoBut I don't know a lot of that.20:23
ali1234i find the launchpad workflow too slow for development20:24
ali1234it would probably be okay once i actually get things working20:25
qenghoYeah, Launchpad isn't your development environment.20:26
ali1234yeah... unfortunately my target is raspberry pi20:26
ali1234so native builds are even slowed20:26
qenghoali1234: "snapcraft cleanbuild" runs lxc. Making that be a different architecture should be possible.20:28
ali1234i couldn't get cleanbuild to even work for host architecture20:28
qenghoJust some other wrapper to an emulator.20:28
ali1234it just gives me apt errors20:28
ali1234http://askubuntu.com/questions/787258/internal-server-error-when-retrieving-files-from-the-archive-in-lxd20:29
qenghohttp 500 from an archive? Sounds funny. Are you using a proxy or something?20:30
ali1234no20:32
qenghoali1234: Well, that would be a problem common to every Ubuntu user everywhere, not specific to snapcraft.20:53
ali1234it only happens with snapcraft20:53
ali1234specifically, only with lxc it seems20:53
ali1234also i didn't post that question20:53
ali1234so it isnt just me20:54
torusJKLHi. I have a qustion regarding building with autotools.23:01
torusJKLI want to instruct snapcraft to build witin the directory build_unix.23:01
torusJKLBut the configure.ac file is in the directory dist.23:02
torusJKLI tried to use source-dir and specified dist.23:02
torusJKLIt found the configure file but then it would say that I should not build in this directory.23:03
torusJKLThe error is: Berkeley DB should not be built in the top-level or "dist" directories. Change directory to the build_unix directory and run ../dist/configure from there.23:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!