**** BEGIN LOGGING AT Sat Nov 23 02:59:57 2019 Nov 23 08:04:18 Greetings! :) Nov 23 08:24:08 errggh Nov 23 08:33:52 build #60 of ramips/rt3883 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt3883/builds/60 Nov 23 10:22:38 Thanks to whoever updated patchwork - forgot about that bit. Nov 23 10:41:12 i like how ipk-files are basically deb-files Nov 23 10:41:58 they even have the deb 2.0 header Nov 23 10:51:43 the apache (httpd) package could use some work... It's a little outdated (i think there's even a critical CVE in that version) Nov 23 10:52:17 also, many modules are missing. imho it would be great to have them available as config-options at build-time Nov 23 11:01:57 build #56 of ramips/rt288x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-19.07/images/builders/ramips%2Frt288x/builds/56 Nov 23 11:08:32 how to handle the PKG_RELEASE when backporting to 19.07? Just bump it by one, too? Nov 23 11:10:28 i am keeping versions between branches consistent Nov 23 11:11:08 that will only work if you keep order Nov 23 11:11:17 if its the same software with the same customizations it should have the same version - but that is only my opinion Nov 23 11:11:46 if one number is left out, you cannot backport it later Nov 23 11:12:49 yes the numbering will be out of sync then Nov 23 11:15:07 is anyone actively working on the apache package? if not I could pick it up for a short time after my pcre stuff is finished. Nov 23 12:52:41 build #51 of ramips/rt288x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-18.06/images/builders/ramips%2Frt288x/builds/51 Nov 23 13:09:04 gladiac1337:perhaps more interestingly is whether anyone's _using_ the apache packages :) Nov 23 13:43:25 Hmmmm Nov 23 13:43:37 mwan3 misdetects an offline connection as online ... Nov 23 13:44:26 It claims my WAN1 would be up, although there isn't even a device (cable-modem) connected to that interface anymore ... Nov 23 13:44:30 (it just died) Nov 23 14:11:41 build #49 of brcm63xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-18.06/images/builders/brcm63xx%2Fgeneric/builds/49 Nov 23 14:21:25 karlp: do we have statistics for that? Nov 23 15:15:52 Hi people I just flashed a new build to my wrt3200acm and am getting crashes Nov 23 15:15:55 https://pastebin.com/Dba524ai Nov 23 15:16:05 Pleas have a look see. Nov 23 15:17:09 build info is r11580-09c428ec6b Nov 23 15:26:26 Tapper: https://bugs.openwrt.org/index.php?do=details&task_id=2624 **** BEGIN LOGGING AT Sat Nov 23 15:43:14 2019 Nov 23 15:49:21 neoraider thanks mate will take a look now. I have my teams game on to so I am distracted lol Nov 23 15:50:26 neoraider ok looks to be the same. thanks Nov 23 15:51:27 build #50 of pistachio/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/openwrt-18.06/images/builders/pistachio%2Fgeneric/builds/50 Nov 23 16:18:30 Can someone help me on building OpenWrt 19.07-rc1 a bit? Nov 23 16:19:17 I checked out tag 19.07-rc1 and did everything as described, but for some packages - mainly luci - I get upgradable packaged on the router right after building it ... Nov 23 16:20:02 As far as I can dig to the cause the reason is that I do not get the same feeds as the WRT 19.07-rc1 build server ... Nov 23 16:20:41 But HOW would I get the same feed? Nov 23 16:21:56 The updates match the commits I see here: https://github.com/openwrt/packages/tree/openwrt-19.07 Nov 23 16:22:23 But how do I make the OpenWrt build env use that "packages" tree? Nov 23 16:25:02 SpaceRat: The OpenWrt 19.07-rc1 tag references specific commits of all feeds in its feeds.conf.default Nov 23 16:26:48 SpaceRat: when you make a build of that tag, you get the packages that were up-to-date when the tag was made Nov 23 16:29:12 neoraider: I got that so far ... but the build server for OpenWrt 19.07-rc1 appears not to stay on that commit ... so there is something missing if I want *my* build server to build (almost) the same as the OpenWrt build server ... Nov 23 16:30:29 SpaceRat: revert the changes to feeds.conf.default from https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=88bff692a56f29c9af402a633e02eb537d983874 Nov 23 16:31:26 Tnx Nov 23 16:35:19 I also have a simple yes/no question: As far as I understand the documentation https://openwrt.org/docs/techref/flash.layout, the less packages I include with the images, the larger my writable overlayfs becomes .. is that correct? Nov 23 16:37:10 SpaceRat: yes, but not for every package you remove you will gain space for the overlayfs, since it only works in erase block steps (most often 64k) Nov 23 16:37:36 Well, I think it was not a good idea to include samba4 inside the image then :) Nov 23 16:37:54 The update 4.9.13 -> 4.9.15-2 made my overlayfs explode :) Nov 23 16:38:54 updating packages means they take twice as much as the base on in the image can't be removed, just hidden (actually more than twice, since the one in the base image is compressed much better) Nov 23 16:39:38 Uhm, that makes less than twice ... Nov 23 16:40:06 The (better compressed) old version in the base image and the update in the overlayfs Nov 23 16:40:26 s/update/bigger update/ Nov 23 16:40:42 Well, depends on the perspective .... Nov 23 16:41:01 yeah - I was comparing to the size included in the image ;) Nov 23 16:41:44 How can I report a bug? Nov 23 16:41:54 if you plan on updating the package, you should install it later; if you don't you are better off by including it in the image Nov 23 16:42:08 https://bugs.openwrt.org/ Nov 23 16:44:02 As the bug is related to the network interfaces overview in Luci, I guess I should use https://github.com/openwrt/luci/issues instead ... Nov 23 16:44:20 thank you for actually reading the page ;D Nov 23 16:45:33 I work in technical support ... I got enough hassle with RTFM and error 40 at work :) Nov 23 17:01:42 SpaceRat ./scripts/feeds update -a then ./scripts/feeds install -a Nov 23 17:07:01 SpaceRat: just saw your earlier question; packages are a rolling release; building the rc1 tag will give you rc1 packages, but opkg will fetch from the openwrt repos which already have updated packages since then - if you want the latest and greatest you need to build the 19.07 branch Nov 23 17:07:46 Well, what I want is rc1 Nov 23 17:07:59 No bleeding edge ... Nov 23 17:08:33 ... that's why I wondered that I found updates using "opkg update && opkg list-upgradable" Nov 23 17:08:57 bleeding edge would be master - the package feeds still use 19.07 branches, so the upgradable packages are mostly bugfixes Nov 23 17:11:05 Well, the kernel on the feed ... if I use the "rc1" feed it's frozen at the rc1-tag, correct? Nov 23 17:12:04 BTW: I got a Linksys WRT1900ACS ... is there any way to flash to the CURRENT partition? Nov 23 17:12:36 Because the other partition contains a working installation of LEDE 17.x, which I do not want to destroy, until I got 19.07 fully up and running ... Nov 23 17:18:57 SpaceRat: if you want rc1 kernel but updated/fixed packages you can just use the imagebuilder, which ships the kmods/etc, but fetches the (userspace) packages from the package feeds Nov 23 17:20:45 Well, the main reason why I build OpenWrt myself at all is ds-lite ... Nov 23 17:21:20 The original base images do not contain support for it, which is a dead end as soon as you happen to have a line with ds-lite. Nov 23 17:21:25 ah Nov 23 17:21:39 At least it used to be Nov 23 17:21:39 yeah, I guess it's time to move it to the base package set Nov 23 17:23:11 Well, if the feeds can be reached using IPv6, everything should be fine ... Nov 23 17:25:01 What would be the most efficient way if I want to build one to three package(s) (Which isn't/aren't on the original feeds) for multiple/all platforms and offer them on my own feed? Nov 23 21:41:13 sdk or openwrt docker sdk containers Nov 23 22:04:02 ^ SpaceRat Nov 23 22:44:14 ynezz: ping Nov 23 22:44:52 ynezz: got a heads up that merging your libubox fiy series will break luci Nov 23 22:44:57 *fix Nov 23 22:45:13 so it might hint at some improper refactoring Nov 23 22:45:29 ah nvm you already seen it Nov 23 22:47:06 jow: yep, working on it right now Nov 23 22:47:41 thanks Nov 23 22:47:50 were you able to repro it? Nov 23 22:48:14 yes, added more jshn test cases Nov 23 22:50:09 and found another off-by-one Nov 23 22:52:00 aparcar[m]: ping Nov 23 23:28:30 hi Nov 24 00:41:17 jow: pong Nov 24 00:45:24 build #149 of ramips/mt7620 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ramips%2Fmt7620/builds/149 Nov 24 00:48:40 build #147 of ramips/mt7621 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ramips%2Fmt7621/builds/147 Nov 24 01:51:00 build #177 of ramips/rt305x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ramips%2Frt305x/builds/177 **** ENDING LOGGING AT Sun Nov 24 02:59:58 2019