| *** frinring_ is now known as frinring | 02:06 | |
| abranson | NeoChapay: that's not the right version of libzypp to build - you should still be using 12.2 until 17.3.1 gets merged. 14 was never used as it couldn't use the old RPM and was never properly tested. | 07:57 |
|---|---|---|
| abranson | check the version/branch in mer:core | 07:58 |
| NeoChapay | abranson: but why not use 14.35 if i create MR and it work fine on my build ? | 08:00 |
| abranson | NeoChapay: because it was never properly tested, and the 17.3.1 version is nearly ready to merge. | 08:01 |
| NeoChapay | abranson: i must use v12 branch ? | 08:02 |
| abranson | version 14 was merged a couple of years ago, but had to be abandoned because it depended on missing functionality in rpm and upgrading that took a long time. this also held back libsolv and zypper. they all had later version in their master branch. | 08:02 |
| abranson | NeoChapay: yes, but only for a week or so. the new one's nearly ready... | 08:02 |
| NeoChapay | ok | 08:02 |
| abranson | thanks - sorry for the mess. the devops have been living with that for nearly three years I think. | 08:03 |
| NeoChapay | abranson: i think bad way if master was not buils | 08:04 |
| abranson | NeoChapay: yeah, I don't know the details of that, but I believe the CI doesn't really allow rollbacks | 08:15 |
| abranson | and it was completely merged before anyone noticed the problem | 08:15 |
| abranson | but I don't know the details | 08:15 |
| abranson | lbt might know more | 08:15 |
| * lbt isn't sure of the question | 08:21 | |
| NeoChapay | abranson: fail https://build.merproject.org/package/show/home:neochapay:mer:core/libzypp | 08:21 |
| abranson | NeoChapay: should work like this: https://build.merproject.org/package/show/mer:core/libzypp | 08:22 |
| NeoChapay | abranson: with last libsolv not work | 08:24 |
| NeoChapay | abranson: in mer:core libsolv-0.1.0 | 08:24 |
| abranson | NeoChapay: libsolv is also held back yes | 08:24 |
| NeoChapay | abranson: maybe will stop use mamonts poop | 08:25 |
| abranson | stop what sorry? | 08:28 |
| NeoChapay | abranson: i say whay we must use old libsolv when we have patch to solv all error ? | 08:29 |
| abranson | because I'm about to merge libsolv 0.6.34 | 08:31 |
| abranson | NeoChapay: https://git.merproject.org/mer-core/libsolv/merge_requests/3 | 08:31 |
| NeoChapay | abranson: https://www.youtube.com/watch?v=ZXsQAXx_ao0 ^_^ | 08:34 |
| abranson | NeoChapay: I should be testing it now :) | 08:35 |
| NeoChapay | abranson: ok...i wait....now in my clone mer-core i will contunue use my branch of libzypp now | 08:38 |
| thinhx2 | hj | 08:50 |
| abranson | NeoChapay: yeah that's a good idea, then you can upgrade to the latest when they're ready | 09:24 |
| spiiroin | review appreciated: https://git.merproject.org/mer-core/mce/merge_requests/79 | 10:53 |
| spiiroin | ^ reduce chances of flickering during display power off | 10:53 |
| mal | some WIP merge requests https://git.merproject.org/mer-core/libsdl/merge_requests/2 and https://git.merproject.org/mer-core/wayland/merge_requests/1 and a new repo that is needed by sdl https://git.merproject.org/mal/wayland-protocols | 11:46 |
| NeoChapay | mal: wooooow! | 12:03 |
| r0kk3rz | i think most things with new wayland need that wayland-protocols package | 12:03 |
| r0kk3rz | gtk3 does at least | 12:04 |
| * NeoChapay whispers quietly from the corner Qt 5.9 or 5.11 ? | 12:07 | |
| r0kk3rz | 5.9 is whats being put in the repos | 12:07 |
| mal | NeoChapay: there are a lot of Qt 5.9 MRs open in mer-core already | 12:07 |
| pvuorela | mal: added some comments. | 12:07 |
| mal | pvuorela: I replied already to SDL questions, need to fix the issues you noticed | 12:08 |
| pvuorela | mal: could perhaps start already with wayland-protocols if it works with current wayland we have? | 12:08 |
| mal | pvuorela: should I remove the .changes file | 12:08 |
| pvuorela | you can keep it, just no need for new changes. | 12:08 |
| r0kk3rz | mal: get lbt to mirror the repo | 12:09 |
| r0kk3rz | *upstream repo | 12:09 |
| mal | I still find mirroring the repos a bit odd | 12:10 |
| lbt | you know you only need a mirror if you use the awful submodule approach ? | 12:10 |
| r0kk3rz | awful? | 12:10 |
| mal | lbt: submodule is awful? | 12:10 |
| lbt | horrible ? | 12:10 |
| r0kk3rz | lbt: are we going to change formats again again again? | 12:11 |
| lbt | anything that stores .patch files in git is awful :) | 12:11 |
| r0kk3rz | ideally there shouldnt be any patches | 12:12 |
| mal | pvuorela: lbt so should i use subtree instead of submodule for wayland and wayland-protocols? | 12:12 |
| lbt | subtree is worse :( | 12:12 |
| pvuorela | NO | 12:12 |
| pvuorela | :) | 12:12 |
| r0kk3rz | theres no patches, so just mirror the upstreams and is fine | 12:13 |
| mal | lbt: then what is better than submodule? | 12:13 |
| lbt | a branch with local patches | 12:13 |
| pvuorela | but let's not go there with vanilla upstream packages. | 12:14 |
| mal | pvuorela: lbt then the other question, should we mirror wayland and wayland-protocol upstream? | 12:14 |
| lbt | pvuorela: yeah - that's true | 12:14 |
| r0kk3rz | lbt: wasnt there a time when mer did that with packaging branches? | 12:14 |
| pvuorela | i'm myself ok mirrored or not. | 12:14 |
| lbt | r0kk3rz: yeah ;( | 12:14 |
| lbt | give me urls and I'll mirror it | 12:14 |
| lbt | I just spent the morning making sure mirrors are properly updated and track upstream adding/removing branches | 12:15 |
| mal | https://github.com/wayland-project/wayland-protocols and https://github.com/wayland-project/wayland | 12:15 |
| mal | although I still don't really understand the point of mirroring those | 12:16 |
| mal | except the rare case of some network issues | 12:16 |
| r0kk3rz | is github the proper upstream? or is freedesktop anongit? | 12:16 |
| mal | r0kk3rz: it seems like it | 12:17 |
| mal | lbt: don't mirrow those | 12:17 |
| mal | those are a mirror already | 12:17 |
| r0kk3rz | the github account says they are mirrors of freedesktop.org | 12:17 |
| mal | lbt: git://anongit.freedesktop.org/wayland/wayland-protocols and git://anongit.freedesktop.org/wayland/wayland | 12:18 |
| mal | r0kk3rz: I did use freedesktop.org on my repos for the submodule | 12:18 |
| r0kk3rz | yeah i saw | 12:19 |
| r0kk3rz | which is why i was surprised when you told lbt to mirror github :P | 12:19 |
| lbt | https://git.merproject.org/mirror/wayland | 12:20 |
| lbt | https://git.merproject.org/mirror/wayland-protocols | 12:20 |
| mal | r0kk3rz: some glitch in my brain | 12:21 |
| r0kk3rz | :) | 12:21 |
| r0kk3rz | thanks lbt | 12:22 |
| mal | pvuorela: I think including wayland-protocols shouldn't affect anything but need to test that | 12:41 |
| mal | that just provides extra functionality to wayland | 12:42 |
| pvuorela | mal: should be unlikely if nothing depends on it :) but i'll check that it actually builds without e.g. updated wayland. | 12:42 |
| pvuorela | btw, ldconfig dependencies still there. | 12:42 |
| mal | pvuorela: hmm, I thought I removed those | 12:43 |
| pvuorela | you removed execution. | 12:43 |
| mal | ah | 12:43 |
| pvuorela | and now succesfully built x86 and armv7 on jolla obs. | 12:43 |
| mal | pvuorela: now the dependencies are gone | 12:45 |
| pvuorela | mal: thanks. | 12:45 |
| pvuorela | lbt: can we get wayland-protocols repository on mer-core? i can create PR for maintainers. | 12:45 |
| lbt | sure | 12:46 |
| lbt | https://git.merproject.org/mer-core/wayland-protocols | 12:47 |
| pvuorela | https://git.merproject.org/mer-core/Maintainers/merge_requests/232 | 12:49 |
| lbt | merged | 12:49 |
| mal | pvuorela: should I now create a MR for the wayland-protocols or how is the first version handled? | 13:24 |
| r0kk3rz | mal: nah its done | 13:27 |
| pvuorela | mal: i'll push from your repo to mer-core. | 13:29 |
| pvuorela | mal: there. | 13:52 |
| mal | thanks | 13:52 |
| mal | pvuorela: probably needs a tag also? | 13:52 |
| pvuorela | yea, i'll do. | 13:53 |
| mal | pvuorela: actually just noticed a tiny issue which is not really a bad thing, the group in spec is not valid it seems, only issue is a warning in build log | 13:58 |
| pvuorela | wouldn't be the first package with warnings for group :) | 13:59 |
| mal | hmm, actually, no it's valid but for some reason there is a warning | 13:59 |
| mal | I think the issue is that rpmlint wants python and it's not in build requirements so that fails | 14:00 |
| mal | ah, the devel package has the wrong group | 14:01 |
| mal | but anyway quite a small issue, maybe during next update some day we'll fix that | 14:02 |
| r0kk3rz | pvuorela: btw i tried to build latest glib with meson, but our meson version is already too old and new meson needs newer python3 :( | 14:11 |
| pvuorela | :D | 14:13 |
| r0kk3rz | tbh python 3.5 has been out a while | 14:17 |
| pvuorela | yea, we should really update python3 too. | 14:18 |
| r0kk3rz | pvuorela: btw, do you know of a good test for cairo? | 14:22 |
| pvuorela | r0kk3rz: not a simple one but at least gecko uses it. | 14:31 |
| r0kk3rz | does sailfish-documents use it? it has some PDF handling in it | 14:32 |
| pvuorela | sailfish-office uses poppler for pdfs and i see poppler depending on gecko. | 14:34 |
| r0kk3rz | hmm ok | 14:34 |
| pvuorela | no idea what poppler does with it though. | 14:34 |
| r0kk3rz | ah poppler pulls in cairo, | 14:36 |
| pvuorela | um, that's what i was supposed to say instead of gecko dependency. | 14:37 |
| r0kk3rz | yes i figured | 14:37 |
| r0kk3rz | ive got a decent update for it anyway | 14:38 |
| pvuorela | nice. | 14:39 |
| pvuorela | for what i've updated cairo, think i've just tested that gecko still builds and works. | 14:40 |
| r0kk3rz | it builds fine against gstreamer at least | 14:40 |
| r0kk3rz | documents still works, and i'll check the browser | 14:41 |
| *** martyone_ is now known as martyone | 19:58 | |
| *** Nokius_ is now known as Nokius | 21:17 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!