| 24 Mar 2018 |
 @memelover69:banter.city | Thanks, I already made a bot using the python sdk, so I just needed to modify a few things to get it to work like this. It just calls the build script when you use the build command. | 22:24:54 |
| @memelover69:banter.city | It reports the exit codes as well, which I think will be useful. | 22:25:12 |
 gr4yg00se | Did you fork the official moto X CM13 repo? | 22:24:43 |
| gr4yg00se | Yea exit codes will be helpful | 22:24:53 |
| @memelover69:banter.city | I just forked the kernel repo. | 22:26:54 |
| @memelover69:banter.city | If we're just patching CVEs, I don't think we'll need to change more than that. | 22:27:21 |
| gr4yg00se | Fair enough | 22:25:49 |
| gr4yg00se | https://github.com/LineageOS/android_kernel_motorola_ghost/tree/cm-13.0 this is the one right? | 22:35:19 |
| @memelover69:banter.city | Yup | 22:37:51 |
| gr4yg00se | Cool | 22:36:29 |
| 25 Mar 2018 |
| @memelover69:banter.city | Alright, everything it set up! It takes around 6:20 to make a build, but it does work. I've forked the kernel to here: https://github.com/meme-lover/android_kernel_motorola_ghost, since I don't think lineage will let us update their repo anymore. We can use the cve tracker from https://cve.lineageos.org/android_kernel_motorola_ghost, and I'll eventually work on making my own. | 04:21:35 |
| @memelover69:banter.city | I just realized that the CVE tracker is lying about some of them, at least. It's patched against the first cve listed, at least. | 04:26:09 |
| gr4yg00se | So should I fork your repo? | 04:47:09 |
| @memelover69:banter.city | Yes | 04:49:23 |
| gr4yg00se | Cool | 04:47:42 |
| gr4yg00se | Also if we go through the proper review of lineage we can’t send them a pull request? | 04:50:10 |
| @memelover69:banter.city | We don't? | 04:52:28 |
| @memelover69:banter.city | This is going to be unofficial | 04:52:33 |
| gr4yg00se | Oh okay.. I thought if lineage is willing to pull might as well send them a pull request. Unofficial works though | 04:51:28 |
| @memelover69:banter.city | Oh, I misunderstood. We can see if we can push to that repo. | 04:53:54 |
| gr4yg00se | Cool | 04:52:50 |
| @memelover69:banter.city | [1:01] <memelover> If I were to create pull requests for a recently now unsupported kernel, would anyone go through the process of committing them, or should I run my own repo?
[01:02] <@zifnab> we don't accept PRs, without a device maintainer someone may or may not look at it
[01:03] <@zifnab> feel free to throw them on review.lineageos.org though
[01:03] <@zifnab> https://wiki.lineageos.org/usinggerrit-howto.html
[01:03] <@zifnab> github's just a dumb mirror for us | 05:09:16 |
| @memelover69:banter.city | By the way, the builds are at http://ghost.headpat.moe:8000 I was having issues with using port 80 for some reason. | 05:11:21 |
| gr4yg00se | I guess it’s simpler keeping it unofficial then and we can throw in the patches whenever we feel like | 05:40:08 |
| gr4yg00se | By the way, the builds are at http://ghost.headpat.moe:8000 I was having issues with using port 80 for some reason - 👍🏼 | 05:40:33 |
| @memelover69:banter.city | Sounds good to me | 05:43:03 |
| gr4yg00se | You might want to hide user group and permissions info from the build website. I know it’s almost harmless but still | 05:42:11 |
| @memelover69:banter.city | I didn't think to do that... I'll look into it. | 05:44:47 |
| gr4yg00se | 👍🏼 | 05:43:17 |
| @memelover69:banter.city | So, I started signing the builds, but the contents of the signed zip seem to differ a lot from an unsigned zip... You can see the difference in the files that I uploaded. Any ideas? | 17:39:49 |
