| rinigus | fridl: good question regarding updates. we don't have webhooks enabled in _service files at chum and chum:testing to avoid spontaneous updates. | 06:02 |
|---|---|---|
| rinigus | we could make you maintainer of your packages in :testing - that way you will bump the version yourself. with all working, you could just submit package from testing to chum. | 06:04 |
| rinigus | piggz: should we do that way? ^ | 06:04 |
| *** amccarthy_ is now known as amccarthy | 07:11 | |
| piggz | rinigus: seems fair | 07:32 |
| rinigus | piggz: and easier for us :) | 07:32 |
| Renaud[m] | hi | 07:33 |
| rinigus | fridl: I have added you as a maintainer for harbour-avarisk in testing. on update, please change release version in _service and if all is fine, just submit from :chum:testing to :chum. and we will be able to accept your submission | 07:35 |
| fridlmue | rinigus: Ok, sounds perfect! | 07:39 |
| Renaud[m] | I have a question regarding linux tool packaging: | 08:05 |
| Renaud[m] | what would entail asking for inclusion into chum organization on github? The packaging burden would not falls onto the chum maintainers, does it? | 08:05 |
| rinigus | Renaud: I think we should be able to make you maintainer of your tools packages in chum repo at github as well. That way we can keep the effort spread among all of us | 08:18 |
| rinigus | advantage of having them in github org is mainly sharing the effort. it is probably easier to do so if we have one location where we can check packaging | 08:19 |
| rinigus | also, I expect that number of org maintainers will increase | 08:20 |
| rinigus | Renaud: ^ | 08:20 |
| Renaud[m] | alright, makes sense | 08:20 |
| Renaud[m] | I'll start opening issues, then :) | 08:22 |
| rinigus | Renaud: great! looking forward | 08:22 |
| Renaud[m] | Another question: are there restrictions regarding licensing? What about GPLv3 software, for instance? | 08:27 |
| rinigus | Renaud: no restrictions so far. gplv3 is fine for sure. you would just need to be able to provide source for the code to make it possible to compile | 08:28 |
| rinigus | we touched on restrictions in README (for devs section), please see | 08:28 |
| fridlmue | wouldn't it be a good Idea to have a repo for "missing packages"-issues in github? That would then be like a wishlist and we could start packaging these things. E. g. I have some Ideas, but most are to complex at the moment and im to much of a starter in that topic. So if something easy pops up there i could try to get that running first. | 08:29 |
| fridlmue | Or do we want to do that in the sfos forum? | 08:29 |
| Renaud[m] | okay, good. I have skimmed through the README but I just wanted to be sure | 08:29 |
| rinigus | fridlmue: that's what the "main" repo is for | 08:30 |
| rinigus | I think it may be too complex and scattered at the forum | 08:30 |
| fridlmue | ok, got it | 08:34 |
| piggz | rinigus: a whole lot of sumbissions for you! | 09:26 |
| Thaodan | "main | 09:51 |
| Thaodan | Why main branch or repo? | 09:52 |
| piggz | Thaodan: main is just a holder repo for documentation/issues | 09:58 |
| rinigus | piggz: I see. but you could accept them yourself - have to run | 10:12 |
| piggz | i know, just keeping you busy :D | 10:12 |
| rinigus | oh, I am. will have to go afk for ~1h, I think. piggz , you should submit first to :testing | 10:14 |
| rinigus | and then to :chum proper (after testing compilation will work) | 10:14 |
| rinigus | that way we keep testing and chum in sync | 10:14 |
| lbt | rinigus: as far as licensing goes I think the OBS should be limited to OSI/open-source licenses. Basically as per: https://en.opensuse.org/openSUSE:Build_Service_application_blacklist | 10:14 |
| rinigus | lbt: we should include that in README | 10:15 |
| rinigus | thanks! | 10:16 |
| lbt | yeah - it's mainly common sense | 10:16 |
| lbt | and generally no binary uploads too | 10:16 |
| piggz | rinigus: that did cross my mind, ok | 10:17 |
| rinigus | lbt: bin uploads so far have been databases for prediction used by keyboard. those take long time to generate and huge datasets with texts. those bins (prediction databases) are in github repos as well | 10:19 |
| piggz | lbt: so, noone should be submitting aliendlavik rpms? | 10:21 |
| rinigus | as soon as they are open sourced, should be no problem | 10:26 |
| lbt | sure, databases, images and blobs like that are fine. Just executables. | 10:28 |
| lbt | piggz: ;) | 10:28 |
| Thaodan | lbt: well firmware is fine too | 11:27 |
| rinigus | Thaodan: probably firmware not needed for chum, though | 12:15 |
| Thaodan | The point is they host linux-firmware there too wich contains executable blobs | 14:35 |
| piggz | we all know what we dont want, proprietary apps, and pirated apps | 15:40 |
| fridl | how can I check, which python packages are available in some repositories on OBS (so not only the Chum, but also the "official" repositories. The search seems not to help really. | 16:42 |
| rinigus | fridl: search can be used with osc. as for other ways, you could use zypper on device or SDK | 16:48 |
| fridl | rinigus: ok, ill play round a little more with osc. | 17:05 |
| *** ggabriel is now known as Guest1637 | 17:21 | |
| *** ggabriel_ is now known as ggabriel | 17:21 | |
| HengYeDev[m] | I'm getting "Secrets database is locked" when using Sailfish Secrets | 17:40 |
| HengYeDev[m] | it only happens on some devices | 17:40 |
| HengYeDev[m] | I am using DeviceLock DeviceLockKeepUnlocked to store the collection | 17:40 |
| * HengYeDev[m] < https://matrix.org/_matrix/media/r0/download/matrix.org/uFqbXXhvpxyrFMGNHzSldxdT/message.txt > | 17:41 | |
| piggz | errrr, is gitlab down for anyone? | 20:19 |
| Nico | gitlab.com or git.sailfish.org? | 20:19 |
| piggz | .com | 20:38 |
| piggz | its back now | 20:38 |
| piggz | was giving a 503 | 20:38 |
| Nico | piggz: They usually update on the 22nd, but it has been unstable all day today, which may be related :3 | 21:58 |
| *** amccarthy_ is now known as amccarthy | 23:26 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!