| *** frinring_ is now known as frinring | 00:44 | |
| *** zbenjamin is now known as Guest88946 | 01:36 | |
| *** zbenjamin_ is now known as zbenjamin | 01:36 | |
| *** Ischwitch is now known as Ingvix | 06:03 | |
| Kabouik_ | 10:18 | |
|---|---|---|
| Kabouik_ | 10:18 | |
| Kabouik_ | Where does the meeting take place? Isn't it here? | 10:18 |
| rinigus | Kabouik_: it is on #sailfishos-meeting | 10:19 |
| Kabouik_ | Thanks @rinigus | 10:20 |
| attah | Out of curiosity... how big is a OBS worker? | 15:55 |
| ol | It depends on how much you're going to build. You can use a regular PC to run your personal OBS server. | 15:59 |
| mkolman | It's big. You just won't believe how vastly, hugely, mind-bogglingly big it is. | 15:59 |
| mkolman | (sorry, couldn't help myself ;-) ) | 15:59 |
| ol | I run my OBS server (https://obs.infoserver.lv) on not very powerful server with 32G of RAM. | 16:00 |
| ol | But what really benefits from high speed and vast amounts of memory is OBS workers that does all dirty work to build packages. | 16:01 |
| attah | I have a Xeon E3-1246v3 based machine with 32GB RAM to spare.... just curious how relevant it miy or may not be | 16:01 |
| ol | I think this is more than enough for OBS server itself. | 16:01 |
| ol | And a couple of OBS workers. | 16:01 |
| mkolman | IIRC Sailfish OS dost (most ?) builds in tmpfs in RAM, making them very fast | 16:02 |
| ol | Yes, exactly. | 16:02 |
| attah | So i guess 32 is some sort of a minimum to be relevant | 16:03 |
| ol | I've settled on 14336 MB for each worker. That's more than enough for even very big packages (like PhantomJS). | 16:03 |
| ol | Most packages don't need this much memory. | 16:04 |
| ol | So, I have 2 workers on the same server. Also if needed, I start 2 more workers on my desktop PC that also has 32G of RAM (that also runs my Matrix homeserver, web server, SMTP server, DNS server). | 16:06 |
| attah | Maybe it is a bad idea to pool together these sort of thing s to replace the central OBS... but just playing with the idea | 16:07 |
| ol | And I have 2 aarch64 workers on cheap aarch64 VPS (about €6/mo), but without tmpfs build, and armv7l worker on Raspberry Pi 4 with 2G of RAM, also without tmpfs build. | 16:08 |
| ol | But I want to buy Raspberry Pi 4 with 8G of RAM to migrate that worker to and use tmpfs build before it kills microSD card with frequent writes. | 16:09 |
| mkolman | IIRC the Sailfish OS OBS has no native ARM hardware & is pretty fast | 16:11 |
| ol | Anyway, server of attah (IRC) will be enough for OBS server and 2 workers. All other workers should be provided by other community members. | 16:11 |
| mkolman | I wonder how even a new RPi compares to a Xeon running emulation | 16:11 |
| attah | It's too bad ARM devices are still so limited in how much RAM they can deal with, at least available hobbyist boards | 16:12 |
| ol | Yes, Sailfish OS uses sb2 for cross-compilation. But it's not suitable for my purposes: I build packages for Fedora. | 16:12 |
| ol | Yes, ARM devices have less of RAM than PC, but they are quite cheap. You can buy its own Raspberry Pi 4 for each OBS worker. | 16:13 |
| ol | Oh, and BTW, my OBS server runs on Fedora, not Suse. | 16:14 |
| mkolman | yeah, Fedora AFAIK Koji always has been native only | 16:14 |
| mkolman | still was weird when it had slow 32 bit ARM native hardware yet Sailfish OS could build ARM binaries super fast using emulation | 16:15 |
| mkolman | back then | 16:15 |
| ol | Koji is not relevant for my case: I use OBS. But sb2 is not relevant as well: it's too fragile even for installing all necessary packages for Fedora. | 16:16 |
| ol | Mer and Sailfish packages are built originally using sb2. Some packages had to be patched for that. | 16:16 |
| ol | I know that because I was working on improving sb2. I even created a fork of sb2, but there was no community interest in that. | 16:18 |
| attah | :( | 16:18 |
| ol | But I think that sb2 approach of partial emulation is quite good: run native tools for most tasks, emulate everything else in qemu. | 16:21 |
| ol | It's just implementation using LD_PRELOAD to replace all file access functions is really fragile and breaks easily. | 16:21 |
| ol | Something on system call level is needed instead. | 16:21 |
| ol | The problem with LD_PRELOAD approach is that glibc is monolitic. If there was a separate library providing ABI to system calls, this would be easy: replace all system calls with rewritten versions, and that's it. | 16:27 |
| ol | But with glibc you have to replace *all* functions that do something with pathnames: not just open(), but fopen(), freopen() etc. because even if you replace open() using LD_PRELOAD, all functions in glibc will use original version of open(). | 16:27 |
| ol | A little bit of offtopic, but if we talk about OBS here, I've started crowdfunding campaign to finance my work on porting OBS 2.10 to Fedora: | 16:35 |
| ol | https://www.gofundme.com/manage/porting-open-build-service-210-to-fedora-linux | 16:35 |
| ol | I don't expect to collect 2-month salary from private persons, but if you can find a corporate sponsor interested in this work, please give this link to them. | 16:35 |
| attah | That's the manage-link, try again ;) | 16:36 |
| attah | ol: fixed that for you https://www.gofundme.com/f/porting-open-build-service-210-to-fedora-linux | 16:42 |
| ol | Thank you! I've copied the wrong link. Of course, it should be https://www.gofundme.com/f/porting-open-build-service-210-to-fedora-linux | 16:43 |
| RobK | I'm trying to read data from a LocalStorage (rows) and bind them to a ListModel. The Qt example just appends an object in JS, but it doesn't seem to work. Which app could I use as example? | 16:47 |
| *** Yardanico is now known as Yardanico_ | 21:01 | |
| *** Yardanico_ is now known as Yardanico | 21:01 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!