valku has joined #openwrt-devel
<owrt-snap-builds> Build [#822]( of `bcm27xx/bcm2709` completed successfully.
philipp64 has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
goliath has quit [Quit: SIGSEGV]
slh has quit [Quit: Lost terminal]
slh64 has quit [Quit: gone]
bluew_ has joined #openwrt-devel
bluew has quit [Read error: Connection reset by peer]
slh has joined #openwrt-devel
slh64 has joined #openwrt-devel
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
shoragan has quit [Quit: quit]
Danct12 has joined #openwrt-devel
minimal has quit [Quit: Leaving]
<owrt-snap-builds> Build [#819]( of `ramips/mt7621` failed.
<owrt-snap-builds> Build [#370]( of `realtek/rtl839x` failed.
tSYS has quit [Quit: *squeak*]
tSYS has joined #openwrt-devel
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #openwrt-devel
<KGB-0> has been updated. (0% images and 100.0% packages reproducible in our current test framework.)
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 480 seconds]
Danct12 has quit [Quit: WeeChat 3.8]
valku has quit [Quit: valku]
rua has quit [Quit: Leaving.]
dether has joined #openwrt-devel
dether has quit []
dether has joined #openwrt-devel
rua has joined #openwrt-devel
shoragan has joined #openwrt-devel
cbeznea has joined #openwrt-devel
ukleinek_ is now known as ukleinek
danitool has joined #openwrt-devel
robimarko has joined #openwrt-devel
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
<robimarko> Hm, so the Github OpenWrt mirror is somehow out of sync with the
goliath has joined #openwrt-devel
<dwfreed> robimarko: because can't push because github rotated their SSH host RSA key, causing errors
<dwfreed> it has been mentioned in -adm already
<Habbie> just as a note, not even as a suggestion, you could also have github pull (but i think this involves writing some actions yaml)
<Habbie> you could even have both, they wouldn't conflict
<robimarko> dwfreed: Thanks, I am not following -adm
<dwfreed> I noticed when I went to try to tab complete your nick there before responding here :)
maciekb5 has joined #openwrt-devel
maciekb has quit [Ping timeout: 480 seconds]
maciekb5 is now known as maciekb
maciekb has quit [Quit: Ping timeout (120 seconds)]
maciekb has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
cbeznea has joined #openwrt-devel
Ansuel_ has joined #openwrt-devel
Ansuel has quit [Ping timeout: 480 seconds]
Ansuel_ is now known as Ansuel
<Ansuel> robimarko it will be synced as soon as the key problem is fixed and a new commit is pushed
<robimarko> Ansuel: It has already been fixed
<Znevna> all these mtk changes make me wanna upgrade
bluew_ has quit [Ping timeout: 480 seconds]
<nbd> robimarko: nope, hasn't been fixed
<nbd> i just pushed something to openwrt and got the host key warnings again
<robimarko> Thats weird, cause it was in sync after the bmips commit
<stintel> looks like there were a bunch of offending keys still
<stintel> I manually removed them, due to HashKnownHosts this is slightly non-trivial
<stintel> there might be more offending keys for different IP addresses they're using
<stintel> yell if it happens again
<stintel> but yeah github should do DNSSEC and SSHFP
<stintel> I guess sales are more importanter
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
<f00b4r0> github doesn't do DNSSEC? o_O
<Habbie> correct
<Habbie> (and no ipv6 either)
<f00b4r0> impressive.
xback has joined #openwrt-devel
valku has joined #openwrt-devel
Lynx- has joined #openwrt-devel
<Lynx-> Which vi(m) package is best for color syntax highlighting?
xback has quit [Ping timeout: 480 seconds]
ktifhfl has joined #openwrt-devel
minimal has joined #openwrt-devel
<nick[m]12> github sync seems dead? Felix pushed more than an hour a mac80211 patch that is still not available on github
ktifhfl has quit [Quit: The Lounge -]
<nbd> nick[m]12: stintel added a fix on the git server side. after the next commit it should sync again
<nick[m]12> nbd: thanks!
ktifhfl has joined #openwrt-devel
<stintel> if not, yell
<karlp> I'm just getting "lto1: internal compiler error: original not compressed with zstd" on glib after dong a dirclean and removing my dl/*glib*
<karlp> I wish I could have simple problems like updating github host keys :|
torv has quit [Remote host closed the connection]
<Ansuel> karlp wipe ccache
torv has joined #openwrt-devel
<Ansuel> ccache bug that doesn't detect config change and doesn't wipe itself
<karlp> might I suggest taht "make dirclean" should remove .ccache?!
<stintel> ${HOME}/.ccache ?
<karlp> no, this is in the openwrt build dir, I don't even ahve a ssystem ccache right now
<Ansuel> .cache in openwrt
<stintel> in that case, makes sense
<nick[m]12> nbd: I saw you send additional to the station fix, some mesh fixes to linux-wireless. You did not put them to OpenWrt? I looks like this is maybe fixing some issue for me in my mesh setup
<karlp> I certainly wouldn't expect it to remove my system home ccache dir, no.
<Ansuel> karlp eh these are workaround tho... imho the current way is fragile but yes wiping .ccache on clean call is not a bad idea
<stintel> we don't really CI how the average dev / user who builds their own images build
<karlp> especially dirclean, dirclean is meant to be the "yes, I'm prepared to rebuild even toolcahins because things are screwed up and I just want to rebuild clean"
<stintel> i.e. with leftover {build,staging}_dir and tmp/
<stintel> there is breakage all the time in this regard, rather frustrating
<nick[m]12> nbd: whups. they are not new and already included into openwrt.
maciekb has quit [Ping timeout: 480 seconds]
maciekb has joined #openwrt-devel
minimal has quit [Quit: Leaving]
<oliv3r[m]> Ansuel: now that you are here, any thoughts on that 7z MR?
minimal has joined #openwrt-devel
maciekb has quit [Quit: bye]
maciekb has joined #openwrt-devel
<oliv3r[m]> nbd
<oliv3r[m]> i've seen same thing on my laptop, but my desktop is fine; something with github's ssh keys being ... something idk
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
ptudor has joined #openwrt-devel
Lynx-- has joined #openwrt-devel
Lynx- is now known as Guest8760
Lynx-- is now known as Lynx-
Guest8760 has quit [Quit: Going offline, see ya! (]
Lynx-- has joined #openwrt-devel
Lynx- is now known as Guest8761
Lynx-- is now known as Lynx-
Guest8761 has quit [Quit: Going offline, see ya! (]
cbeznea has quit [Quit: Leaving.]
<stintel> nbd: strange
<stintel> but like I said the HashKnownHosts option that is enabled by default in Debian makes things difficult
<stintel> and I don't want to wipe the known_hosts file entirely
<stintel> might introduce other problems
<stintel> ah wait
shibboleth has joined #openwrt-devel
<stintel> the key isn't hashed, just the hostname/IP
<stintel> can someone confirm this is the exposed key?
<stintel> AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
<Habbie> checking
<stintel> nvm found it
<Habbie> good
<stintel> pffft can't even sed the thing out
<stintel> 8h of sleep in 3 nights is not enough
<shibboleth> stintel, what, getting divorced? :P
<stintel> nbd: I hope I did it properly now
<stintel> shibboleth: you need to be married before you can get a divorce :P
<shibboleth> true. and fortunately :P
* enyc meeps
<enyc> If I'm seeing things rightly, lots of changes being submitted to master which may go into a new 23.xx release cycle, or so, at this stage, and no real need for 22.03.x new point release now, or so?
schwicht has joined #openwrt-devel
<stintel> since we didn't branch 23.xx yet, everything that's in master now will most likely end up in 23.xx unless something gets reverted
<enyc> stintel: sure thintg, but I'm just wonedring whats going on dev-wise, maybe this isn't unusual but it seems anomalous to me no new point release in some time, seems odd, could just be "watched kettle" syndrome ;o
<stintel> we usually do a new point release shortly after some bad bugs are found
<stintel> I guess that didn't happen recently
<stintel> release to release is pointless
robimarko has quit [Quit: Leaving]
Borromini has joined #openwrt-devel
schwicht_ has joined #openwrt-devel
Daanct12 has joined #openwrt-devel
<owrt-snap-builds> Build [#820]( of `ramips/mt7621` completed successfully.
Guest8635 has quit [Ping timeout: 480 seconds]
Lynx- has quit [Ping timeout: 480 seconds]
<owrt-snap-builds> Build [#371]( of `realtek/rtl839x` completed successfully.
schwicht has quit [Quit: Textual IRC Client:]
Lynx- has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
shibboleth has quit [Quit: shibboleth]
digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
schwicht_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Lynx- has quit [Quit: Going offline, see ya! (]
Ansuel has quit [Quit: ZNC 1.8.2 -]
Ansuel has joined #openwrt-devel
<olmari> hmm... openwrt buildroot, using "env" script, on save it doesn't seem to save file permission levels correctly
<olmari> always "create mode 100644" when saving
<olmari> and then no 600 anymore for key-files etc ;)
<olmari> anything I could do about that?
<dwfreed> git does not track permissions other than execute
<dwfreed> and execute is a single bit, not separate bits for user/group/other
<dwfreed> that single bit will then be applied to all 3 types on checkout
<dwfreed> if you have a file that should not be world readable, your package install script should be setting appropriate permissions
ptudor has quit [Ping timeout: 480 seconds]
<olmari> dwfreed: well... I don't have package installation script, but freaking ssh host keys :D
<olmari> (for openssh)
schwicht has joined #openwrt-devel
schwicht has quit []
<olmari> ...but took me apparently this long to know git doesn't care about permissions more than x
<Habbie> Ansuel, wow
ptudor has joined #openwrt-devel
<olmari> Well... paid company is... paid company :D
<olmari> I mean.. that fact doesn't itself mean much, but incentives are always something else ;)
schwicht has joined #openwrt-devel
<pekster> olmari: If you're using custom files (via the build system or image builder: there's support for both [1]) it's up to you to set permissions correctly before invoking `make`. An alternative is to use uci-defaults and script the key (or other material) to place.
digitalcircuit has joined #openwrt-devel
<pekster> Do beware if including private keys like that you should protect the resulting firmware image as you would key material since anyone with access to it could trivially extract your host keys.
<olmari> pekster: well... quite the funsies for git deficiensy... (yeah not openwrt failure on that particularity )
<olmari> rest of the facts are known :)
<pekster> Deployment isn't really git's responsibility; tools like scripts or Ansible/Puppet/Chef/… are better at that anyway.
<olmari> true... but also I am not deploying anything myself in the strictest meaning... only wanna throw keyfiles :D
<olmari> without env it even works :P
<olmari> so yeah...
aiyion has quit [Remote host closed the connection]
aiyion has joined #openwrt-devel
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<olmari> I suppose the "env" should take care, while I have no direct ideas how, but yeah.. Also I can manage without this, just.. meh :D
<olmari> Okay, then totally another question... tplink WDR4900 still supposed to work wuth latest master?
<olmari> I know the past things happened with it and some kernel size and bootloader issues
<olmari> something similar issue again? :)
<slh> there's only ome way to find out ;)
<olmari> well... kind og
<olmari> of
<olmari> I know I can eventually take the device from wall and use TTL-serial, but first I need to get there :D
<olmari> ac7v2 went just fine ;)
<slh> it's not exactly a popular device (yes, I know, it's still rather fast), so I wouldn't expect too many others to have tried it - you may be the first in weeks/ months
<olmari> wdr4900 seems not to be tehre after update
<olmari> While I know and/or knew this is always option (to brick), at the moment was more beneficial to try update it rather than let it sit doing nothing