gromero has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
n3ph has joined #openwrt-devel
djfe has quit [Remote host closed the connection]
djfe has joined #openwrt-devel
n3ph_ has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
owrt-images-builds has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 480 seconds]
wille-io has quit [Quit: Ping timeout (120 seconds)]
wille-io has joined #openwrt-devel
wille-io has quit [Quit: Ping timeout (120 seconds)]
wille-io has joined #openwrt-devel
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #openwrt-devel
wille-io has quit [Quit: Ping timeout (120 seconds)]
wille-io has joined #openwrt-devel
Tapper has joined #openwrt-devel
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
<enyc>
Just briefly wondering if any Dev's can answer my #openwrt question over what it is that populates LuCI menu items e.g. Services -> rp-PPPoE-server on boot.
<enyc>
I know for sure it does when /etc/config/ppp etc is uncommented, but can't seem to figure out from /etc/init.d/ what it is that does this; restarting web and network and boot scripts does not help.
<enyc>
I'd like it to happen 'now' without actually rebooting for a number of reasons, on one particular in-situ router.
guidosarducci_ has quit []
guidosarducci has joined #openwrt-devel
caskd has quit [Remote host closed the connection]
caskd has joined #openwrt-devel
<robimarko>
aparcar: you want to use the v21 for buildworker images, that one reverts to Debian 11
<ynezz>
aparcar[m]: it seems like the feeds don't have parallel main branch yet
<aparcar[m]>
correct. Since I'm not very active in the feeds I don't want to run in and change stuff
<aparcar[m]>
however there was a decision for packages.git to switch to main, I'm happy to do that
<ynezz>
I'm not talking about switch the default
<ynezz>
there is no main branch at all
<ynezz>
it was agreed, that those branches should co-exist for some time before doing the switch, right?
<aparcar[m]>
parallel branches is more difficult for the feeds since they are mainly hosted on github. github does not support mirroring on it's own afaik. with openwrt.git it's easy since we have that running on our own infra
<aparcar[m]>
I guess we could implement a chain like, pushing to github triggers git.o.o to push to github.com master branch
<aparcar[m]>
regarding co-existing, I thought that was only meant for openwrt.git
<aparcar[m]>
If we switch default branch, for i.e. packages.git, the buildbots would just keep on working
<aparcar[m]>
as they don't specifically checkout master
<ynezz>
indeed, seems like its getting the feeds.conf.default
<ynezz>
probably the upgrade didn't went very well, I'll nuke the database and see if helps
<ynezz>
since I nuked all the states, only phase1/main is currently running, we need to wait for some changes in other branches/feeds to start the builds
minimal has joined #openwrt-devel
mentalow has left #openwrt-devel [WeeChat 4.2.2]
<aparcar[m]>
Ansuel: want to backport some APK stuff to 24.10? Not saying setting it as default 😉
<aparcar[m]>
ynezz: were you able to test my latest apk IB fix? you made a good call just directly installing them via index instead of calling the filename
rua has quit [Quit: Leaving.]
<ynezz>
no, trying to figure out why main/phase2 buildbot is not fetching any changes
<schmars[m]>
btw the kmods feeds in some 21.02-snapshot targets are gone for good, i assume? (no problem, just checking)
rua has joined #openwrt-devel
<aparcar[m]>
ynezz: is it polling on a non existing main branch now?
<ynezz>
during testing in staging I've created main branch in my forked feed repository, wasn't aware, that its not the case in the feeds
<aparcar[m]>
ynezz: dang sorry. I didn't see that coming. Does Git Poller support something like branch=None to use the default branch? So package feeds can do their own thing without us handling changes in the buildbot?
<schmars[m]>
it should fetch HEAD (= default branch) if no branch is specified
<schmars[m]>
according to the docs, and i think i've seen this behaviour in my buildbot