**** BEGIN LOGGING AT Tue Jan 19 03:00:19 2021 Jan 19 04:08:05 Anyone want to review PR #14489? Thanks Jan 19 04:09:06 mangix: that's surprising. glibc gets built in so many places (though not all of them appropriate, given its footprint). Jan 19 05:03:46 philipp64: ummmm not in OpenWrt Jan 19 06:06:12 mangix: I meant regarding building glibc on Centos7, unless I've missed something... Jan 19 06:58:08 philipp64: i assume a newer make is available with whatever backports they have Jan 19 08:04:45 aparcar[m]: does the GitHub Actions build include a host perl? Jan 19 08:06:36 mangix: I assume. Why? Jan 19 10:21:51 svanheule[m]: did you need to adjust bmork's mtdsplit patch set on current master? Jan 19 10:22:00 patch #2 is already breaking for me Jan 19 10:22:04 on current master Jan 19 10:24:46 Borromini: I just applied everything, compiled, and that worked on my WNDR3700v2 Jan 19 10:26:00 ok. have to read up on git-pw again :^) Jan 19 10:26:45 yep that works >_> Jan 19 10:26:50 nevermind me :) Jan 19 10:27:15 going to try this on a wndr3700 v1 and dir-860l Jan 19 10:27:29 git-pw? Jan 19 10:29:52 it's a command that allows you to interact with patchwork Jan 19 10:30:17 https://github.com/getpatchwork/git-pw Jan 19 10:30:19 $ git-pw series apply 217644 e.g. would apply the whole series Jan 19 10:31:28 pretty neat tool :) Jan 19 10:31:43 yeah Jan 19 10:33:24 aha, I just did git am on the series patch downloaded from PW Jan 19 10:34:17 no need! pip3 install git-pw :^) Jan 19 10:34:32 aparcar[m]: https://github.com/openwrt/packages/pull/14506 Jan 19 10:34:47 note how circleci fails in a similar way to the buildbots but actions does not Jan 19 10:34:50 svanheule[m]: although python's git-pw is 1.5.1 according to debian and upstream is 2.0. Jan 19 10:34:54 ewww, I'd never use pip Jan 19 10:35:11 native distro packaging format or gtfo Jan 19 10:35:30 stintel: I only feel safe using pip in a virtualenv Jan 19 10:35:35 aparcar[m]: well actually, no host perl was never a problem with actions, indicating that it does include perl Jan 19 10:35:36 svanheule[m]: nevermind, running the proper pip update commands gives 2.0 Jan 19 10:35:52 for the gentoo folks, there's an ebuild for git-pw in my overlay ;) Jan 19 10:35:59 Wow we got more press for the forum hack than when we put out a new build! Jan 19 10:36:04 stintel: debian testing has git-pw 2.0 :P Jan 19 10:36:10 Borromini: second the git-pw from pip Jan 19 10:36:13 I am just checking the twitter. Jan 19 10:36:20 Tapper: one would alsmost think you ordered it ;) Jan 19 10:36:21 works on centos 7 as well Jan 19 10:36:38 lol Jan 19 10:36:54 * Borromini has once set up a virtualenv but hasn't really bothered so far, don't do that much with python Jan 19 10:39:55 mm, with python "programs", virtualenv is generally the way to go, one can install stuff with pip to there to hearts contents and not mess up global stuff Jan 19 10:40:02 which, with pip, is easy Jan 19 10:40:17 same with cargo Jan 19 10:41:52 or with global stuff it is "default thought" that OS/repo provided python stuff is to be used, pip in otherhand gets whatever versions and packages one desires, hence venv is useful there Jan 19 10:42:24 btrfs-progs: scrub status: print percents of scrubbed bytes Jan 19 10:42:27 finally Jan 19 10:44:47 so in good and bad, python makes it easy to "virtualize" python enviroment, and then free to use whatever versions needed for the exact project... Without needing to think what the next one needs Jan 19 10:46:06 so a virtualenv per 'package' is recommended? Jan 19 10:46:56 great. just forgot to do sysupgrade -n :-/ Jan 19 10:46:58 * Borromini preps for breakage Jan 19 10:47:14 what's the point of sysupgrade anyway if you use it with -n ¯\_(ツ)_/¯ Jan 19 10:47:15 Borromini: generally yes, per package or per project, etc... "one unit of program(s) you provide" :D Jan 19 10:47:22 Borromini: DSA? Jan 19 10:48:12 I sysupgraded my dir860l from >2yo image to master without -n but with -f and it worked :P I did prepare /etc/config/network for it though, don't remember what exactly I did Jan 19 10:48:19 mangix: no just an mtdsplit series Jan 19 10:48:41 but I've got so many configs on most of my devices, if I can't reliably sysupgrade without doing -n I'd find another distro Jan 19 10:48:42 most python based packages from any OS repos has venv baked in them at some method (because OFCOURSE there has to be multime methods for that too 😀 ) Jan 19 10:48:55 but it seems i did, since it's reset itself to default IP and settings :) Jan 19 10:49:13 stintel: i learnt to make backups :P Jan 19 10:49:24 s/packages/random python-based program that is available at a repo Jan 19 10:50:34 Borromini: too many devices to be restoring backups all the time. the backups also contain the incompatible config so you'd be messing about anyway Jan 19 10:50:51 stintel: oh. yeah :( Jan 19 10:51:06 Borromini: all my OpenWrt devices have automated nightly sysupgrade --create-backup .. Jan 19 10:51:20 eh? :P Jan 19 10:51:55 i use sysupgrade without -n all the time Jan 19 10:52:13 it doesnt matter if you are on-top of things Jan 19 10:52:50 Borromini: well running master soft-bricks stuff every now and then, I need those backups :P Jan 19 10:54:54 true :P Jan 19 10:55:05 * Borromini looks at his second bricked tl-wr1043nd v2 Jan 19 10:55:38 eh, 4MB flash right? throw it in the bin ;) Jan 19 10:56:04 8MB isn't even enough anymore for my dumpAP images :/ Jan 19 10:57:00 stintel: get that soldering iron Jan 19 10:57:27 Borromini: isn't that thing 2.4ghz n only? Jan 19 10:57:30 stintel: i thought the v2 had 8 MiB Jan 19 10:57:46 mangix: it is, but i kept it around as an ath79 testing device Jan 19 11:01:14 mangix: pfft that thing is too slow anyway Jan 19 11:01:26 I remember borrowing one from a friend for stress-testing some ath9k bugfixes Jan 19 11:01:42 for the 17.x release or so Jan 19 11:06:49 :) Jan 19 11:15:48 svanheule[m]: sorry i don't recall - did the patch set work for you with and without keeping settings? Jan 19 11:22:19 stintel: i tried overclocking it. was only successful in doing a 20 mhz overclock Jan 19 11:44:03 svanheule[m]: nevermind, works both ways here with my mt7621 device at least :-) Jan 19 11:44:09 Borromini: I think so Jan 19 11:44:26 Borromini: ok :-) Jan 19 12:05:11 FYI https://git.openwrt.org/e87c0d934c54d0b07caef1db3af170510acf3cfa and https://www.jsof-tech.com/disclosures/dnspooq/ Jan 19 12:21:50 https://openwrt.org/advisory/2021-01-19-1 Jan 19 12:44:00 ynezz: is the FIXME intentional? Jan 19 12:44:05 otherwise good work! Jan 19 12:44:26 it's still work in progress Jan 19 12:44:40 but the config mitigations should be already usable Jan 19 12:44:48 so that's why I've shared it Jan 19 12:55:21 Hauke: ynezz: thanks for taking care of this Jan 19 12:59:28 seconded. nice Jan 19 13:00:04 Just got a push notification from heise about our Forum hack: https://www.heise.de/news/Jetzt-neues-Passwort-vergeben-OpenWrt-Forum-gehackt-5028697.html Jan 19 13:01:39 let's hope it brings us more users and eventually more contributors / team members ;-) Jan 19 13:02:03 also, 2FA should be enforced for admins everywhere possible Jan 19 13:02:16 e.g. DO - I don't believe everyone has it enabled Jan 19 13:02:37 now it's just the forum, DO would be another level Jan 19 13:03:35 nvm - it seems everybody does there nowadays, perfect Jan 19 13:08:09 AFAIK wiki has no 2FA Jan 19 13:09:04 it's _less_ important than where we publish code or manage infra Jan 19 13:09:30 but we could maybe add fail2ban to ban offending IPs Jan 19 13:09:42 or crowdsecurity, or ... Jan 19 13:11:20 ynezz: btw, I've a suggestion for an improved upgrade command line: Jan 19 13:11:25 opkg update; opkg upgrade $(opkg list-installed dnsmasq* | cut -d' ' -f1) Jan 19 13:11:45 thanks! Jan 19 13:11:46 slightly less special chars, so less likely to mess up due to smart formatting/copy paste / line breaks etc. Jan 19 13:12:13 (ideally "opkg upgrade" would just take wilcards, but unfortunately it doesn't) Jan 19 13:13:17 and the verify command can be replaced with just "opkg list-installed dnsmasq*" Jan 19 13:13:59 fixed, thanks Jan 19 13:14:25 yw Jan 19 13:14:57 Hauke: https://www.root.cz/zpravicky/forum-openwrt-bylo-napadeno-utocnik-ziskal-uzivatelska-data/ Jan 19 13:15:00 :p Jan 19 13:19:40 stintel: what's DO? Jan 19 13:19:51 ynezz: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8055e38794741313f8f4e6059f83c71dc0ab1d1c Jan 19 13:20:03 Borromini: DigitalOcean, our hoster for forum, wiki, mail Jan 19 13:20:17 oh :) Jan 19 13:21:13 I think that most forum admin even with similar number of suers would not detect such a problem, the ones who detect it probably most of them just change the password and thats it, I would be supprised if the rate of forums which inform thgeir users in such a cases is bigger than 5% Jan 19 13:21:45 the dnsmasq updates are pushed now, please test them again and then someone can create 19.07.6 Jan 19 13:32:43 honestly i try to set 2FA on all the accounts that allow it but i wasn't aware discourse already allowed that. Jan 19 13:37:31 Borromini: I recently found out and added all my U2F keys Jan 19 13:37:46 now I'm actually thinking to retire my yubikeys if they can actually be cloned Jan 19 13:37:55 :) Jan 19 13:40:19 and I just got them :P (well 2 out of the 4 I have) Jan 19 13:40:45 :P Jan 19 13:40:53 so you have yubi *and* the solos? Jan 19 13:42:25 yeah, I got the new yubi's (5+NFC and 5C+NFC) at the time our mother company got pwnd Jan 19 13:42:31 a bit of an impulse buy Jan 19 13:42:39 then I remembered the open alternatives Jan 19 13:44:08 :) Jan 19 13:44:56 i'm not sure if the keys allow cloning. what i read last time i researched was you just need to register two keys with e.g. google or whatever site you'd like to use it with Jan 19 13:45:17 so not a real backup, but just another key you keep safe somewhere in case the first gets lost Jan 19 13:47:26 yes. and the problem there is: you cannot register the "backup" key when you're on the go and register on a new website Jan 19 13:48:20 I still have to check if the U2F/FIDO2 implementations of Ledger or Trezor Cryptocoin wallets will generate the whatever key this standard uses from your seed Jan 19 13:48:28 in this case, that problem would be irrelevant Jan 19 13:49:29 as you will be able to have n "identical" keys Jan 19 13:49:50 actually I can test that as I have 2 ledger wallets Jan 19 13:49:55 * stintel find the 2nd one Jan 19 13:52:26 imagine that works via bt Jan 19 13:52:37 I'd immediately order another Ledger Nano X Jan 19 14:08:47 apparently it does Jan 19 14:15:39 :) Jan 19 14:17:46 but no fido2 yet Jan 19 14:17:47 derp Jan 19 14:19:12 Apparently solokey v2will have ed25519 key support too, they answered (for sideways relating) Jan 19 14:20:36 oooh and #478 will implement this possibly on the v1 Jan 19 14:20:38 * stintel reads Jan 19 14:26:55 build #247 of x86/geode is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Fgeode/builds/247 blamelist: Hauke Mehrtens Jan 19 14:26:55 build #242 of kirkwood/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/kirkwood%2Fgeneric/builds/242 blamelist: Hauke Mehrtens Jan 19 14:26:55 build #242 of ramips/rt288x is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt288x/builds/242 blamelist: Hauke Mehrtens Jan 19 14:26:59 build #236 of ath25/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath25%2Fgeneric/builds/236 blamelist: Hauke Mehrtens Jan 19 14:26:59 build #190 of ath79/tiny is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Ftiny/builds/190 blamelist: Hauke Mehrtens Jan 19 14:27:00 build #198 of ipq40xx/generic is complete: Exception [exception dlfindbinpl] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ipq40xx%2Fgeneric/builds/198 blamelist: Hauke Mehrtens Jan 19 14:27:03 build #196 of sunxi/cortexa8 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa8/builds/196 blamelist: Hauke Mehrtens Jan 19 14:27:03 build #196 of lantiq/xway_legacy is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxway_legacy/builds/196 blamelist: Hauke Mehrtens Jan 19 14:27:25 build #210 of x86/legacy is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Flegacy/builds/210 blamelist: Hauke Mehrtens Jan 19 14:27:25 build #213 of mxs/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mxs%2Fgeneric/builds/213 blamelist: Hauke Mehrtens Jan 19 14:27:25 build #211 of lantiq/xrx200 is complete: Exception [exception ccachecc] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxrx200/builds/211 blamelist: Hauke Mehrtens Jan 19 14:27:35 build #212 of brcm2708/bcm2708 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2708/builds/212 blamelist: Hauke Mehrtens Jan 19 14:27:36 build #203 of brcm2708/bcm2709 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2709/builds/203 blamelist: Hauke Mehrtens Jan 19 14:27:36 build #217 of octeon/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/octeon%2Fgeneric/builds/217 blamelist: Hauke Mehrtens Jan 19 14:27:43 build #197 of x86/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Fgeneric/builds/197 blamelist: Hauke Mehrtens Jan 19 14:27:45 build #195 of at91/sama5 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/at91%2Fsama5/builds/195 blamelist: Hauke Mehrtens Jan 19 14:27:46 build #198 of ath79/generic is complete: Exception [exception interrupted interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Fgeneric/builds/198 blamelist: Hauke Mehrtens Jan 19 14:27:46 build #195 of samsung/s5pv210 is complete: Exception [exception] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/samsung%2Fs5pv210/builds/195 blamelist: Hauke Mehrtens Jan 19 14:27:55 build #199 of ramips/mt7620 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt7620/builds/199 blamelist: Hauke Mehrtens Jan 19 14:27:56 build #190 of mpc85xx/p2020 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fp2020/builds/190 blamelist: Hauke Mehrtens Jan 19 14:27:56 build #196 of brcm63xx/smp is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm63xx%2Fsmp/builds/196 blamelist: Hauke Mehrtens Jan 19 14:28:05 build #192 of ramips/mt7621 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt7621/builds/192 blamelist: Hauke Mehrtens Jan 19 14:28:05 build #213 of layerscape/armv7 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/layerscape%2Farmv7/builds/213 blamelist: Hauke Mehrtens Jan 19 14:28:06 build #211 of lantiq/falcon is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Ffalcon/builds/211 blamelist: Hauke Mehrtens Jan 19 14:28:16 build #242 of apm821xx/sata is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/apm821xx%2Fsata/builds/242 blamelist: Hauke Mehrtens Jan 19 14:28:16 build #208 of sunxi/cortexa7 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa7/builds/208 blamelist: Hauke Mehrtens Jan 19 14:28:16 build #236 of brcm63xx/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm63xx%2Fgeneric/builds/236 blamelist: Hauke Mehrtens Jan 19 14:28:34 build #242 of sunxi/cortexa53 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa53/builds/242 blamelist: Hauke Mehrtens Jan 19 14:28:35 build #248 of oxnas/ox820 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/oxnas%2Fox820/builds/248 blamelist: Hauke Mehrtens Jan 19 14:28:35 build #246 of lantiq/ase is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fase/builds/246 blamelist: Hauke Mehrtens Jan 19 14:28:52 build #236 of at91/sam9x is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/at91%2Fsam9x/builds/236 blamelist: Hauke Mehrtens Jan 19 14:28:53 build #236 of ipq806x/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ipq806x%2Fgeneric/builds/236 blamelist: Hauke Mehrtens Jan 19 14:28:53 build #237 of x86/64 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2F64/builds/237 blamelist: Hauke Mehrtens Jan 19 14:39:47 build #249 of mediatek/mt7622 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7622/builds/249 blamelist: Hauke Mehrtens Jan 19 14:39:47 build #255 of mvebu/cortexa72 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa72/builds/255 blamelist: Hauke Mehrtens Jan 19 14:39:48 build #251 of ar71xx/mikrotik is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fmikrotik/builds/251 blamelist: Hauke Mehrtens Jan 19 14:39:56 build #244 of mediatek/mt7623 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7623/builds/244 blamelist: Hauke Mehrtens Jan 19 14:39:56 build #255 of armvirt/32 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/armvirt%2F32/builds/255 blamelist: Hauke Mehrtens Jan 19 14:39:56 build #249 of mvebu/cortexa53 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa53/builds/249 blamelist: Hauke Mehrtens Jan 19 14:39:57 build #242 of cns3xxx/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/cns3xxx%2Fgeneric/builds/242 blamelist: Hauke Mehrtens Jan 19 14:39:57 build #251 of mvebu/cortexa9 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa9/builds/251 blamelist: Hauke Mehrtens Jan 19 14:40:01 build #256 of archs38/generic is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/archs38%2Fgeneric/builds/256 blamelist: Hauke Mehrtens Jan 19 14:40:06 build #263 of octeontx/generic is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/octeontx%2Fgeneric/builds/263 blamelist: Hauke Mehrtens Jan 19 14:40:11 build #240 of tegra/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/tegra%2Fgeneric/builds/240 blamelist: Hauke Mehrtens Jan 19 14:40:11 build #237 of pistachio/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/pistachio%2Fgeneric/builds/237 blamelist: Hauke Mehrtens Jan 19 14:40:11 build #230 of ath79/nand is complete: Exception [exception ccachecc] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Fnand/builds/230 blamelist: Hauke Mehrtens Jan 19 14:40:12 build #265 of malta/be is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/malta%2Fbe/builds/265 blamelist: Hauke Mehrtens Jan 19 14:40:12 build #245 of ar71xx/generic is complete: Exception [exception ccachecc] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fgeneric/builds/245 blamelist: Hauke Mehrtens Jan 19 14:40:18 build #214 of mpc85xx/p1020 is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fp1020/builds/214 blamelist: Hauke Mehrtens Jan 19 14:40:21 build #217 of ar71xx/tiny is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Ftiny/builds/217 blamelist: Hauke Mehrtens Jan 19 14:40:22 build #206 of gemini/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/gemini%2Fgeneric/builds/206 blamelist: Hauke Mehrtens Jan 19 14:40:22 build #221 of imx6/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/imx6%2Fgeneric/builds/221 blamelist: Hauke Mehrtens Jan 19 14:40:22 build #217 of rb532/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/rb532%2Fgeneric/builds/217 blamelist: Hauke Mehrtens Jan 19 14:40:23 build #213 of ramips/rt305x is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt305x/builds/213 blamelist: Hauke Mehrtens Jan 19 14:40:29 build #218 of brcm47xx/legacy is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Flegacy/builds/218 blamelist: Hauke Mehrtens Jan 19 14:40:32 build #218 of lantiq/xway is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxway/builds/218 blamelist: Hauke Mehrtens Jan 19 14:40:32 build #223 of zynq/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/zynq%2Fgeneric/builds/223 blamelist: Hauke Mehrtens Jan 19 14:40:32 build #214 of ar71xx/nand is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fnand/builds/214 blamelist: Hauke Mehrtens Jan 19 14:40:32 build #218 of ramips/mt76x8 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt76x8/builds/218 blamelist: Hauke Mehrtens Jan 19 14:40:32 build #217 of armvirt/64 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/armvirt%2F64/builds/217 blamelist: Hauke Mehrtens Jan 19 14:40:39 build #250 of layerscape/armv8_64b is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/layerscape%2Farmv8_64b/builds/250 blamelist: Hauke Mehrtens Jan 19 14:40:41 build #255 of mpc85xx/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fgeneric/builds/255 blamelist: Hauke Mehrtens Jan 19 14:40:41 build #227 of bcm53xx/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/bcm53xx%2Fgeneric/builds/227 blamelist: Hauke Mehrtens Jan 19 14:40:41 build #223 of brcm2708/bcm2710 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2710/builds/223 blamelist: Hauke Mehrtens Jan 19 14:40:42 build #221 of omap/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/omap%2Fgeneric/builds/221 blamelist: Hauke Mehrtens Jan 19 14:40:45 build #252 of ramips/rt3883 is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt3883/builds/252 blamelist: Hauke Mehrtens Jan 19 14:40:49 build #248 of x86/geode is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Fgeode/builds/248 blamelist: Hauke Mehrtens Jan 19 14:40:50 build #243 of kirkwood/generic is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/kirkwood%2Fgeneric/builds/243 blamelist: Hauke Mehrtens Jan 19 14:40:50 build #243 of ramips/rt288x is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt288x/builds/243 blamelist: Hauke Mehrtens Jan 19 14:42:25 Hi I am getting this when doing ./scripts/feeds update. Jan 19 14:42:29 fatal: loose object 4d2bb84647575641eb55fc82e62b341b7aa056d6 (stored in .git/objects/4d/2bb84647575641eb55fc82e62b341b7a Jan 19 14:42:32 a056d6) is corrupt Jan 19 14:42:32 failed. Jan 19 14:42:39 any one know how to fix? Jan 19 14:44:52 due to the forum hack we have 500 mentions on twitter lol more then I have ever seen be for. Jan 19 14:45:17 we pay advertising with passwords Jan 19 14:45:26 better this than with bitcoin ;) Jan 19 14:45:50 build #241 of brcm47xx/mips74k is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Fmips74k/builds/241 Jan 19 14:45:55 build #239 of arc770/generic is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/arc770%2Fgeneric/builds/239 Jan 19 14:46:00 build #237 of brcm47xx/generic is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Fgeneric/builds/237 Jan 19 14:48:57 build #209 of apm821xx/nand is complete: Failure [failed gitcheckout] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/apm821xx%2Fnand/builds/209 Jan 19 14:58:17 build #257 of armvirt/32 is complete: Exception [exception dlfindbinpl df ccachestat] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/armvirt%2F32/builds/257 Jan 19 14:58:17 build #251 of mediatek/mt7622 is complete: Exception [exception nproc df ccachestat] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7622/builds/251 Jan 19 14:58:52 So does any one know anything about my ./scripts/feeds update thing? Jan 19 15:01:03 build #252 of ar71xx/mikrotik is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fmikrotik/builds/252 Jan 19 15:01:03 build #246 of mediatek/mt7623 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7623/builds/246 Jan 19 15:19:29 Tapper: is there even an official Twitter account or you mean hashtags Jan 19 15:27:42 Tapper: looks like one of your feed repos is corrupt Jan 19 15:27:55 just ./scripts/feeds clean and retry ... Jan 19 15:28:28 adrianschmutzler thanks mate I fix it now. Jan 19 15:29:15 build #240 of x86/64 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2F64/builds/240 Jan 19 15:29:15 build #258 of armvirt/32 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/armvirt%2F32/builds/258 Jan 19 15:29:15 build #253 of ar71xx/mikrotik is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fmikrotik/builds/253 Jan 19 15:29:15 build #247 of mediatek/mt7623 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7623/builds/247 Jan 19 15:29:15 build #257 of mvebu/cortexa72 is complete: Exception [exception interrupted] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa72/builds/257 Jan 19 16:28:23 build #254 of mvebu/cortexa9 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa9/builds/254 Jan 19 16:28:30 build #239 of ath25/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath25%2Fgeneric/builds/239 Jan 19 16:32:32 build #245 of cns3xxx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/cns3xxx%2Fgeneric/builds/245 Jan 19 16:32:55 build #246 of kirkwood/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/kirkwood%2Fgeneric/builds/246 Jan 19 16:34:05 build #245 of sunxi/cortexa53 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa53/builds/245 Jan 19 16:34:35 build #249 of lantiq/ase is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fase/builds/249 Jan 19 16:34:36 build #251 of x86/geode is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Fgeode/builds/251 Jan 19 16:35:46 build #193 of mpc85xx/p2020 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fp2020/builds/193 Jan 19 16:35:53 build #198 of samsung/s5pv210 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/samsung%2Fs5pv210/builds/198 Jan 19 16:36:12 build #246 of ramips/rt288x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt288x/builds/246 Jan 19 16:36:41 build #233 of ath79/nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Fnand/builds/233 Jan 19 16:36:51 build #253 of mediatek/mt7622 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mediatek%2Fmt7622/builds/253 Jan 19 16:37:38 build #251 of oxnas/ox820 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/oxnas%2Fox820/builds/251 Jan 19 16:37:42 build #240 of pistachio/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/pistachio%2Fgeneric/builds/240 Jan 19 16:38:43 build #245 of apm821xx/sata is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/apm821xx%2Fsata/builds/245 Jan 19 16:38:49 build #268 of malta/be is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/malta%2Fbe/builds/268 Jan 19 16:39:05 build #202 of ramips/mt7620 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt7620/builds/202 Jan 19 16:39:39 build #214 of lantiq/falcon is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Ffalcon/builds/214 Jan 19 16:40:17 build #239 of brcm63xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm63xx%2Fgeneric/builds/239 Jan 19 16:40:18 build #252 of mvebu/cortexa53 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mvebu%2Fcortexa53/builds/252 Jan 19 16:41:02 build #198 of at91/sama5 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/at91%2Fsama5/builds/198 Jan 19 16:41:12 build #195 of ramips/mt7621 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt7621/builds/195 Jan 19 16:41:44 build #216 of layerscape/armv7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/layerscape%2Farmv7/builds/216 Jan 19 16:42:24 build #239 of brcm47xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Fgeneric/builds/239 Jan 19 16:42:29 build #199 of brcm63xx/smp is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm63xx%2Fsmp/builds/199 Jan 19 16:42:51 build #259 of archs38/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/archs38%2Fgeneric/builds/259 Jan 19 16:43:44 build #243 of brcm47xx/mips74k is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Fmips74k/builds/243 Jan 19 16:45:18 build #266 of octeontx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/octeontx%2Fgeneric/builds/266 Jan 19 16:45:31 build #243 of tegra/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/tegra%2Fgeneric/builds/243 Jan 19 16:45:37 build #220 of ar71xx/tiny is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Ftiny/builds/220 Jan 19 16:45:40 build #201 of ath79/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Fgeneric/builds/201 Jan 19 16:46:23 build #241 of arc770/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/arc770%2Fgeneric/builds/241 Jan 19 16:49:29 build #216 of ramips/rt305x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt305x/builds/216 Jan 19 16:49:44 build #217 of mpc85xx/p1020 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fp1020/builds/217 Jan 19 16:51:35 build #211 of sunxi/cortexa7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa7/builds/211 Jan 19 16:52:58 build #200 of x86/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Fgeneric/builds/200 Jan 19 16:53:06 build #220 of rb532/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/rb532%2Fgeneric/builds/220 Jan 19 16:53:22 build #248 of ar71xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fgeneric/builds/248 Jan 19 16:54:54 build #224 of imx6/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/imx6%2Fgeneric/builds/224 Jan 19 16:55:54 build #209 of gemini/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/gemini%2Fgeneric/builds/209 Jan 19 17:03:52 build #217 of ar71xx/nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ar71xx%2Fnand/builds/217 Jan 19 17:04:54 build #220 of armvirt/64 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/armvirt%2F64/builds/220 Jan 19 17:05:26 build #221 of ramips/mt76x8 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Fmt76x8/builds/221 Jan 19 17:07:24 build #221 of brcm47xx/legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm47xx%2Flegacy/builds/221 Jan 19 17:09:40 build #230 of bcm53xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/bcm53xx%2Fgeneric/builds/230 Jan 19 17:10:05 adrianschmutzler, ping Jan 19 17:11:06 build #193 of ath79/tiny is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ath79%2Ftiny/builds/193 Jan 19 17:11:57 build #221 of lantiq/xway is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxway/builds/221 Jan 19 17:12:13 build #258 of mpc85xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mpc85xx%2Fgeneric/builds/258 Jan 19 17:13:40 build #239 of at91/sam9x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/at91%2Fsam9x/builds/239 Jan 19 17:14:24 build #199 of lantiq/xway_legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxway_legacy/builds/199 Jan 19 17:16:01 build #215 of brcm2708/bcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2708/builds/215 Jan 19 17:17:16 build #216 of mxs/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/mxs%2Fgeneric/builds/216 Jan 19 17:17:16 build #213 of x86/legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/x86%2Flegacy/builds/213 Jan 19 17:17:16 build #226 of zynq/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/zynq%2Fgeneric/builds/226 Jan 19 17:17:45 build #220 of octeon/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/octeon%2Fgeneric/builds/220 Jan 19 17:17:54 build #201 of ipq40xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ipq40xx%2Fgeneric/builds/201 Jan 19 17:20:32 bleh, updated all my OpenWrt devices running dnsmasq only to figure out I missed a kernel bump Jan 19 17:22:01 build #206 of brcm2708/bcm2709 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2709/builds/206 Jan 19 17:22:10 build #239 of ipq806x/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ipq806x%2Fgeneric/builds/239 Jan 19 17:24:07 build #214 of lantiq/xrx200 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/lantiq%2Fxrx200/builds/214 Jan 19 17:25:41 build #199 of sunxi/cortexa8 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/sunxi%2Fcortexa8/builds/199 Jan 19 17:31:57 FATAL ERROR: Couldn't open "/builder/shared-workdir/build/build_dir/target-aarch64_generic_musl/linux-layerscape_armv8_64b/linux-4.14.215/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb-sdk.dtb.tmp": No such file or directory Jan 19 17:32:01 in http://buildbot.openwrt.org/openwrt-19.07/images/builders/layerscape%2Farmv8_64b/builds/253/steps/images/logs/stdio Jan 19 17:34:32 build #226 of brcm2708/bcm2710 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/brcm2708%2Fbcm2710/builds/226 Jan 19 17:34:40 build #255 of ramips/rt3883 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt3883/builds/255 Jan 19 17:42:31 build #211 of apm821xx/nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/apm821xx%2Fnand/builds/211 Jan 19 17:45:31 ynezz: I assume this is a concurrency problem because these build bots have different number of core or speed Jan 19 17:45:35 I retriggered it Jan 19 19:25:49 adrianschmutzler: I'm about to push the AUTORELEASE patch for base-files, it would raise the relase once from 242 to 1401, do you think that's a problem? Jan 19 19:26:24 increasing is never a problem Jan 19 19:26:35 only decreasing Jan 19 19:26:52 ack Jan 19 19:27:08 if unsure, i.e. if the syntax changes, use the opkg compare tool Jan 19 19:27:37 base-files_1402-r15385+186-c5d033a34d_aarch64_generic.ipk Jan 19 19:27:47 it's still the same Jan 19 19:28:54 only the release digit changes Jan 19 19:29:58 adrianschmutzler currently the release reset happens on either bump or update, should I add any other "codeword"? Jan 19 19:32:03 well, I don't really understand the mechanics, so I don't know ... Jan 19 19:33:11 if using AUTORELEASE as PKG_RELEASE the number of commits since a commit with subject including "update to" or "bump to" is used Jan 19 19:33:57 meaning no more manual modification of PKG_RELEASE and still knowing how many downstream releases we had since the last upstream version change Jan 19 19:35:07 okay, so this is useless for base-files where we have no upstream Jan 19 19:35:17 let me check uboot-envtools Jan 19 19:36:51 how will you deal with stable branches? just live with collisions in the PKG_RELEASE, as it does refer to a specific state anymore anyway? Jan 19 19:37:06 ... does _not_ refer ... Jan 19 19:38:19 For uboot-envtools there is "update to" and "bump to", rarely also with capital first letter Jan 19 19:39:01 Note that just "update" won't work there, as one might just "update flash location of device X" etc. Jan 19 19:39:16 yea it filter ": update to " Jan 19 19:39:37 that should be good enough Jan 19 19:40:17 adrianschmutzler: please read the commit message here https://git.sr.ht/~aparcar/openwrt/commit/a2dd2e5bbfbc236fc3e99ba2f166665f00b14fa6 Jan 19 19:40:30 it works for both base-files and uboot-envstuff Jan 19 19:45:16 I see Jan 19 19:45:27 Though the use of that $(1) argument is really ugly Jan 19 19:45:45 I'd consider splitting that into two functions ... Jan 19 19:46:53 commitcount and commitsinceupdate Jan 19 19:46:56 or like that Jan 19 19:47:47 and I'm not sure whether I like the date as fallback Jan 19 19:48:12 If one implements that to work as commit count or "autorelease", it should fail if no data is available Jan 19 19:48:26 and not switch to a totally different scheme without notice Jan 19 19:50:47 it's pretty much what luci does, using date as fallback Jan 19 19:51:03 so failing here is not an option Jan 19 19:51:19 well, what you do depends on what you want to do with it Jan 19 19:51:41 if you want a global mechanism that is thrown onto any package, you will choose something like that Jan 19 19:52:15 but then you wouldn't distinguish between COMMITCOUNT and AUTORELEASE, but just go fully automatic Jan 19 19:53:05 but if you assume the user will choose and apply a specific scheme to a specific package (like COMMITCOUNT vs. AUTORELEASE), I'd serve a specific scheme Jan 19 19:54:41 which would severely reduce the ifs Jan 19 19:55:34 two commands for AUTORELEASE, one for COMMITCOUNT Jan 19 19:55:42 if I'm not mistaken Jan 19 19:55:48 what is ifs? Jan 19 19:55:56 conditions Jan 19 19:56:15 oh no abbreviation ;} Jan 19 19:57:03 let me just put something together, mom Jan 19 19:57:16 ideally I want it fully automated, but for a smoother transition I don't want to change release numbers for 6000 packages Jan 19 19:57:44 both variants will be fully automatic, the question is whether the user has a choice or not Jan 19 19:58:08 user=the person defining the variable in the package Jan 19 20:00:39 build #254 of layerscape/armv8_64b is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/layerscape%2Farmv8_64b/builds/254 Jan 19 20:02:13 essentially, what we need is only this: Jan 19 20:02:16 https://zerobin.fff.community/?c08205ed883264c7#lXDdSSbPvl2f/gegvgzh8PUF+zm3nmx4o524ysF+Ws4= Jan 19 20:03:07 this crashes if anyone uses a tarball Jan 19 20:03:42 in that case I'd prefer it to be base-files-210119.123123-*.ipk Jan 19 20:04:36 base-files_210119.68914-r15385+186-c5d033a34d_aarch64_generic.ipk Jan 19 20:04:58 Hmm ... Jan 19 20:06:50 Should the tarball builder get his own versioning scheme ...? Jan 19 20:07:20 I think that's not really our concern as none of our infra does that Jan 19 20:07:30 but it should still be possible to build Jan 19 20:07:58 as it uses SOURCE_DATE_EPOCH it's at least reproducible and can therefor be pointed back to a specific release Jan 19 20:08:49 how will that matter in the context of a tarball builder? Jan 19 20:09:14 opkg list-installed on a running device maybe Jan 19 20:11:19 but then I must say I would make it fully automatic and remove the argument Jan 19 20:11:38 people building outside a git repo likely build a static image they use internally and don't maintain a public package repository. Jan 19 20:11:46 I.e. having only one variable Jan 19 20:12:01 Hello! Who haver latest drivers for MediaTek RT5390 for full speed WiFi? Jan 19 20:12:37 sure we could do that as well as the only case where commitcount seems usable is base-files Jan 19 20:12:51 would be interesting how expensive the git log --grep is Jan 19 20:13:05 because with the current more specific scheme, we circumvent that Jan 19 20:13:38 that's true. I'll give it a quick try Jan 19 20:14:55 just checked in /target, gives me about 1.5 s for each of the git commands Jan 19 20:17:42 adrianschmutzler: ugh Jan 19 20:18:03 i got 0.3 seconds Jan 19 20:18:16 well, target is not really the smallest to test Jan 19 20:18:28 that why I chose it ... Jan 19 20:18:37 anyway, did you copy this 1:1 from luci? Jan 19 20:20:24 wait I'm talking about packages, how is target a package? Jan 19 20:20:43 i just threw the two git commands about a huge history Jan 19 20:20:58 so I have some waiting time which can be reasonably measured Jan 19 20:21:42 anyway, maybe we should just keep your version Jan 19 20:22:39 the tarball issue is valid, and though the "1" parameter is ugly, I didn't find a better idea in several minutes so let's just keep it Jan 19 20:23:10 I'm having a weird problem with dnsmasq returning incorrect results for SRV records. I'm building from the same source tree both archer c7 v2 and archer c7 v5. The v5 build works, the v2 build doesn't. dnsmasq related options are the same in the configs... Jan 19 20:24:53 also building for two ipq806x targets from the same source tree that also don't work Jan 19 20:25:06 adrianschmutzler: so let's just give it a try? Jan 19 20:33:21 I have not validated the code in detail Jan 19 20:34:55 but I give up my objections from above Jan 19 20:35:43 And I still don't understand how the semicolons are put there ;-) Jan 19 20:36:29 try & error Jan 19 20:37:38 only `then` and `else` don't require a following semicolon Jan 19 20:37:59 but some fi do have one and others don't Jan 19 20:38:21 oh sorry I got a corrected version in my local msater branch Jan 19 20:38:24 there was one missing Jan 19 20:39:11 updated Jan 19 20:40:17 adrianschmutzler: https://git.sr.ht/~aparcar/openwrt/commit/2ba9a002978a6a9187947ef95ea982d1c771ff8a the semicolons should be more consistent now Jan 19 20:48:21 There is a typo in the comment "non-empty" Jan 19 20:49:19 and if it's run in a shell anyway, I don't think we need to set last_bump="" at all Jan 19 20:49:33 and you can just remove that particular else Jan 19 20:53:23 ok Jan 19 20:56:53 it's probably okay then Jan 19 20:57:36 and if you change anyways, I'd recommend to be precise in the comment and really put the matched strings there, too Jan 19 21:01:41 updated Jan 19 21:09:12 Guys… is it just me having broadcast traffic issues with MT7615 in stations using WPA3 (personal)…? Jan 19 21:09:29 So, now, the remaining question will just be whether we believe in our reviewers or directly put [uU]pdate in the grep ;-) Jan 19 21:09:53 well the policy says lowercase right? Jan 19 21:09:55 and [bB]ump Jan 19 21:10:09 If we use this feature I'll let people at packages.git etc know about it Jan 19 21:10:15 The policy also says that you should have a commit message, and that commit titles should be short etc. Jan 19 21:11:06 Of the four bumps for uboot-envtools I checked, 3 were "update" and 1 was "Update" Jan 19 21:11:36 omfg how many times is uboot-envtools updated... Jan 19 21:12:58 Well, if we have one wrong update, we cannot fix it without reducing the overall version Jan 19 21:13:43 adrianschmutzler: sorry I don't understand what you're saying Jan 19 21:14:04 If somebody pushes "Update to", the PKG_RELEASE won't be reset Jan 19 21:14:11 Either we live with that fact Jan 19 21:14:36 Or we update the pattern then and get something like 2021.01-2345 -> 2021.01-1 Jan 19 21:15:20 well base-files uses commit count so that can't happen Jan 19 21:15:25 $(COMMITCOUNT) Jan 19 21:16:25 That's why I was talking about uboot-envtools ... Jan 19 21:17:02 but I don't care terribly. if you don't want to do another change, I can also patch it in separately later ... Jan 19 21:18:00 well let's don't push anything but perfect commits Jan 19 21:18:01 at least the most recent change was lower-case, so no harm there Jan 19 21:18:07 how would you change it? Jan 19 21:18:40 Just replace "update" with "[Uu]pdate" and "bump" with "[bB]ump" in the git grep arguments Jan 19 21:18:56 assuming grep actually means regex ... Jan 19 21:19:16 let me test that... Jan 19 21:20:14 ouch, this also greps in the commit message? Jan 19 21:20:44 hah I just realized that Jan 19 21:28:39 this will break whenever a bump is referenced Jan 19 21:28:45 e.g. e7d0d2e9dc Jan 19 21:28:55 yea I'm looking into this Jan 19 21:29:15 This references another commit in Fixes: which is a bump commit and thus matches Jan 19 21:34:04 adrianschmutzler: git log --oneline . | grep "[uU]pdate" -m 1 Jan 19 21:34:47 combined with another cut to get have the has only... ugh Jan 19 21:34:54 jow: can you help with some shell magic? Jan 19 21:35:00 sure. for what? Jan 19 21:36:22 jow: https://git.sr.ht/~aparcar/openwrt/commit/d2ae99f1a45c5e79fdb373a77f2f37579f5c35f3 Jan 19 21:37:12 problem is that git log --grep also checks the commit message. Now it requires a chain of git log --oneline | grep "update" | cut -f 1 -f " " Jan 19 21:37:21 I thought maybe you have a better idea or know a git command Jan 19 21:40:33 I'm not sure whether text-parsing is the way out here ... Jan 19 21:41:00 Maybe we should just drop resetting on update and keep just commitcount Jan 19 21:41:37 afair there is no builtin way to only grep the commit subject Jan 19 21:43:34 well the git | grep | cut chain shouldn't be too expensive? Jan 19 21:45:23 but it's even more ugly, and we have to either "print" the full history first or grep twice Jan 19 21:45:43 apart from the fact that I don't know how stable git output is supposed to be Jan 19 21:46:51 I'd say implement the commit count for now and then we can still expand it with the autorelease functionality later when we have a good idea about that Jan 19 21:47:23 and personally, I could even live with not resetting the commit count for a few packages Jan 19 21:47:52 uboot-envtools currently has 297 commits, 2020.04-297 would not be that terrible Jan 19 21:48:08 adrianschmutzler: I'd assume it's very stable, specially as we can manually define the format to be "$commit_hash $subject". By using grep -m 1 it will close the stdin after a first match and thereby stops git from running. It doesn't print the full log Jan 19 21:50:50 git log --pretty=format:'%h %s' | grep -m 1 ": [uU]pdate to " | cut -d " " -f 1 Jan 19 21:54:19 interesting, for a long history the latter is actually faster Jan 19 21:54:33 (obviously because only the title is parsed) Jan 19 21:55:12 Hah! Jan 19 21:55:33 what I do is going into target/ and then trying to match something that isn't there Jan 19 21:55:44 e.g. time git log --pretty=format:'%h %s' | grep -m1 "xxxxxxxxxxxxxxxxxx" Jan 19 21:56:00 that's where I get these long times like 1-1.5 s Jan 19 21:56:23 of course, when I match something reasonable, it's much faster Jan 19 21:56:33 it will never run in target Jan 19 21:56:48 yes, but I need a long history Jan 19 21:56:53 oh fair Jan 19 21:57:07 just use hyperfine to get real values Jan 19 21:57:42 anyway, I think your latest suggestion is simple enough Jan 19 21:58:46 but since we touched so many parts now, I'd be happy if you resubmit the final version and have it on the list for a few days Jan 19 21:59:17 ack Jan 19 21:59:47 and don't forget to add ":[Bb]ump to " Jan 19 21:59:53 🙂 never Jan 19 22:03:28 but still, discussing and testing thoroughly really helps. The message-matching, which is actually obvious if you think about it, was only revealed as a problem after we talked maybe an hour about the subject Jan 19 22:03:28 adrianschmutzler, re c2600/ad7200 dts (ipq806x, really), jacekowski filed a bugreport a while back: https://bugs.openwrt.org/index.php?do=details&task_id=3285&string=mtu&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= Jan 19 22:04:32 shibboleth: So? Jan 19 22:05:45 yeah, so since you... wanted to generally improve these/update them, would you be open to such a suggestion? Jan 19 22:06:05 add tx-fifo-depth 4096? Jan 19 22:06:16 I wanted to _have them improved_ ... Jan 19 22:06:26 ;-) Jan 19 22:06:55 this would allow for setting a higher mtu and possibly work around the jumboframe/random reboot issue? Jan 19 22:07:21 ... like all devices in OpenWrt. It's not like I have a specific liaison with this particular device Jan 19 22:07:41 shibboleth: I don't have the slightest idea Jan 19 22:07:57 no, sure. but if such a patch should be posted, you won't object on spec/purity? Jan 19 22:08:36 this sounds to me like a misunderstanding. how would I object towards a patch that fixes something Jan 19 22:09:04 If it's not proper, I'd maybe give pointer to how to make it right, of course Jan 19 22:09:30 alright then. do we have to go through all the motions or could this be sorted without all the singing and dancing? Jan 19 22:09:40 patch, review Jan 19 22:10:08 well, what else do you have in mind, apart from "patch, review"? Jan 19 22:10:35 apparently jacecoski filed the bugreport, submitted patches, but pri:very low for some reason Jan 19 22:11:04 ah, so now we are coming closer Jan 19 22:11:12 adrianschmutzler: did I ever sneaked around reviews? Jan 19 22:11:23 so you want special priority for a specific subject Jan 19 22:11:29 oh, no Jan 19 22:11:50 but is a new patch in order or could the old one be dusted off? Jan 19 22:12:33 well, where is it? patchwork or github? Jan 19 22:13:09 i'm waiting for an answer from him on that, i'll let you know :). presumably the ML and timed out on patchwork Jan 19 22:15:04 well, in patchwork you have the advantage of being able to just respond to the original mail with a "Ping." or similar Jan 19 22:16:14 beyond that, the typical means to get forward are to ping people that are active on the target or typically working with stuff similar to the problem (networking/MTU/switch etc. here) Jan 19 22:17:05 if you don't know these people from experience with the project, you may check the git history, e.g. for the relevant target etc. Jan 19 22:17:12 who is active, and also what he does- Jan 19 22:17:41 e.g. I have a lot of activity on several targets, but on many of them commits are trivial/cosmetic Jan 19 22:17:46 sure, reason i pinged you was the convo we had about dts/syntax Jan 19 22:17:50 which won't help you with this matter Jan 19 22:18:20 i'll bring it up once i've gotten hold of him Jan 19 22:18:23 I might be able to help you with the syntax, yes, but I probably won't understand the underlying technical problem on this arch Jan 19 22:19:20 ty Jan 19 22:24:11 aparcar: warum busybox? Jan 19 22:24:39 adrianschmutzler: low hanging fruit, but optional Jan 19 22:25:17 I mean eventually this should be used for more packages than base-files and uboot-env Jan 19 22:25:23 nicht? Jan 19 22:26:14 I'm not sure yet. But in this case, I was curious why this specific package out of so many ... Jan 19 22:26:46 And BTW: any particular reason for --max-count instead of -m? Jan 19 22:27:12 easier for other people to understand what's going on Jan 19 22:29:22 Looks good Jan 19 22:29:33 haven't checked the date-stuff, though Jan 19 22:30:18 I would skip busybox for now, but don't really have something substantial to justify that for you Jan 19 22:31:41 I'll let it ripe for a day or two Jan 19 22:31:55 thanks for your time, it'll hopefully save a lot of time longterm Jan 19 22:33:16 yes, particularly the uboot-envtools are quite a pain Jan 19 22:33:33 either you do it manually every time you merge or you just ignore it Jan 19 22:46:53 aparcar[m]: did you see the comment about the need to backport https://git.openwrt.org/4f3806364011aa3aef26fc ? Jan 19 22:49:34 zorun: ugh it was never backported... Jan 19 22:49:37 can do Jan 19 22:51:19 aparcar[m]: should I remove the item about imagebuild not neededing gcc and so on from the 19.07.6 releases notes? Jan 19 22:53:58 oh yes I think that needs to happen then Jan 19 22:54:01 sorry for that Jan 19 22:59:15 Checking 'gcc'... ok. Jan 19 22:59:23 it does look like it doesn't work in 19.07.6 Jan 19 23:04:08 I backported it Jan 19 23:04:18 thanks Jan 19 23:04:40 zorun: na thank you and sorry that I didn't do that earlier. How is your vote going btw? Jan 19 23:05:51 ask the people who are supposed to vote ;) Jan 19 23:12:05 >KGB-1< https://tests.reproducible-builds.org/openwrt/openwrt_mediatek.html has been updated. (100.0% images and 98.3% packages reproducible in our current test framework.) Jan 19 23:33:31 incredible Jan 19 23:33:40 util-linux' mount.pc file is broken **** ENDING LOGGING AT Wed Jan 20 02:59:57 2021