| dcaliste | Good morning pvuorela, sorry for the late coming. | 07:09 |
|---|---|---|
| *** ggabriel is now known as Guest284 | 07:21 | |
| alinmelena[m] | what is the way to get something in chum | 07:52 |
| alinmelena[m] | https://github.com/black-sheep-dev/harbour-quartermaster | 07:52 |
| alinmelena[m] | already has an openrepos | 07:52 |
| dcaliste | alinmelena[m] : https://forum.sailfishos.org/t/announcing-sailfishos-chum/7381 | 08:10 |
| alinmelena[m] | dcaliste i know it but since is not my package I was wondering what is the process | 08:22 |
| alinmelena[m] | not to say I will need to recover my old singup details | 08:24 |
| dcaliste | Well, I guess it's more or less the same, create a _service file in your OBS home for it, then ask for inclusion of it into chum:testing. You'll get owner of it later on in sailfishos:chum:testing but you can ask piggz to add other people also. | 08:25 |
| alinmelena[m] | ok | 08:28 |
| alinmelena[m] | now I need to get an account | 08:28 |
| piggz | hello, wassup | 08:53 |
| piggz | ah, so also, there is good docs/guide on the chum github... | 08:53 |
| piggz | alinmelena[m]: see https://github.com/sailfishos-chum/main | 08:54 |
| Renaud[m] | piggz: Hi, could you disable build of emacs on chum for sfos < 4.1 ? I don't think I'll be able to fix those. You can copy and paste meta configuration from chum:testing. | 08:56 |
| piggz | ok | 08:58 |
| Renaud[m] | thanks | 08:59 |
| piggz | Renaud[m]: do you want to keep the ok x86 builds? | 09:12 |
| Renaud[m] | as long as they build fine, why not :) | 09:13 |
| piggz | done | 09:24 |
| Renaud[m] | thank you. I was wondering if you'd like to have a workaround for the faulty builds (emacs27 built fine, but not emacs28) or if we can consider those old versions deprecated? | 09:26 |
| piggz | im not too worried, up to you as maintainer really :) | 09:35 |
| Renaud[m] | okay, thanks :) | 09:40 |
| alinmelena[m] | piggz i suspect first I need an account | 09:56 |
| alinmelena[m] | i try to resurect my old stuff | 09:56 |
| piggz | alinmelena[m]: yes ... lbt will need to do that <cough> | 09:56 |
| alinmelena[m] | my username on the old build system was alin | 09:56 |
| alinmelena[m] | yes I know... | 09:56 |
| alinmelena[m] | I am still hopping to get fortran enabled in the gcc build | 09:57 |
| piggz | alinmelena[m]: well, https://build.sailfishos.org/project/show/home:alin still exists, so, you ened to remember your password :) | 09:57 |
| alinmelena[m] | he he | 10:14 |
| alinmelena[m] | that I do not remember so I do not see it | 10:14 |
| alinmelena[m] | * not see a way to reset it | 10:14 |
| alinmelena[m] | let me check some stuff | 10:15 |
| alinmelena[m] | nope | 10:20 |
| alinmelena[m] | will need reseted | 10:20 |
| alinmelena[m] | piggz: recovered | 10:40 |
| pvuorela | dcaliste: hey sorry, totally forgot this was the week to get back on the weeklies. | 10:52 |
| dcaliste | pvuorela, no problem. We can discuss whenever it is fine for you (and me), this week or on next slot. | 10:53 |
| pvuorela | dcaliste: sure. noticed you did some more notebook api adjustments which i'll need to check. was concentrating first on getting that set first in. | 10:56 |
| alinmelena[m] | ok things fail but run | 10:56 |
| alinmelena[m] | back in building | 10:56 |
| dcaliste | Yes, since I was touching the servicehandler API by moving away from Notebook::Ptr, I considered that simplifying the API of the same functions can be done in one run, particularly in the repos that will need to be updated thereafter. Sorry if it's an inconvenience for you… | 10:59 |
| pvuorela | need to check. seemed anyhow from the nemo-calendar pr that the set is still a bit wip. | 11:01 |
| dcaliste | Indeed, using the new API in nemo-qml-plugin-calendar hightlighted some const issues that I corrected this morning. I need to create a PR for buteo-sync-plugins-social also and for the birthday contactsd plugin. After that changes will have to be propagated to EAS bits from your side. I don't have access to it. | 11:04 |
| pvuorela | sure. | 11:04 |
| dcaliste | I'm leaving for lunch now but we can continue to discuss one or two points later in the afternoon. | 11:05 |
| pvuorela | alright. | 11:05 |
| alinmelena[m] | can someone please be critical of this | 18:17 |
| alinmelena[m] | https://build.sailfishos.org/project/show/home:alin:lavello | 18:17 |
| alinmelena[m] | before i start debugging | 18:17 |
| mal | you are missing a dependency from the spec at least | 18:18 |
| mal | also for cleaner spec I would use %make_build instead of "make %{?_smp_mflags}" | 18:19 |
| alinmelena[m] | mal I did not right the spec... I will fork and clean it up I wanted just to know if i Put the right targets | 18:37 |
| alinmelena[m] | s/right/write/, s/i/I/, s/Put/put/ | 18:52 |
| alinmelena[m] | one must love the irony of this + FFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -march=armv8-a -I/usr/lib64/gfortran/modules' | 19:23 |
| alinmelena[m] | lbt ^ | 19:24 |
| mal | what is the issue? | 19:28 |
| alinmelena[m] | the fortran include.. but the obs does not provide fortran.. | 19:39 |
| alinmelena[m] | was one of my old jokes.. in past I used to ask lbt to enable fortran on the gcc package | 19:40 |
| alinmelena[m] | one thing I am confused about packaging.. is the yaml or the .spec that counts these days.. thought in the past yaml was used to generate the spec | 19:41 |
| alinmelena[m] | but i see some overlap these days | 19:42 |
| mal | alinmelena[m]: yaml is a bit obsolete and just normal spec is recommended | 20:20 |
| alinmelena[m] | cool this is how I got it green | 20:57 |
| alinmelena[m] | I will test and do a pr/mr to the original | 20:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!