ivanich has quit [Read error: Connection reset by peer]
ivanich has quit [Read error: Connection reset by peer]
ivanich has joined #openwrt-devel
ivanich has joined #openwrt-devel
Tapper has quit [Ping timeout: 245 seconds]
Tapper has quit [Ping timeout: 245 seconds]
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
Tapper has joined #openwrt-devel
Tapper has joined #openwrt-devel
schwicht has quit [Read error: Connection reset by peer]
schwicht has quit [Read error: Connection reset by peer]
<philipp64>
ynezz: I have a Xeon-D KVM setup... with resources enough to run 5 or 6 x86_64 or x86 VM's for testing, if you're interested...
<philipp64>
ynezz: I have a Xeon-D KVM setup... with resources enough to run 5 or 6 x86_64 or x86 VM's for testing, if you're interested...
schwicht has joined #openwrt-devel
schwicht has joined #openwrt-devel
Borromini has joined #openwrt-devel
Borromini has joined #openwrt-devel
<philipp64>
nbd: can you please have a look at PR #4006 on openwrt?
<philipp64>
nbd: can you please have a look at PR #4006 on openwrt?
valku has joined #openwrt-devel
valku has joined #openwrt-devel
<lipnitsk>
philipp64: you probably want to rebase your PR since one of the commits appears to have been merged to master already
<lipnitsk>
philipp64: you probably want to rebase your PR since one of the commits appears to have been merged to master already
Darkmatter66 has quit [Ping timeout: 264 seconds]
Darkmatter66 has quit [Ping timeout: 264 seconds]
shibboleth has joined #openwrt-devel
shibboleth has joined #openwrt-devel
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
danitool has joined #openwrt-devel
danitool has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
shibboleth has quit [Quit: shibboleth]
shibboleth has quit [Quit: shibboleth]
dedeckeh has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
Borromini has quit [Quit: Lost terminal]
<mangix>
ugh. lots of buildbot failures
<mangix>
ugh. lots of buildbot failures
<mangix>
guess i shouldn't have wished for an upgrade to debian 10
<mangix>
guess i shouldn't have wished for an upgrade to debian 10
<mangix>
then again, debian is broken in too many ways
<mangix>
then again, debian is broken in too many ways
Tapper has quit [Ping timeout: 240 seconds]
Tapper has quit [Ping timeout: 240 seconds]
Tapper has joined #openwrt-devel
Tapper has joined #openwrt-devel
Radu-Mamy has joined #openwrt-devel
Radu-Mamy has joined #openwrt-devel
<aparcar[m]>
mangix: sush
<aparcar[m]>
mangix: sush
<aparcar[m]>
we're working on it
<aparcar[m]>
we're working on it
Darkmatter66 has quit [Ping timeout: 240 seconds]
Darkmatter66 has quit [Ping timeout: 240 seconds]
<mangix>
aparcar[m]: my irritation is mostly as a debian 10 user. too many bugs.
<mangix>
aparcar[m]: my irritation is mostly as a debian 10 user. too many bugs.
<ynezz>
I assume they accept patches :P
<ynezz>
I assume they accept patches :P
<mangix>
nope
<mangix>
nope
<mangix>
i submitted a bug report with a link to the patch. hasn't been looked at yet.
<mangix>
i submitted a bug report with a link to the patch. hasn't been looked at yet.
<mangix>
no idea what timeframe to expect
<mangix>
no idea what timeframe to expect
<mangix>
one other hilarious thing is pip3 is totally broken. pip3 list -o crashes. I worked around it by doing pip3 install --user --upgrade pip
<mangix>
one other hilarious thing is pip3 is totally broken. pip3 list -o crashes. I worked around it by doing pip3 install --user --upgrade pip
<mangix>
which works properly
<mangix>
which works properly
<aparcar[m]>
mangix: you could get openwrt to build on alpine
<aparcar[m]>
mangix: you could get openwrt to build on alpine
<ynezz>
it seems like nowadays you can use pip from distro, it's always pip install --upgrade pip
<ynezz>
it seems like nowadays you can use pip from distro, it's always pip install --upgrade pip
<ynezz>
s/can/can't/
<ynezz>
s/can/can't/
<mangix>
aparcar[m]: why?
<mangix>
aparcar[m]: why?
<mangix>
ynezz: interesting discussion there. also applicable to rust.
<mangix>
ynezz: interesting discussion there. also applicable to rust.
<mangix>
eg. do you use rg from the distro or from cargo
<mangix>
eg. do you use rg from the distro or from cargo
<ynezz>
sorry, but what is rg?
<ynezz>
sorry, but what is rg?
<aparcar[m]>
ynezz: ripgrep, you want it
<aparcar[m]>
ynezz: ripgrep, you want it
<mangix>
rust replacement for GNU grep
<mangix>
rust replacement for GNU grep
<aparcar[m]>
it finds any string in openwrt.git within like.. no time
<aparcar[m]>
it finds any string in openwrt.git within like.. no time
<aparcar[m]>
#fanboy
<aparcar[m]>
#fanboy
<ynezz>
I prefer git grep
<ynezz>
I prefer git grep
<mangix>
it's just an example. main question is whether to prefer distro or cargo/pip packages
<mangix>
it's just an example. main question is whether to prefer distro or cargo/pip packages
<ynezz>
venv
<ynezz>
venv
<aparcar[m]>
ynezz: it works outside of git too
<aparcar[m]>
ynezz: it works outside of git too
<ynezz>
less surprises
<ynezz>
less surprises
<ynezz>
no, thanks
<ynezz>
no, thanks
<mangix>
oh rg is quite nice. when I want to grep files in a directory, I usually do git init .; git add .; git commit -m m and then git grep w/e
<mangix>
oh rg is quite nice. when I want to grep files in a directory, I usually do git init .; git add .; git commit -m m and then git grep w/e
<mangix>
but rg just works
<mangix>
but rg just works
<ynezz>
I don't care if the search takes 30ms or 300ms, the difference is blink of eye
<ynezz>
I don't care if the search takes 30ms or 300ms, the difference is blink of eye
<mangix>
huh. what is usr/lib/libc-client.so ?
<mangix>
huh. what is usr/lib/libc-client.so ?
goliath has quit [Quit: SIGSEGV]
goliath has quit [Quit: SIGSEGV]
<ynezz>
aparcar[m]: BTW is it possible to have some kind of URL include in GitHub actions, like it's possible on GitLab? Or any other method which would allow reusing of some kind of generic codebase between similar projects?
<ynezz>
aparcar[m]: BTW is it possible to have some kind of URL include in GitHub actions, like it's possible on GitLab? Or any other method which would allow reusing of some kind of generic codebase between similar projects?
<ynezz>
aparcar[m]: or somthing similar to that dynamic child pipeline, so you could generate the next pipeline on the fly? so far it seems to me, that the only solution is to code custom GH action "plugin" (or whats the proper term for that)
<ynezz>
aparcar[m]: or somthing similar to that dynamic child pipeline, so you could generate the next pipeline on the fly? so far it seems to me, that the only solution is to code custom GH action "plugin" (or whats the proper term for that)