**** BEGIN LOGGING AT Sun Feb 28 02:59:57 2021 Feb 28 04:18:04 When the Kernel reports an error on Port 2.... I've got eth0, eth1, eth2, would that be Eth1 or 2? **** BEGIN LOGGING AT Sun Feb 28 05:02:04 2021 Feb 28 06:18:47 build #806 of archs38/generic is complete: Failure [failed toolchain] Build details are at http://buildbot.openwrt.org/master/images/builders/archs38%2Fgeneric/builds/806 blamelist: John Crispin , Jason A. Donenfeld , David Bauer , Daniel Golle , John Audia Feb 28 06:18:47 , Felix Fietkau , Aleksander Jan Bajkowski Feb 28 07:50:13 mangix: upstream Git as in https://github.com/git/git ? Feb 28 08:31:37 lipnitsk: DSA :/ Feb 28 08:33:16 build #792 of mediatek/mt7623 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/mediatek%2Fmt7623/builds/792 Feb 28 09:23:07 ynezz: do you know about the `main` branch? Feb 28 09:32:37 ynezz: yes Feb 28 09:38:31 ynezz: https://www.phoronix.com/scan.php?page=news_item&px=Git-2.28-Released Feb 28 09:39:41 uhh Feb 28 09:53:22 vdi generation doesn't work in 21-02 branch (and maybe on master). Target: x86-64 Feb 28 09:57:20 jmv09: ask aparcar[m] Feb 28 10:05:47 Grommish: what is wrong with 5.10 ? Feb 28 10:37:42 I can't use repository packages from home-built builds. e.g. Packages for kmod-usb-audio found, but incompatible with the architectures configured Feb 28 10:39:56 jmv09: that's normal for all kernel modules, you should build all the kmods you need in advance yourself and use just them. Feb 28 11:13:36 jmv09: vdi creation requires you to install qemu utils Feb 28 11:59:36 damex: kernel panic, I put the log in the 5.10 PR Feb 28 12:01:53 * Borromini is trying the 5.10 bump on his erlite Feb 28 12:03:07 if anybody catches dangole, it looks like he pushed a 'main' branch to openwrt git? Feb 28 12:16:33 build #885 of arc770/generic is complete: Failure [failed toolchain] Build details are at http://buildbot.openwrt.org/master/images/builders/arc770%2Fgeneric/builds/885 blamelist: Felix Fietkau , David Bauer , Daniel Golle , John Crispin Feb 28 13:17:57 >KGB-0< https://tests.reproducible-builds.org/openwrt/openwrt_ar71xx.html has been updated. (99.1% images and 98.4% packages reproducible in our current test framework.) Feb 28 15:16:54 Just pushed pulseaudio to work with bluez again on github. How to pass the "DSO" test? Feb 28 15:16:56 https://github.com/openwrt/packages/pull/14951 Feb 28 15:17:36 DCO check. Feb 28 15:26:33 jmv09: it means you need to git commit --amend -s to add the Signed-off-by line to the commit message. Feb 28 15:42:18 @PaulFertser: what is the procedure on github? I remember having to put the signature in the "optional" extended description. Feb 28 15:42:25 I mean on the website. Feb 28 15:42:57 jmv09: you're supposed to amend the commit locally and re-push it to the same branch, and the "github pull request" will be automatically updated. Feb 28 15:44:15 jmv09, 2 whitespace changes are not needed Feb 28 15:46:39 From more than a year ago, I remember you could sign your commit directly in github, in the "optional" externded description. No need for command line stuff, except for merging commits. But now that doesn't work anymore. I was just testing with the whitespace changes. Feb 28 15:51:59 Trying to pull a dead horse: As far as I can tell e.g. https://github.com/openwrt/packages/pull/14955 has the correct sign-off in the commit. Feb 28 16:30:15 dengqf6: sorry, what about DSA? Thank you for closing the PR - I will reopen later today. Feb 28 16:32:59 jmv09: the S-o-b line doesn't match Author: , that's what it complains about. Feb 28 17:17:03 PaulFertser (or others). Got through the DCO. But still failing on buildpr. ? https://github.com/openwrt/packages/pull/14957 Feb 28 17:17:04 the commit message also needs to be more than just "bluez" Feb 28 17:20:27 Ah real name issue. Feb 28 17:21:27 dangole: did you receive my email re: selinux-policy v0.7? just asking because someone emailed me asking about it Feb 28 17:21:41 sob not matching author is so bogus though, I mean thte whole point of sob is because author is irrelevant and can't be trusted when different people are mailing patches Feb 28 17:21:56 seems like it finally start to get some traction ... Feb 28 17:25:30 well, technically author is about authorship and signed-off about responsibility Feb 28 17:25:43 that's why there is co-developed-by Feb 28 17:27:07 Getting through now: https://github.com/openwrt/packages/pull/14958 Feb 28 17:28:24 Should I generate one for the 22-01 branch as well? Feb 28 17:28:30 21-02 Feb 28 17:28:51 adrianschmutzler: still no support there for the forced requirement that sob == authorship on packages. Feb 28 17:38:43 Hmm. AGAIN bluidpr. but now it failed to download the SDK? Feb 28 17:39:51 I don't think I can fix this... Feb 28 17:52:59 Ok, that may have been a fluke. Feb 28 17:54:11 grift: did not see that, will push now. was deep down in the medidatek loader rabbit hole all last week... Feb 28 17:54:30 yes i noticed Feb 28 17:55:23 i wouldnt have bothered you just but some one emailed me Feb 28 17:57:10 dangole: Was the push of the main branch to openwrt.git intentional? Feb 28 17:59:35 seems like interest is slowly picking up, mvista.com also showed interest to see and and how the can leverage for their stuff Feb 28 18:01:19 Something goes wrong with the commits of "Rosen Penev". It stops the checks of my pull request on the 21-02 branch: https://github.com/openwrt/packages/pull/14959 Feb 28 18:02:01 His commits have been issues without "package name:" format... Feb 28 18:03:20 lipnitsk: no, that went wrong and now only jow can delete it. i was intending to push to my staging tree, have some remote systems run test builds, then push to master and then go to bed Feb 28 18:04:08 lipnitsk: so 'git push -f staging main' became 'git push -f origin main', maybe because subconsciously i wanted to push to openwrt.git already and go to sleep... Feb 28 18:05:06 ya happens to all sometimes.. Feb 28 18:05:35 routine can be a hazard Feb 28 18:06:38 grift: pushed selinux-policy-0.7 to master. you can maybe do that yourself in future: just bump the version in the package Makefile, fixup the MIRROR_HASH and then send the patch to the list. that would keep me out of the loop. Feb 28 18:07:10 i guess ... Feb 28 18:07:40 someone has to commit it anyway, but ok Feb 28 18:09:19 i am actually trying to get people into the loop rather than out of the loop, youre just an easy victim Feb 28 18:09:35 but yes i will do that next time Feb 28 18:17:05 https://github.com/openwrt/packages/pull/14960 is ready to merge into master. Feb 28 18:18:35 dangole: could it be you accidentally pushed your own main branch? Feb 28 18:19:10 you mean the commit with the pr0nhub tokens? Feb 28 18:19:53 shibboleth: nothing as saucy as that i'm afraid Feb 28 18:20:40 Borromini, i was out watching standup two days ago. knee? meet jerk :) Feb 28 18:37:30 Looking for a past/present x86_64 maintainer. Pinging ldir- or maybe philipp64. Feb 28 18:39:10 Borromini: yes, as i said, i pushed to openwrt.git instead to my staging tree by accident. plan was to first test using my own builders and then push to master (like i did in the end, not noticing i had created the new branch before) Feb 28 18:43:31 dangole: sorry, my connection timed out Feb 28 19:29:24 Borromini: no worries :) Feb 28 20:18:13 dangole: was the sepolicy update related to that issue with labeling at boot on ram fs? Feb 28 20:28:40 guidosarducci: no that is not a policy issue Feb 28 20:30:20 grift: OK, I didn't look at the changes closely. Feb 28 20:30:33 the main reason for 0.7 was because there was a change to ntpdhotplug that required changed to the policy, and there was a change to pppd that needed a change Feb 28 20:31:27 and on top of that some new services/utils were targeted like irqbalance, fdisk, blockd, lsusb and some others Feb 28 20:31:51 and i started some work on supporting a selinux feature that comes with linux 5.10 Feb 28 20:32:34 and various other "fixes" and some optimizations Feb 28 20:33:00 tcpdump now also targeted Feb 28 20:35:45 but the volatile root issue needs a fix elsewhere, hopefully it will be addressed soon though Feb 28 20:36:33 grift: thanks, good to know. I'll try it out when I can. Feb 28 22:27:25 build #17 of octeontx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-21.02/images/builders/octeontx%2Fgeneric/builds/17 Feb 28 22:42:21 build #17 of oxnas/ox820 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-21.02/images/builders/oxnas%2Fox820/builds/17 Feb 28 23:27:54 build #17 of pistachio/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-21.02/images/builders/pistachio%2Fgeneric/builds/17 Feb 28 23:28:23 build #17 of bcm63xx/smp is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-21.02/images/builders/bcm63xx%2Fsmp/builds/17 Mar 01 00:41:53 updated openwrt/upstream, https://sdwalker.github.io/uscan/index.html Mar 01 01:07:51 build #17 of bcm53xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-21.02/images/builders/bcm53xx%2Fgeneric/builds/17 Mar 01 02:03:29 build #787 of mediatek/mt7622 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/mediatek%2Fmt7622/builds/787 **** ENDING LOGGING AT Mon Mar 01 02:59:57 2021