Sunday, 2018-12-30

T4linusdan was added by: linusdan01:57
T4<BirdZhang> @linusdan line 31: ERROR: CONFIG_IKCONFIG_PROC is invalid02:03
T4<linusdan> Hi Bird! … So, I do not know if I put the configuration in the wrong place or it was the same value … In mer-kernel-check passed without errors02:07
T4<BirdZhang> you need change it in your kernel, and rebuild hybris-boot02:08
*** ChanServ sets mode: +v T402:13
T4Mufga1 was added by: Mufga102:15
T4<linusdan> (Photo, 447x28) Is already done. And compiled also with this configuration. … I can not even put it as N because hybris-boot needs it … I'm lost :/02:16
T4<BirdZhang> can you share your kernel source github link ?02:16
T4<linusdan> Of course! … Its here: …
T4<BirdZhang> so need enable CONFIG_IKCONFIG and CONFIG_PROC_FS02:19
T4<linusdan> THANKS! … I'll look the others too! Did not know I had a summary for kernel dependencies. I searched before and did not find it! … Can you suggest any book so I can learn more about kernels? I do not understand almost anything02:32
T4<BirdZhang> and and logs are very helpful. i know few about kernels.02:35
T4<linusdan> My heart beat faster … 😍😍😍😍😍😍😍😍 … THANKS THANKS THANKS ❤️❤️❤️02:39
T4<BirdZhang> you are welcome ;)02:40
UmeaboyThe instructions in the HADK to do export PLATFORM_SDK_ROOT=/srv/mer followed by curl -k -O seems to contain a typo or am I wrong?03:42
UmeaboyI mean the first thing you do is to add export PLATFORM_SDK_ROOT="/srv/mer" into the hadk.env file.03:42
UmeaboyThat contains quotes.03:43
UmeaboyI'm sorry if I'm wrong.03:44
T4Null0101 was added by: Null010103:49
T4louisdemedicis was added by: louisdemedicis04:23
UmeaboyCan anyone confirm if that's the case or not?05:12
T4louisdemedicis was added by: louisdemedicis06:41
T4WaseemAlkurdi was added by: WaseemAlkurdi06:48
T4dohniks was added by: dohniks08:40
*** ChanServ sets mode: +v T408:44
malUmeaboy: what typo?10:06
wdehooghi, I have audio problems on bacon. when playing music from streams using qmultimedia (shoutcast, somafm) the11:52
wdehoogaudio always has hickups. This has always been a problem.11:52
wdehoogI have a patch for qmultimedia that adds support for QT_GSTREAMER_PLAYBIN_FLAGS11:52
wdehoogand a  config file .config/qtmultimedia/settings.conf with support for11:52
wdehoogflags, buffer-duration, buffer-size, ring-buffer-max-size, connection-speed11:52
wdehoogwhen I use buffer-size=256000 , flags=0x182 the audio is ok (no hickups)11:52
wdehoogNobody else seem to suffer this problem so maybe there is a much better solution.11:52
wdehoogadding the playbin buffer also drastically speeds up filling the buffer of the qml audio object11:58
T4<MarcoDS_bit> Hi all again, could you please help me with this error?
malthat file should be provided by external/vim13:20
T4<MarcoDS_bit> Tried re-syncing external/vim but I get the error anyway13:22
T4<MarcoDS_bit> Mhhh13:22
T4<MarcoDS_bit> Oh and I don't have vim in my manifest.xml is that normal?13:23
malit should be in the snippets manifest13:25
T4<MarcoDS_bit> Yep it is there and it is uncommented, but not working🤔13:28
mal@MarcoDS_bit have you ever made a successful build yet?13:33
T4<MarcoDS_bit> Nope, just re-downloaded all the stuffs for building sailfish13:34
malcan you give your local manifest13:34
T4<MarcoDS_bit> Pastebin or file?13:35
malpastebin is fine13:35
T4<MarcoDS_bit> :P  …
malI mean local manifest, not the actual manifest13:38
mallocal manifest as in the file where you have the device repos13:38
malin .repo/local_manifests13:39
T4<MarcoDS_bit> Ouch sorry,
T4<linusdan> Hi all, … I was able to solve the kernel problem! Now I have this problem: …
mal@linusdan do you use latest build target?13:52
T4<linusdan> @MarcoDS_bit [Oh and I don't have vim in my manifest.xml is …], If all dependencies for your device are not met, the repository clone will be requested. Do until the compilation stops fill the patience :) … While at manifest file: Yes, to avoid downloading unnecessary things13:55
T4<linusdan> @mal [@linusdan do you use latest build target?], Yes,
T4<linusdan> Mer-hybris repositories are also up-to-date13:59
mal@MarcoDS_bit the vendor repo is wrong, neither path or name should have whyred, the repo is vendor specific not device specific14:05
T4<linusdan> In name="TheMuppets/proprietary_vendor_xiaomi/whyred" exclude whyred14:12
T4<linusdan> If you just want the whyred folder, it would be better to make a fork and delete what you do not need14:16
*** ChanServ sets mode: +v T414:27
T4<MarcoDS_bit> Ouch yeah I'm changing it now, but could it be related to the vim problem?15:34
T4<linusdan> No, just the path error15:39
r0kk3rzwdehoog: make a pr in mer and talk to abranson about it15:46
T4<linusdan> rokk3rz, did you mean me or Marco?15:51
T4<MarcoDS_bit> @linusdan [rokk3rz, did you mean me or Marco?], None of us15:52
malI saw the wim error in channel logs from quite a while back and they just worked around it in an ugly way16:13
T4<MarcoDS_bit> Manually copying files?16:15
wdehoogr0kk3rz: first I'd like to know if this is a problem on other devices as well16:19
malwdehoog: is there some app that can be used for easy testing16:20
wdehoogmal: for example sailsoma (from openrepos). but I see this problem for more then a year on bacon so I doubt it also happens on another device16:23
r0kk3rzwdehoog: yeah, thats why i said talk to andy about it16:28
r0kk3rzits ok if its uncommon, being able to tweak things in configs is useful16:30
malwdehoog: how often do you hear those hiccups in the audio?16:34
malI had some during the first 10-20 seconds of playback but then it seems ok16:35
wdehoogyes at the start it is most prominent, but it takes more then 20s for me to go away16:38
wdehoogmal: high bitrate streams (320 mp3) almost never reach 100 bufferprogress16:39
wdehoogmal: for me with a small buffer (256K) the problem is gone16:40
malwdehoog: which channel uses 320 bitrate?16:40
wdehoogma: with other apps, I created shoutcast-sailfish, try to remain qml only16:41
wdehoogsome streams in the Electronic | Techo list have 32016:42
wdehoogbut the current version of my app behaves weird due to buffering16:42
malbut even with that quick test I made it seems that buffer could use improvements16:45
wdehoogmal: thanks for testing. lets see what abranson has to say. I guess now it is holidays16:48
T4<linusdan> I solved my problem of the 'geoclue-providers-hybris' repository by reversing the last pull request ☺️17:15
malok, so it probably need newer release, maybe the next that will be made available or something17:28
T4saukkom was added by: saukkom18:03
T4<MarcoDS_bit> New error, mhh18:09
T4<MarcoDS_bit> Ok solved using the ugly way lol18:24
T4<srmane4444> Ох его опять нету18:27
T4Carmelo (MISSING @USERNAME! was added by: Carmelo (MISSING @USERNAME!
T4<MarcoDS_bit> pt.2
T4<linusdan> The error for the glory! … sed not create ks file …
malyou missed one >18:43
malthere should be one > before $KS near the end of sed command18:44
mali.e. forwarding the output to file defined by $KS18:44
Umeaboymal: When you begin with making the hadk.env file you add export PLATFORM_SDK_ROOT="/srv/mer" and then when you get to the PlatformSDK installation you do export PLATFORM_SDK_ROOT=/srv/mer18:47
UmeaboyI don't know about you, but I'm missing quotes.18:48
maldoes it really need quotes in the latter case?18:52
UmeaboyI'm not an expert so you tell me.18:53
malnever heard anyone having issues so I assume that is fine18:54
r0kk3rzquite sure they are equivalent18:56
UmeaboyAny chance of having my PR merged?
r0kk3rzonce we know its right18:57
malfirst of all squash the commits to one and make sure the commit message follows the usual format in most of the commits [codename] Add Some device to fixup-mountpoints18:57
Umeaboymal: I can't find the Squash and merge option in my PR.19:03
r0kk3rzshould really go through all those PRs at some point19:04
malUmeaboy: git rebase -i some_hash and then do the needed stuff to commit list and after the commits are ok force push to github19:05
malr0kk3rz: indeed, many seem ok19:05
r0kk3rzi find it easier to use the HEAD~X macro, so for the last 5 commits you do HEAD~519:06
malthat works also19:06
malUmeaboy: there are many guides online how to do squashing using git rebase19:06
malUmeaboy: why did you close the PR, like I said you should have just force pushed to the same branch you used and the PR would have updated automatically19:15
UmeaboyI opened a new one with just one commit.19:18
malyou should learn the basics on git so that is not needed in the future19:20
malUmeaboy: why did't you follow the commit syntax I told?19:20
UmeaboyI could've done that, but chose to start over instead.19:21
malso now you can learn how to change the commit message using git commit --amend and then git push --force19:21
UmeaboyRight. I was aware of the git commit --amend command from before. I just don't use it.19:22
r0kk3rzwhy not?19:22
malamending is very common thing to do19:22
malso is rebasing19:22
maland interactive rebasing19:23
UmeaboyWhy rebase if you can undo what you've done and learn NOT to do the mistakes again? Just saying. I'm not expecting you to agree, it's just how I work.19:26
r0kk3rzbecause its less effort :P19:27
malconsider it this way, if others review the changes they would have to start over as they cannot see what changed to the previous version if you always make new PRs, also you rarely get finished code on first try, it's easy that typos happen or that others think there is a better way to do the same thing so modifying the PR is very common19:28
r0kk3rzyeah, github is set up for that kind of process19:29
UmeaboyYeah, I just prefer stuff to be as close to perfect as it can get before it gets merged so you won't have to update it much more than needed.19:29
malthat might work for simple changes but not for anything bigger19:29
malyou just need to learn that rebasing and amending is going to be needed quite often19:30
UmeaboyYeah, and my PR was simple this time.19:31
T4<linusdan> linusdan: <mal> The error persists. The file is generated, but not read.19:31
r0kk3rzdont be so precious, you know its not important when mal says 'just amend it' :P19:31
UmeaboyYeah. I know. Problem solved now so now I'll just wait for it to be merged.19:32
malUmeaboy: but you did't rewrite the commit message again yet19:34
kimmoli(and it is "Add" not "Added")19:36
kimmolidont tell what you did, tell what the commit does19:36
malthat's what I said when I told the correct format: [codename] Add Some device to fixup-mountpoints19:38
UmeaboyDoes it look OK now?19:41
malUmeaboy: what did I say about amending19:42
maland no19:42
malthe commit message is still wrong19:42
UmeaboyI don't use the terminal. I do it straight to the github website.19:42
malwell then it won't work19:43
malhow is it so difficult to use [codename] Add Some device to fixup-mountpoints19:43
mali.e. in your case [maple] Add Sony Xperia XZ Premium to fixup-mountpoints19:44
malthe dual and single sim versions probably use the same codename19:44
UmeaboyYeah, they do.19:45
*** ChanServ sets mode: +v T420:28
abransonwdehoog, mal: fine tuning those buffers sounds good. leszek did some adjustments there in the past that we keep as a patch.20:31
abransonjust checked - that was deactivating the max-size-time20:33
wdehoogabranson: this is my "fix"
abransonwdehoog: is that affecting the same thing but from the higher end?20:35
wdehoogabranson: looks like it. I only wanted changes for the qml mediaplayer and wanted to see which setting would help so that is why I used a settings file20:37
abransonmight be a good idea to add those values to leszek's patch and see if it helps. some things use gst directly after all.20:46
tortoisedocabranson : are you mantainer of sb2+21:06
wdehoogabranson: you mean for my phone (oneplus one) only? I hate all those hardcoded stuff.21:06
wdehoogabranson: maybe something like in /var/lib/environment/nemo/60-multimedia.conf ?21:06
wdehoogbut then for gstreamer21:06
tortoisedocabranson : at least from the mantainers list you show up; would you be interested to take a look at this mr :
tortoisedoc(its a two-liner fixing a missing dont expand last path item flag  on the remove gate )21:10
maltortoisedoc: afaik usually having a mer bug id in the commit message is wanted21:12
tortoisedocmal : hmhm ok21:27
tortoisedocmal : where can i fill in a mer bug?21:27
tortoisedocthere was a bugzilla somewhere iirc21:28
tortoisedocthanks mal just got there myself .)21:28
malthere is the scratchbox2 component in Mer core category21:29
malso file it under that21:29
tortoisedocmal : done ,
merbotMer bug 1997 in scratchbox2 "The bitter end expansion: Last path of symlink is always expanded" [Critical,New]21:36
tortoisedocmal : how can I link it to my mr?21:37
tortoisedoci recall from bitbucket, jira tickets are automagically linked to commits via the id's21:39
tortoisedoci dont know if something similar is available for bugzilla / gitlab21:40
maltortoisedoc: just add MER#1997 to the end of the commit message, preferrably to the first line (so it shows nicely)21:41
maltortoisedoc: maybe reformat the commit message so the first line contains a short message and any further longer description in the following lines21:42
maltortoisedoc: also check the other commits in sb2 repo for the normal formatting i.e. [something] in the beginning of the commit message21:43
malthat makes it appear properly in changelogs21:44
tortoisedocmal : added [gates], as the change pertains to taht21:44
tortoisedocalso added MER bug in it21:45
maltortoisedoc: in commit message, not PR title (which can be anything but usuall close to commit message)21:46
tortoisedocnow what? :)21:47
tortoisedocmal : ^21:47
malcommit message still looks wrong, you only added [gates] to PR title21:48
malmaybe the commit message could be [gates] Add missing flags to remove gates. MER#1997 and then on second line you can say why21:49
malor something like that21:50
malso the first line is not too long21:50
malit's messy in my opinion if the message shown here is not complete but instead part of it is hidden
tortoisedocmal : you think title is ok?21:52
malyes, PR title is ok, just adapt the commit message21:53
maltortoisedoc: sorry for bugging, I just like nice and clean commit history :)21:54
tortoisedochehe it's ok :) im not allergic to nitpicking :)21:54
tortoisedocmal : how about now?21:55
maldid you force push the change?21:55
tortoisedocedited in-place21:55
tortoisedoc(the commit comment / title I mean)21:56
malI can't see any difference in the commit message, you always just edit the PR title21:56
tortoisedocbut yes, I force-pushed a few times21:56
tortoisedocI have21:57
tortoisedocAdd the flag to avoid resolution of last part of path; see MER#199721:57
tortoisedocas the first comment line21:57
tortoisedocpacked and juicy :D21:57
malyou are mixing things, I'm talking about te git commit message not the PR21:57
malso git commit --amend and then edit the commit message and then git push --force21:58
tortoisedocwill do!21:59
malI thought it was clear what I meant when I said commit message22:00
tortoisedocits too late for this, my bad :P22:00
tortoisedocmal : whats the max line size in commit history usually? 80 chars?22:01
tortoisedocmal : repushed22:02
tortoisedocmal : btw thanks for taking the time to guide me through this :)22:02
maltortoisedoc: 80 or 72 I think22:06
maltortoisedoc: looking good now, let's wait for someone who maintains that to check it22:07
T4<linusdan> mal: i9100 is coming! My error while trying to generate the kickstarter file was because it had extra space between the \ and the $ KS hahaha 👌🏼 🙃 … Tkanks!22:15
mal@linusdan you have to be careful when copying multiline commands from hadk22:16
T4<linusdan> I'll take more care at other times :)22:23
T4<linusdan> Another problem. In the root filesystem compilation appeared: … Q: Failed to apply RootPasswordConfig, skip and continue? … If I confirm, will I be able to configure later or will I have to do something else?22:42
r0kk3rzyou mean running mic?22:45
T4<linusdan> yes, i'm running mic :)22:45

Generated by 2.17.1 by Marius Gedminas - find it at!