00:47 <owrt-snap-builds> Build [#841](https://buildbot.openwrt.org/master/images/#builders/35/builds/841) of `mvebu/cortexa72` failed.

00:47 <owrt-snap-builds> Build [#853](https://buildbot.openwrt.org/master/images/#builders/15/builds/853) of `armvirt/64` failed.

06:06 <KGB-1> https://tests.reproducible-builds.org/openwrt/openwrt_kirkwood.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)

08:51 <Mangix> Greetings from Europe.

08:51 <aparcar[m]> https://github.com/openwrt/docker/actions/runs/4706933855/jobs/8348506915

08:51 <aparcar[m]> are there issues with bmips?

08:57 <dwfreed> aparcar[m]: I don't even see a bmips builder

08:57 <dwfreed> or a dir in snapshots, for that matter

09:00 <dwfreed> the only device tagged with bcm6328 on the wiki that also has reasonable RAM & storage is the sercomm ad1018, and that is in bcm63xx/smp

10:02 <hauke> aparcar[m]: bmips is source only

10:04 <owrt-snap-builds> Build [#843](https://buildbot.openwrt.org/master/images/#builders/52/builds/843) of `x86/legacy` completed successfully.

13:02 <enyc> ** Question for others about as this seems to be tricky question not yet answered -- is there a clear way via UCI/configs to do the equivalent of "ip -6 ro add default from [delegated block]::/48 dev pppoe-wan" in actual interface-configuration, without relying on DHCPv6-PD , and not doing a gateway via specific IPv6-address either. ?.

13:14 <gch981213> enyc: I added a similar route for IPv4 by specifying 0.0.0.0 as the gateway using route config in /etc/config/network.

13:14 <gch981213> enyc: I guess you can use :: as IPv6 gateway for your route.

13:55 <enyc> gch981213: good point, trying that ;o

13:57 <enyc> gch981213: NO luck (at least after service network restart , not full reboot)

13:59 <enyc> "config interface 'wan6'" "option device '@wan'" "option proto 'static'" "option ip6prefix '[PREFIX]::/48'" "option delegate '0'" "option option ip6gw '::'" is NOT working to create ipv6-default-route via wan ppp automatically

13:59 <enyc> I guess I can try adding a static IPv6 global address on that interface anyhow...

14:06 <enyc> gch981213: AHA thankyou for hint, I have to set an ipv6 global address (can just be /128 duplicate of a lan side address...) and a gateway of :: and then that WORKS wahey!

14:06 <enyc> not source-specific-route but thats' okay for this configuration and essentially doing the equivalent of the ipv4 static block routing anyhow

14:08 <enyc> At least on OpenWRT 21.02.6 -- a lot I'm going to re-think / re-number / etc with OpenWRT 23.xx , in time =)

14:49 <f00b4r0> hmm why does the main site links to release notes on GH (that by the way do not mention the MV88E6176 switch issue)?

15:36 <enyc> f00b4r0: which page/where?

15:37 <f00b4r0> main page, release notes links

18:12 <Ansuel> guys i'm chekcing bzip2 and i found 3 different project of the same lib... and 3 different maintainers for each fork... wth???

18:13 <Ansuel> 1. https://sourceware.org/git/?p=bzip2.git

18:14 <Ansuel> 2. https://gitlab.com/federicomenaquintero/bzip2

18:14 <Ansuel> 3. https://gitlab.com/bzip2/bzip2

18:28 <dangole_> Ansuel: Debian is using pointing to option (1) https://sourceware.org/bzip2/ , see https://packages.debian.org/bullseye/bzip2

18:31 <dangole_> Ansuel: https://sourceware.org/bzip2/downloads.html names gitlab.com/bzip2/bzip2 as "Experimental bzip2 1.1.x: There is also a experimental future branch which includes a modern build system and an experimental Rust port. "

19:41 <raenye> Hello. Do I need to actively do something to have my pull requests reviewed? I have one for a new device and one for a cosmetic luci fix.

23:35 <KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_x86.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)