**** BEGIN LOGGING AT Wed Oct 02 02:59:57 2019 Oct 02 05:41:28 jow: hey, would you find a moment to look at my luci patches? Oct 02 05:41:43 jow: or do you mind if I just push them and see if anyone complains? Oct 02 05:54:24 what exactly means TARGET_uml? Oct 02 06:44:56 aparcar[m]: it's a symbol for compiling OpenWrt for target defined in target/linux/uml/ Oct 02 06:48:06 rmilecki: can you pls check PR#2447 ? Oct 02 06:48:15 ynezz: can I get a link pls? Oct 02 06:48:22 laziness... Oct 02 06:49:03 https://github.com/openwrt/openwrt/pull/2447 :) Oct 02 06:52:34 rmilecki: oh thanks! Oct 02 06:52:35 ynezz: reviewed, thanks for a link Oct 02 06:52:56 aparcar[m]: that was easy ;) Oct 02 06:52:56 good, thanks Oct 02 06:53:20 could you please merge this https://patchwork.ozlabs.org/patch/1169120/ so rebuild.aparcar.org eventually goes to (nearly) 100%? Oct 02 06:53:33 rmilecki: yea fair, I could have spent a few more minutes thinking Oct 02 06:54:06 no worries Oct 02 06:54:57 aparcar[m]: i'm a bit scared of include/kernel-defaults.mk jow: lynxis: can you look at that aparcar[m]'s patch? Oct 02 06:55:26 rmilecki: what could go wrong ;) Oct 02 06:55:31 :D Oct 02 06:55:35 anyway thanks for pinging them Oct 02 06:57:26 can somebody explain me this comment? https://patchwork.ozlabs.org/patch/1168928/#2268979 I don't understand how to att ffile-prefix-map to that filter out Oct 02 07:01:48 rmilecki: you got an easy answer for that as well? Oct 02 07:02:08 aparcar[m]: no, you're messing with too low level building stuff as for me ;) Oct 02 07:03:03 ynezz: What do you think of applying to a hosten gitlab gold for the evaluation? It is later changeable to "ultimate" meaning self hosted. It includes all premium features and should improve the evaluation process. Only problem I see is the is the git send mail support anyway Oct 02 07:06:19 aparcar[m]: I don't like this golden cages, so I think, that we should stick with the CE (FOSS) version Oct 02 07:06:49 ynezz: even if it's self hostd? Oct 02 07:07:42 aparcar[m]: but you get that gold/ultimate or whatever license for some period of time, don't you? Oct 02 07:08:41 ynezz: afaik yearly renewal. but as kde/gnome/ migrate I think/hope they don't play a false game there Oct 02 07:10:58 yeah, let's see how this pans out after the IPO next year :) Oct 02 07:12:30 I mean, we're aiming (at least talked about it at Hamburg this way) for self-hosted and FOSS solution kdcllggutkvfbggjiledbihbkvrhgc Oct 02 07:13:24 and I don't see the difference between proprietary GitHub and proprietary GitLab Oct 02 07:13:28 rmilecki: sorry, I've been busy with writing api docs the last few days Oct 02 07:13:37 rmilecki: will take a look now Oct 02 07:13:43 jow: np & thanks Oct 02 07:17:32 rmilecki: the patches were on the ml, right? Oct 02 07:18:00 yes, set Oct 02 07:18:19 jow: pending patches from me: https://patchwork.ozlabs.org/project/openwrt/list/?series=&submitter=5824&state=&q=&archive=&delegate= Oct 02 07:19:47 aparcar[m]: FYI, In March 2015, GitLab acquired Gitorious, a competing Git hosting service. Gitorious had at the time around 822,000 registered users. Users were encouraged to move to GitLab, and the Gitorious service was discontinued in June 2015. Oct 02 07:20:19 aparcar[m]: it's a company, so business is at the first place :) Oct 02 07:20:53 rmilecki: hm, this one could be problematic: https://patchwork.ozlabs.org/patch/1167339/ Oct 02 07:21:18 ynezz: bueno, let's stick with foss then Oct 02 07:21:31 jow: this is only for *new* validation function that explicitly marks firmware file as broken Oct 02 07:21:45 rmilecki: storage size detection is not reliable so we should allow force if the size appears too large Oct 02 07:21:52 but not if its not forcable according to sysupgrade Oct 02 07:22:11 jow: flash size error won't mark firmware as non forceable Oct 02 07:22:16 jow: one sec Oct 02 07:22:28 jow: check this one: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=e68c1cebd1d87ce60f0646688e437e83081e2322 Oct 02 07:22:36 jow: it adds "notify_firmware_broken" Oct 02 07:22:36 aparcar[m]: well, it might be just my oppinion (probably Daniel's as well as was strongly against proprietary GitLab solution) so let's see how the discussion/voting pans out, maybe we'll stick with GitHub :p Oct 02 07:22:49 jow: it's the only thing that can mark firmware as non-forceable Oct 02 07:23:35 jow: that function is defines in the https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/base-files/files/usr/libexec/validate_firmware_image Oct 02 07:23:50 and that file (validate_firmware_image) shows you how "forceable" works Oct 02 07:24:36 jow: i made sure that all validation steps used before my refactoring *will not* mark firmware file as non-forceable Oct 02 07:24:46 it's a totally new option that has to be used explicitly Oct 02 07:24:46 rmilecki: yeah, had a logic flaw Oct 02 07:24:49 I'll apply it Oct 02 07:25:01 jow: np, i'm happy to explain if sth isn't clear Oct 02 07:25:09 jow: please note that missed acl par Oct 02 07:25:19 *part Oct 02 07:25:32 jow: see my comment (e-mail reply) in the https://patchwork.ozlabs.org/patch/1167338/ Oct 02 07:25:48 ynezz: I'm afraid that's a good point Oct 02 07:25:51 initially I forgot ot send my modules/luci-base/root/usr/share/rpcd/acl.d/luci-base.json change Oct 02 07:31:31 rmilecki: whats the return value of the ubus call? An object? Oct 02 07:37:38 jow: yes Oct 02 07:38:25 jow: check commit message of https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=f522047958f99ab7b506ec550f796c0460af1a85 Oct 02 07:38:34 ubus call will result in the same format Oct 02 07:40:27 jow: https://pastebin.com/qpjEszEq Oct 02 07:44:49 ok, I'm going to force a default `{ "valid": false, "forcable": true }` in case the ubus call failed Oct 02 07:45:04 failed as in network error, permission denied, crash etc. Oct 02 07:45:13 ok Oct 02 07:48:05 rmilecki: pushed Oct 02 07:48:13 hooray =) Oct 02 07:48:16 ty Oct 02 07:48:45 rmilecki: btw, do you have an idea why `/sys/devices/virtual/mtd/mtd*/name` exists on some devices and on some not? Is that a DTS thing? Oct 02 07:49:23 i didn't know about it until now Oct 02 07:49:28 ls: /sys/devices/virtual/mtd/: No such file or directory Oct 02 07:49:35 hehe, ok. Oct 02 07:54:52 anyone nows where -fmacro-prefix-map is added to gcc params? I tried to find it in the code but it always appears in the buildlog when compiling kmods Oct 02 07:56:33 jow: i found it on an ancient ath25 device Oct 02 07:56:48 jow: oh, I understand what "expect" is about now, thanks ;) Oct 02 07:57:15 also an ubnt-erx Oct 02 07:57:57 jow: did you see also that one? https://patchwork.ozlabs.org/patch/1167446/ Oct 02 07:58:03 it's luci-mod-system: check for sysupgrade with backup possibility Oct 02 07:59:22 and mikrotik rb493g Oct 02 08:17:58 ynezz: ideas regarding farco? Oct 02 08:18:14 *fmacro-prefix-map Oct 02 08:19:13 what's the problem? Oct 02 08:20:19 I'm missing the context, build error for example Oct 02 08:21:43 aparcar[m]: rules.mk Oct 02 08:21:54 i finish my bread and explain Oct 02 08:22:04 also see the gcc8 patch on the ml Oct 02 08:23:50 oh wait, you're paul... lol Oct 02 08:25:08 with my fixup your gcc8 patch replaced -fmacro-prefix-map with -ffile-prefix-map, maybe that's why you can't find it anymore? :) Oct 02 08:27:35 dhewg: oh nice I was looking for you in the IRC but did not figure out ur username Oct 02 08:27:49 I applied the patch and compiled it freshly Oct 02 08:28:01 same irc handle issue here hehe Oct 02 08:28:01 however the buildlog still contains fmarco Oct 02 08:28:06 so it's added somewhere else Oct 02 08:29:02 afaict rules.mk was the only spot Oct 02 08:29:09 https://paste.debian.net/1103588/ Oct 02 08:29:18 dhewg: yea that's my current problem Oct 02 08:29:22 maybe you feed it via .config/external toolchain? Oct 02 08:30:14 there's no -ffile-prefix-map either, sure it's using the gcc8 patch? Oct 02 09:07:51 dhewg: http://ix.io/1P76 sorry for the delay Oct 02 09:08:08 so for some packages it uses the right -ffile-prefix-map but for some not Oct 02 09:08:46 rmilecki: yeah Oct 02 09:09:00 jow: ok, take your time Oct 02 09:11:05 dhewg: maybe this? https://github.com/torvalds/linux/commit/a73619a845d5625079cc1b3b820f44c899618388 Oct 02 09:11:12 inb4 my first kernel patch Oct 02 09:11:56 aparcar[m]: https://ybin.me/p/c80897c26e1d655e#bWfKF5iE9FAybL/H/C4fJ5PTADZQ3ynvmn+SBuFCrVI= Oct 02 09:12:07 that's from a full rebuild, so works for me? Oct 02 09:12:32 and yeah, the macro-prefix-map hits are all from the kernel Oct 02 09:15:30 linux master still uses it, dunno if file-prefix-map would be better there Oct 02 09:18:51 so I guess I'd patch that... Oct 02 09:19:27 jow: can you have a quick look at the TIME_EPOCH patch to make the initramfs reproducible? Oct 02 13:42:47 hey! Oct 02 13:43:45 what does support_list special_id stands for? Oct 02 13:45:37 :S just got it ;) Oct 02 13:59:20 i'm new by here, where can i find the guidelines for pull request? Oct 02 14:09:15 ok, just found it, ty Oct 02 14:46:09 anybody tried JUCI? https://github.com/mkschreder/juci Oct 02 14:46:25 or any other "fancy" web interface as a simpler alternative to LuCI Oct 02 14:47:34 simpler as in smaller packaging or for user? I find Luci quite simple for basically any user (that have any grasp of anything) Oct 02 14:53:23 zorun: is juci still being developed? Oct 02 14:59:18 karlp: no idea, but indeed, the last meaningful commits date back from ~2017 Oct 02 14:59:33 olmari: experience in my community network shows that this is not the case :/ Oct 02 14:59:42 that's about when I last heard about it. Oct 02 14:59:43 olmari: like, too much menus, too much tabs, too much options Oct 02 15:00:22 for instance, the SSID and PSK are in two different tabs in luci Oct 02 15:00:38 karlp: ok, thanks Oct 02 15:01:12 I have some students that could work on a simple/intuitive interface as a project, I just want to make sure that it doesn't already exist! Oct 02 15:01:24 aer you confusing simple to use and look with "hide everything that isn't bare basics"? Oct 02 15:02:34 for me luci seems very simple, the only downside is it is a bit slow, but it may be related to hardware Oct 02 15:03:44 olmari: or you are :) Oct 02 15:04:09 olmari: it would target non-specialists, and the goal is to answer a small set of use-cases Oct 02 15:04:17 identifying these use-cases is the first part of the project Oct 02 15:04:54 like "configure the wifi (SSID, PSK)", or "visualising which machines are connected", or "create a port redirection" Oct 02 15:05:51 which is a different than LuCI which has "strict" categories Oct 02 15:06:01 AFAIK general case is that luci exposes all the basic stuff on any sections "front"page, rest menaingful config is then on sub-tabs, or like with wifi it is further divided into "tech" tab taht has channels etc, security which has WPA etc.... Oct 02 15:06:05 a different *approach Oct 02 15:06:21 sure, for certain special case you can to whatever ofcourse =) Oct 02 15:07:40 problem for oversimplified mixup like you are proposing is then that if one needs to do anything else that slightly differ from what you show and clueless is lost again Oct 02 15:08:11 sure, but there's still LuCI for anything outside of these use-cases Oct 02 15:10:54 speaking of fancy interfaces, I really like the look of this new OUI thing Oct 02 15:10:57 https://github.com/zhaojh329/oui Oct 02 15:12:23 some screenshots: https://github.com/zhaojh329/oui/issues/20 Oct 02 15:13:10 but it still follows the same structure and sub-structure (such as SSID and PSK in separate tabs) Oct 02 15:26:03 * zorun is realising just now that LuCI2 is not the one shipped with openwrt Oct 02 16:13:14 I've dumped C2V2(US) flash, then updated partition table, extra-para, support-list, built it, it still returns "invalid bin file" when trying to upload via web gui, any tip? Oct 02 20:25:50 win 25 Oct 02 20:25:52 grrr Oct 03 00:57:50 ynezz: do you have any additional information about gitorious? https://gitorious.org/ Oct 03 00:58:00 ynezz: regarding the takeofer Oct 03 01:01:10 ynezz: looks like gitlab at least somewhat tried to be nice to the users https://www.archiveteam.org/index.php?title=Gitorious **** BEGIN LOGGING AT Thu Oct 03 01:17:07 2019 **** ENDING LOGGING AT Thu Oct 03 01:44:01 2019 **** BEGIN LOGGING AT Thu Oct 03 01:47:37 2019 **** ENDING LOGGING AT Thu Oct 03 02:59:57 2019