**** BEGIN LOGGING AT Tue Aug 27 02:59:57 2019
Aug 27 07:49:03 <mckoan> good morning
Aug 27 09:35:11 <jklare> Hi
Aug 27 09:35:54 <jklare> I am currently trying to find the related Issue to this patch http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd/0001-networkd-fix-link-up.patch?h=master
Aug 27 09:36:03 <jklare> The commit message says it closes #12504 and mentions #12505
Aug 27 09:36:11 <jklare> 	If i go to bugzilla.yoctoproject.org and search for these issues, both of them are there but have nothing to do with this patch
Aug 27 09:36:22 <jklare> i would like to backport these patches to systemd 241 to be able to use systemd link up in the warrior release
Aug 27 09:36:31 <jklare> can anybody help me here and point me into the right direction?
Aug 27 12:12:54 <vmeson> jklare: did you ask Rickardo about the defects? Anyway, you don't need the defect IDs to backport to warrior, right?
Aug 27 12:14:35 <jklare> vmeson i wanted to use the old issue to follow up on the same thing instead of opening a new one
Aug 27 12:15:14 <jklare> vmeson Rickardo is the right person to talk to when trying to backport i assume? (i am completely new here :) )
Aug 27 12:17:00 <vmeson> jklare: Ricardo is the patch author. For backporting, you do the cherry-pick and send to the list with the warrior prefix, CCing Armin is a good idea.
Aug 27 12:17:42 <jklare>  vmeson ok thanks, i will try to do so
Aug 27 12:17:46 <vmeson> Armin Kuster <akuster808 at gmail.com>
Aug 27 12:18:09 <vmeson> jklare: cool, thanks for pitching in and asking!
Aug 27 12:20:10 <vmeson> jklare: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded <-- can be useful if you are new.
Aug 27 12:21:50 <vmeson> This commit would go to the openembedded-core list rather than openembedded-devel
Aug 27 12:21:58 * vmeson heads to the office.
Aug 27 12:23:48 <jklare> vmeson thanks for the help, will try to walk through that :)
Aug 27 14:22:19 <jklare> vmeson hi again
Aug 27 14:22:57 <jklare> i submitted a patch, but i think i missed something during the formatting since it does not mention that this is targeting warrior
Aug 27 14:23:21 <jklare> vmeson is there a way to edit a submitted patch?
Aug 27 14:25:55 <vmeson> jklare: No. Just reply to the patch, explaining the error briefly and saying that you'll submit a v2.
Aug 27 14:26:24 <vmeson> the patches are merge manually even though patchtest does some inspection and patch analysis.
Aug 27 14:27:05 <jklare> vmeson ok, but i think i missed the part in the docs that explain how i can target a new patch to a specific branch
Aug 27 14:27:33 <jklare> vmeson this is the patch i am talking about https://patchwork.openembedded.org/patch/164334/
Aug 27 14:27:52 <jklare> i based it on top of the warrior branch
Aug 27 14:28:04 <jklare> but that does not seem to be reflected anywhere now
Aug 27 14:28:11 <vmeson> jklare: like this: [OE-core] [thud][PATCH] libedit: Add native and nativesdk to BBCLASSEXTEND
Aug 27 14:29:10 <vmeson> you set that in git-send email: git format-patch <COMMIT_HASH> -1 --subject-prefix="<BRANCH_NAME>][PATCH"
Aug 27 14:29:26 <vmeson> from: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Backporting_fixes_to_stable_releases
Aug 27 14:29:34 <vmeson> jklare: ok?
Aug 27 14:30:50 <jklare> vmeson working on it, still not sure how i will send the email as a v2
Aug 27 14:30:57 <jklare> vmeson but lets see what happens :)
Aug 27 14:31:05 <jklare> vmeson thanks for the help :)
Aug 27 14:32:17 <jklare> vmeson i generated a patch file now
Aug 27 14:36:27 <jklare> vmeson looks better :)
Aug 27 14:36:38 <jklare> vmeson does it look ok for you? https://patchwork.openembedded.org/patch/164336/ 
Aug 27 14:36:52 <jklare> vmeson i mean just the way it is submitted, not the content itself
Aug 27 14:38:31 <vmeson> jklare: yes, the format is as expected now for warrior. Have you build and booted and tested systemd with this update? What machines?
Aug 27 14:40:11 <jklare> vmeson i have build an image for a agema-ag7648 switch by adding an additional layer which modified exactly that SRCREV and it worked fine
Aug 27 14:42:56 <jklare> vmeson but i guess my commit message will fail the patchtest.... sry 
Aug 27 14:43:12 <jklare> vmeson will push v3 soon
Aug 27 14:44:25 <vmeson> jklare: I don't see a patchtest email about v2, yet....
Aug 27 14:44:51 <jklare> vmeson yeah, but looking at other patches that failed, i guess it will fail :)
Aug 27 14:45:01 <vmeson> jklare: it would be good if you could build systemd for all qemu arches in oe-core. I don't expect that it will be a problem but it's best to check.
Aug 27 14:45:41 <vmeson> jklare: re patchtest: wait for the wavefunction to collapse. ;-)
Aug 27 14:48:36 <vmeson> jklare: on a good machine: for i in `ls ../../oe-core.git/meta/conf/machine | grep qemu | sed -e 's/\.conf//'`; do bitbake systemd && touch sd-okay-$i || touch sd-fail-$i; done
Aug 27 14:49:04 <jklare> vmeson thanks, will give it a spin soon
Aug 27 14:53:01 <jklare> vmeson sadly with a changed commit message it opened a new patch, can i somehow close the old one?
Aug 27 14:53:52 <vmeson> jklare: you don't need to worry about the stale patches in patchworks/test.
Aug 27 15:04:23 <jklare> vmeson it passed the patchtest, YAY, thanks a lot :)
Aug 27 15:06:48 <vmeson> jklare: you're welcome, keep the updates/bug fixes coming!
Aug 27 15:07:00 <jklare> vmeson i will :)
Aug 27 17:07:47 <vmeson> jklare: correction: for i in `ls ../../oe-core.git/meta/conf/machine | grep qemu | sed -e 's/\.conf//'`; do MACHINE=$i bitbake systemd && touch sd-okay-$i || touch sd-fail-$i; done
Aug 27 17:07:57 <vmeson> I forgot to set MACHINE! oops.
**** ENDING LOGGING AT Wed Aug 28 02:59:57 2019