<mixi_>
thank you very much Borromini , thats a helpful hint
<ynezz>
ugh, 17.87/hr avg hourly rate paid
<stintel>
some people would be very happy with that ;)
<ynezz>
yeah, depends on the location
nast has quit [Remote host closed the connection]
Tapper has joined #openwrt-devel
<danitool>
hi, does still 18.06 accept device fixes backports?
<ynezz>
18.06 is EOL
<ynezz>
there is ongoing discussion whether to do next 18.06 release due to the recent dnsmasq security issue
<danitool>
I know it, no new releases
<ynezz>
ah, I misread that
<stintel>
does it make sense to keep accepting fixes for people who build their own images?
<ynezz>
well, you can always try that
<danitool>
but without new releases, it could still merge some fixes
<ynezz>
send a patch and lets see
<ynezz>
as always, fix for one might be regression for other one :)
<danitool>
well, for a particular device there is no risk, futhermore if the fix is made on the specific device dts file
<ynezz>
the simple fixes and tiny changes sometimes cause big problems
<Borromini>
stintel: i'd say it does
<danitool>
sure, a butterfly can destroy the world
<ynezz>
is the bug reported on bugs.openwrt.org?
<ynezz>
is the fix in the tree already, aka it's just backport?
<danitool>
no, it isn't
<danitool>
no, it isn't <-- the first question
<danitool>
yes, it's just a backport <--- 2nd
<danitool>
btw I'll search in the bugtracker to be sure there is no report
<ynezz>
or forum
<ynezz>
it would certainly help in the decision
<danitool>
at the forum there was a report
<ynezz>
so add `References: https:/forum.openwrt.org/foo/url` to the patch
<danitool>
ok, thank you
<ynezz>
above the Signed-off:
Acinonyx has quit [Read error: Connection reset by peer]
<danitool>
BTW I own the device
<danitool>
it's just a wifi problem caused by missing pinctrl
Acinonyx has joined #openwrt-devel
<danitool>
I wanted to have a functional 18.06 at least for testing purposes
<ynezz>
BTW it's prefered to have backports done with `git cherry-pick -x` as it keeps reference to the upstream commit
<mangix>
cannot find -llibubox
<mangix>
what the hell?
<ynezz>
it's cmake
<Borromini>
danitool: what hardware?
<rmilecki>
mixi_: sure they are, but it's a relatively small market
<rmilecki>
mixi_: if you find company that needs something generic developer for OpenWrt, it's usually simpler
<rmilecki>
mixi_: some companies need dev working on specific hardware
<rmilecki>
so it's sometimes hard for company and devs to "find" each other
<mangix>
ynezz: that's completely wrong though.
<rmilecki>
e.g. demand for Broadcom is quite low but I got company that uses it & OpenWrt
<mixi_>
rmilecki, so how to proceed if you want a career in openwrt?
<stintel>
replace the firewalls at your current job with OpenWrt :P
<Borromini>
:P
<rmilecki>
mixi_: if you are a developer, i suggest posting on ML and forum, let know what you can work on (some target? specific hw? upstream Linux? software?)
<Borromini>
stintel is a selfmade man :P
<rmilecki>
mixi_: link your contributions (git commits)
<rmilecki>
mixi_: also search forum / ML for job offers
<rmilecki>
it's a small market, i'd even try replying to some old posts
<ynezz>
AFAIK it blocks some development so I would like to get it in
kontaxis has quit [Remote host closed the connection]
kontaxis has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
<rmilecki>
ynezz: looks good to me!
mixi__ has joined #openwrt-devel
mixi_ has quit [Read error: Connection reset by peer]
<ynezz>
thanks
<rmilecki>
np :)
<svanheule[m]>
ynezz: Borromini was testing these patches again, but bricked one of his devices
<Borromini>
yes i have a DIR-878 A1 (which uses the sge parser bmork modified)
<ynezz>
is bmork aware? :)
<Borromini>
and i'll be trying an rt-ac57u which i need to revive first from an unrelated issue
<Borromini>
ynezz: the DIR-878 is production, sysupgrade bricked it, since the d-link recovery doesn't like linux browsers i can't say for sure if a clean flash works.
<Borromini>
so i'm holding off on that for now
<Borromini>
sysupgrade was without -n for sure, so might not have been the best approach either (but 'production') :P
mixi_ has joined #openwrt-devel
<Borromini>
that being said, i flashed a build with the v4 patchset on a realtek switch (gs1900-8hp) and that doesn't seem to show any issues
<Borromini>
i recall realtek being part of the targets that needed testing?
<ldir>
Hello unix gurus - I'm looking for a neat way of doing the following. I have a command 'foo' that returns two lines of text, the 2nd line contains an access key - in essence "Authentication success\nkey is keytext" neat way of getting 'keytext' into a variable.
<stintel>
| tail -n1 | awk '{print $3}' ?
<ldir>
that's close to what I have already tail -n1 | cut -d' ' -f3
<jow>
command | sed -ne '2s#key is ##p'
<jow>
command | sed -ne '2s#^key is ##p'
<jow>
or real dirty, if keytext never contains whitespace and is never followed by something else:
<jow>
for key in $(command); do :; done # $key contains keytext after the loop
<ldir>
oooh yuck :-)
<karlp>
oh, that's special :)
<karlp>
I like that :)
<Borromini>
$command|awk '/key/ {print $3}' should work as well
* Borromini
thinks
Tapper has quit [Ping timeout: 256 seconds]
* ldir
went with jow's sed solution
valku has joined #openwrt-devel
aparcar[m] has quit [Quit: Bridge terminating on SIGTERM]
pavlix has quit [Quit: Bridge terminating on SIGTERM]
JuniorJPDJ has quit [Quit: Bridge terminating on SIGTERM]
pgwipeout[m] has quit [Quit: Bridge terminating on SIGTERM]
svanheule[m] has quit [Quit: Bridge terminating on SIGTERM]
decke[m] has quit [Quit: Bridge terminating on SIGTERM]
olmari has quit [Quit: Bridge terminating on SIGTERM]
agb[m] has quit [Quit: Bridge terminating on SIGTERM]
fblaese has quit [Quit: Bridge terminating on SIGTERM]
t4h4[m] has quit [Quit: Bridge terminating on SIGTERM]
MatMaul has quit [Quit: Bridge terminating on SIGTERM]
voltagex has quit [Quit: Bridge terminating on SIGTERM]
nick[m]2 has quit [Quit: Bridge terminating on SIGTERM]
akira25[m] has quit [Quit: Bridge terminating on SIGTERM]
Floppe has quit [Remote host closed the connection]
Floppe has joined #openwrt-devel
Borromini has quit [Ping timeout: 246 seconds]
decke[m] has joined #openwrt-devel
kakaka has quit [Remote host closed the connection]
hexa- has quit [Ping timeout: 240 seconds]
adrianschmutzler has joined #openwrt-devel
<lmore377>
blocktrron: thank you!
<blocktrron>
lmore377: ping me once you've updated the PR
<ldir>
I ended up with this as it turned out I needed to get rid of some trailing whitespace - sed -ne '2s#^key is ##;2s# *$##p'
<lmore377>
blocktrron: one quick note about the led situation, on this device the led is red/blue and it's connected to a microcontroller and based on how you switch those 3 pins on and off it'll do different patterns of either red or blue. if you look at some of the past comments there's one that explains it better (i can copy paste it to yours in a bit)
<adrianschmutzler>
lmore377: but still, labels should follow the common scheme
hexa- has joined #openwrt-devel
kakaka has joined #openwrt-devel
<ynezz>
we should really automate that, people won't argue with robots :p
kakaka has quit [Remote host closed the connection]
luke-jr has quit [Remote host closed the connection]
luke-jr has joined #openwrt-devel
<blocktrron>
lmore377: wasn't aware of that, in this case this is fine
<blocktrron>
> if you look at some of the past comments there's one that explains it better - This is what i was referring to with "Reviewing long running GItHub PRs as an outsider is pain"
decke has quit [Quit: Leaving.]
<adrianschmutzler>
still, the labels should at least converted to something like just "ledctrl1", "ledctrl2", etc.
Strykar has quit [Quit: /quit]
Strykar has joined #openwrt-devel
agb[m] has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
nick[m] has joined #openwrt-devel
svanheule[m] has joined #openwrt-devel
fblaese has joined #openwrt-devel
JuniorJPDJ has joined #openwrt-devel
pgwipeout[m] has joined #openwrt-devel
aparcar[m] has joined #openwrt-devel
MatMaul has joined #openwrt-devel
voltagex has joined #openwrt-devel
olmari has joined #openwrt-devel
akira25[m] has joined #openwrt-devel
pavlix has joined #openwrt-devel
Tost has quit [Ping timeout: 260 seconds]
jas4711 has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
Borromini has joined #openwrt-devel
samantaz__ has quit [Quit: Bye]
danitool has joined #openwrt-devel
<danitool>
hi, I can't download the upgrade image into the router from the Openwrt website
Darkmatter66 has joined #openwrt-devel
<danitool>
I get "Failed to redirect to /releases/19.07.6/target....."
<danitool>
is this the expected behavior?
<stintel>
danitool: you'll have to be more specific than "the upgrade image"
<danitool>
the sysupgrade image
<danitool>
well, probably any image
dedeckeh has quit [Quit: Ping timeout (120 seconds)]
<danitool>
I mean downloading the sysupgrade image using openwrt itself
<danitool>
with the browser at my PC the download is ok
<danitool>
mm, probably it is redirecting to the https url, but the "wget" lacks https capacity
Darkmatter66 has quit [Ping timeout: 246 seconds]
feriman has joined #openwrt-devel
gch9812133289452 has joined #openwrt-devel
blb4393 has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
inhaller has joined #openwrt-devel
<inhaller>
hello everyone
<inhaller>
i'm trying to port openwrt to an Aerohive AP230, but i'm having trouble getting the squashfs image in the right format