| *** tristan has quit IRC | 01:53 | |
| *** tristan has joined #buildstream | 01:54 | |
| *** ChanServ sets mode: +o tristan | 01:54 | |
| *** tristan has quit IRC | 03:27 | |
| *** tristan has joined #buildstream | 07:02 | |
| *** ChanServ sets mode: +o tristan | 07:02 | |
| *** tristan has quit IRC | 07:17 | |
| *** tristan has joined #buildstream | 07:34 | |
| *** ChanServ sets mode: +o tristan | 07:34 | |
| tristan | robjh, sorry I was under the weather last week and missed your inquiries, did you get things sorted out in the end ? | 07:59 |
|---|---|---|
| *** tristan has quit IRC | 08:15 | |
| *** tristan has joined #buildstream | 08:15 | |
| *** ChanServ sets mode: +o tristan | 08:15 | |
| *** tristan has quit IRC | 08:23 | |
| coldtom | robjh, NoneType object is not callable is fixed by installing ruamel.yaml.clib | 09:01 |
| *** santi has joined #buildstream | 09:41 | |
| *** dftxbs3e has joined #buildstream | 09:42 | |
| robjh | coldtom, yeah i found that, fixing a weirder problem now :) | 09:43 |
| coldtom | hah, it's bugs all the way down | 09:45 |
| *** tristan has joined #buildstream | 10:38 | |
| *** ChanServ sets mode: +o tristan | 10:38 | |
| robjh | tristan, i found the answer to about everything i was asking about yesterday :) | 11:18 |
| *** tristan has quit IRC | 11:44 | |
| *** tristan has joined #buildstream | 11:45 | |
| *** ChanServ sets mode: +o tristan | 11:45 | |
| robjh | God damn, its all working! :D | 12:10 |
| coldtom | \o/ | 12:11 |
| robjh | ITS TIME TO UNINSTALL BUILDSTREAM! | 12:11 |
| tristan | Good to hear that :) | 12:11 |
| tristan | Oh... haha | 12:11 |
| tristan | Spoke too soon ? hehe | 12:11 |
| robjh | nono, its time for everyone to uninstall buildstream. | 12:12 |
| tristan | ... Because... it was incorrectly installed ? | 12:12 |
| tristan | missing version information ? | 12:13 |
| robjh | no, because ive packaged it as an appimage | 12:13 |
| robjh | \o/ | 12:15 |
| robjh | cross compiled too :D | 12:16 |
| tristan | Appimage ?! | 12:19 |
| tristan | Whoa, that is a blast from the past | 12:19 |
| robjh | a blast from 2018? | 12:20 |
| tristan | https://blogs.gnome.org/tvb/2013/12/14/application-bundles-revisited/ | 12:20 |
| robjh | i seee | 12:21 |
| tristan | That was my latest encounter, I wrote a vala script to replace the older thing which was doing some awk/sed in generated linker scripts to mess around with symbol versions | 12:21 |
| robjh | Error staging source: file could not be opened successfully DANG! | 12:22 |
| tristan | is it still not feasible to have a flatpak of buildstream ? | 12:22 |
| robjh | can you run a flatpak without installing a runtime first? | 12:22 |
| tristan | I guess it is feasible but requires running code outside the sandbox (some few other corner case flatpaks I think also do this) | 12:22 |
| tristan | No you cannot, but I think it's not a big deal | 12:23 |
| robjh | its an absolute blocker for me | 12:23 |
| tristan | I mean, the tradeoff here is (A) AppImage: Mess around with your linked libraries and try to get glibc symbol tables to do something they are not really supporting well... (B) Flatpak: Have a common runtime and actually provide the symbols on a variety of platforms | 12:24 |
| robjh | if youre going to install the runtime, you might aswell just install the application properly | 12:25 |
| robjh | hey, maybe you can package the flatpak runtime and a flatpak as an appimage | 12:26 |
| coldtom | robjh: you _could_ define an empty flatpak runtime and use that as the app's runtime (I think) | 12:26 |
| tristan | I'm curious, if you managed to run BuildStream in an app image, how old can the host OS be ? (what is the lowest version of glibc this buildstream will run on ?) | 12:26 |
| tristan | I probably don't understand the use case here | 12:26 |
| robjh | im not sure yet, the cross toolchain is configured to support a glibc 2.11 and kernel 3.2 | 12:27 |
| tristan | robjh, From my POV, the main use case of AppImage and Flatpak (i.e. "Application bundling" in general) is to allow developers to deliver bleeding edge software directly to users more conveniently | 12:27 |
| robjh | but i need to get it working better first | 12:27 |
| tristan | As a user, I want to run my LTS stable distro, and use bleeding edge apps built yesterday | 12:28 |
| robjh | tristan, i want to be able to checkout a buildstream project, and not have to worry about the specific verion of buildstream i have installed | 12:28 |
| tristan | For these use cases, I think that Flatpak is a more solid/reliable solution (after having doing my fair share of struggling with app image, at least that is my opinion) | 12:28 |
| robjh | you people drove me to this | 12:29 |
| tristan | You should not have to worry about that, you should only have to worry about having a "recent enough" version of stable buildstream | 12:29 |
| robjh | i also dont want to have to faff about with buildbox on arm | 12:29 |
| tristan | If you are using BuildStream 1.9x development snapshots, I can understand your pain | 12:29 |
| tristan | That is because you are using unstable software, I don't have any solution for that except for: use BuildStream 1, or help get BuildStream 2 over the line, there really is nothing "usable" in between | 12:30 |
| robjh | when i started my project, i was told i should just use bst2 from the start | 12:30 |
| robjh | so my project is bst2 and you guys break it constantly | 12:31 |
| tristan | bst2 does not exist, though | 12:31 |
| robjh | oh sod off you know what i mean | 12:31 |
| tristan | I don't know who told you to do that, if it is an experimental project who's purpose is to advance the development of bst2, then that would be a good recommendation | 12:31 |
| robjh | bst2 does not exist, though | 12:31 |
| tristan | if you wanted something to build a serious product, then you need something stable | 12:32 |
| tristan | I'm not kidding here, bst2 does really not exist - there is no realistic world where one can recommend to a user to use it, as it is not stable - there is no story for consuming updates | 12:32 |
| robjh | so this discussion does nothing to solve my current problem: <robjh> Error staging source: file could not be opened | 12:33 |
| tristan | it's experimental until it is released | 12:33 |
| robjh | its never getting released | 12:33 |
| tristan | Thanks for your words of encouragement | 12:36 |
| robjh | anytime | 12:36 |
| tristan | if it never get's released: Then that is a complete waste of the last few years, so I certainly hope it does. | 12:36 |
| robjh | im sure it might eventually, but it certainly feels like the new wayland | 12:37 |
| robjh | is there a way to make the logs for download and extraction a bit more verbose? i need to see what its trying to run | 12:39 |
| *** cs-shadow has joined #buildstream | 12:46 | |
| *** tristan has quit IRC | 12:46 | |
| *** tristan has joined #buildstream | 12:48 | |
| *** ChanServ sets mode: +o tristan | 12:48 | |
| *** tristan has quit IRC | 12:55 | |
| *** tristan has joined #buildstream | 13:50 | |
| *** ChanServ sets mode: +o tristan | 13:50 | |
| robjh | i solved it, python wasnt built with zlib or bz2 :) | 13:54 |
| *** tristan has quit IRC | 14:28 | |
| *** santi has quit IRC | 15:01 | |
| *** cs-shadow has quit IRC | 15:45 | |
| *** cs-shadow has joined #buildstream | 16:04 | |
| *** santi has joined #buildstream | 16:19 | |
| *** santi has quit IRC | 19:00 | |
| *** cs-shadow has quit IRC | 19:25 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!