**** BEGIN LOGGING AT Tue Oct 15 02:59:57 2019 Oct 15 11:27:16 do I need to bump PKG_RELEASE for an added dependency? (https://github.com/openwrt/packages/issues/10246) Oct 15 11:27:48 I guess in this case not, as the new domoticz version was probably never built Oct 15 11:27:58 so there are no packages Oct 15 11:28:04 mangix: ^ Oct 15 11:28:05 thoughts? Oct 15 11:29:46 interesting, it actually built for x86_64 for example Oct 15 12:03:25 is bash so called because that's what I've been doing with my head against a wall? Oct 15 12:50:10 ldir: how may we help you? Oct 15 12:58:43 lol - nah - I've just decreased the rate of hitting so it hurts less :-) Oct 15 13:14:33 uhm, did we deprecate pre-gcc-8 toolchains? Oct 15 13:15:59 Is this https://hub.docker.com/r/openwrtorg/rootfs/ something that can be run in production ? Oct 15 13:17:40 given a url like that, how does one get to the actual source of the container? where's the dockerfile and all that? Oct 15 13:19:05 karlp: pfft, source of the container Oct 15 13:19:21 just use docker run, it will conveniently download and execute all that code for you Oct 15 13:19:52 and it has over 2000 pulls already so it can't be evil Oct 15 13:20:01 :) Oct 15 13:23:12 hmm the armvirt-32-master tag there says architecture amd64? confusing Oct 15 13:23:24 and I agree that the info on docker hub should link to the source Oct 15 13:29:42 jow: yea yeah, I just still think it's odd taht there's _nothing_ that I can see that gets you to where that container definition comes from. Oct 15 13:29:44 it just "is" Oct 15 13:30:05 it truly is magic Oct 15 13:30:08 (this is a general docker hub thing, not justthe owrt packages) Oct 15 13:43:45 so will it work as wrt inside docker container ? Oct 15 13:44:04 apparently Oct 15 13:46:30 https://hub.docker.com/_/alpine -> seems their images are even smaller than ours :o Oct 15 13:46:57 and here different archs are shown under same tag Oct 15 13:47:03 maybe we should follow this example :) Oct 15 13:47:06 aparcar[m]: ^ Oct 15 13:47:26 well I guess an alpine base image just ships busybox Oct 15 13:47:35 no fw3, procd, netifd, ... Oct 15 13:53:43 jow: what about volumes and container persistance ? Oct 15 13:53:54 like installed packages and config Oct 15 14:07:13 stintel: purely fyi, there a build error in latest master when selecting brcm2708 - 64bit and selecting gdb+gdb_server: https://pastebin.com/BPmZsR5w Oct 15 14:08:00 (I first though it was due to my staged patches for musl and gdb, but the same errors occurs on openwrt master without those) Oct 15 14:09:00 xback: no surprise there, gdb, strace, perf, all these tools keep breaking all the time Oct 15 14:09:09 I gave up and removed them from my .config's Oct 15 14:09:53 stintel: thanks for confirming. I'll push my changes then Oct 15 15:03:48 xback: dare I ask what the mac80211 commits are in your tree? Oct 15 15:04:11 in 19.07 ? Oct 15 15:05:03 no in xback/master Oct 15 15:05:27 ldir: those are the bumps from Hauke which he posted a few days ago for testing Oct 15 15:06:10 but now you've got me curious about 19,07 :-) Oct 15 15:06:53 ldir: 19.07 also contains a bump from Hauke, but I also backported the rate control improvement from Felix Oct 15 15:07:31 currently testing those mac80211 bumps in the lab here, and the 19.07 improvements in the field Oct 15 15:09:00 hmm I could test them in the lab here too, Did I say lab? I meant on Mrs ldir - "have you broken the internet... again?" Oct 15 15:09:21 sounds like a hazardous environment, your lab ;) Oct 15 15:10:14 does innocent wide eyed look whilst typing 'git reset --hard HEAD~' ; make -j4 Oct 15 15:10:54 It's just basically a large table containing roughly a dozen devices of different archs, all interconnected :-) Oct 15 15:11:03 that's my "stage 1" testing Oct 15 15:11:08 xback: I meant ldir's lab ;) Oct 15 15:11:46 I believe it's called 'dogfooding' Oct 15 15:11:59 haha :) Oct 15 15:12:13 as in.. when I get it wrong that's what I get given to eat :-) Oct 15 15:12:24 LOL Oct 15 15:16:32 ldir: just imagine it's a bowl of cereal ;-) Oct 15 15:16:42 lol Oct 15 15:17:41 * stintel passes ldir some milk Oct 15 15:17:59 * xback passes ldir a spoon Oct 15 15:18:16 I haven't broken it... yet Oct 15 16:19:11 karlp: https://github.com/openwrt/docker/ -> Dockerfile.rootfs Oct 15 16:21:21 I'm sure, that it's somehow possible to push/upload that dockerfile to docker hub as well, so one could get that dockerfile on the docker hub directly, but it's currently not being done Oct 15 16:21:38 this is how it's being built https://github.com/openwrt/docker/blob/master/.gitlab/ci/rootfs.yml Oct 15 16:22:39 more details https://github.com/openwrt/docker/#rootfs Oct 15 16:25:22 here's the build pipeline doing all the build/push magic https://gitlab.com/openwrtorg/docker/pipelines/88343199 (221 jobs for master in 25 minutes and 13 seconds (queued for 3 seconds)) Oct 15 16:25:58 so feel free to join and fix/add missing bits :) Oct 15 16:43:18 muhaha: I'd be surprised if that is working properly yet Oct 15 16:43:33 I don't think it supports passing a docker volume as /overlay Oct 15 16:43:38 but maybe it just works Oct 15 17:16:22 ynezz: it was a docker question, not the specifics of this instance. how, in general, are people meant to workout what's in a container from the docker hub links and descirption **** BEGIN LOGGING AT Tue Oct 15 18:01:41 2019 Oct 15 18:02:25 muhaha: o/ Oct 15 18:02:45 aparcar[m]: ah didn't know about that issue, good to know it's planned! Oct 15 18:04:08 stintel ? Oct 15 18:12:24 jow: can you please look at my prepare/buildinfo PRs so the json files are eventually created Oct 15 18:33:15 is there any ETA for 19.07 ? ( or just usual : when its done.. :) Oct 15 18:33:22 *release Oct 15 18:38:31 aparcar[m]: no, I don't think, that its required, just maybe the https://hub.docker.com/r/openwrtorg/ overview should contain a link back to the docker git repository (README.md?) so it's more clear how it's being developed/build, report issues etc. Oct 15 18:43:05 karlp: hm, back in the days I remember seeing Dockerfile tab along with the image/project on the docker hub, but now it seems to be just part of the project description Oct 15 18:45:50 muhaha: please follow the mailing list for that, jow made a good list of whats missing Oct 15 19:23:45 ynezz: having an official image would be cool I guess... will look into that Oct 16 00:22:59 stintel: yes Oct 16 00:23:19 if the ipk is changed, PKG_RELEASE must be bumped Oct 16 00:23:23 *changes Oct 16 00:35:20 stintel: what were your brcmfmac issues recently? I'm trying to get an ap6212 module up, and I can use iw list, and "wifi config" but can't bring it up https://zerobin.net/?8e4744207109abfc#t3T5LXuoqjOjDl5eLHfA/unuCbdwPV779C7cycYo+XU= Oct 16 00:35:57 (admittedly, I'm using a 5.3.6 kernel, with all of brcmfmac baked in on top of a an openwrt rootfs, so .... all bets are off?) Oct 16 00:36:08 (I want 5.2+ to get the bluetooth for the ap6212 working) Oct 16 01:55:57 karlp: master already has backports 5.3, which should provide everything needed for brcmfmac. if you want 5.4-rc2, there's https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=shortlog;h=refs/heads/mac80211-5.4 **** ENDING LOGGING AT Wed Oct 16 02:59:57 2019