<peterm6881>
let me paste a couple of respnses from the main Buildroot channel
<zolk3ri>
alright
<zolk3ri>
I'm using agetty on my desktop PC, FWIW
<peterm6881>
<peterm6881> Any idea why getty is respawning with 2023.02, but fine up to and including 2022.11?
<peterm6881>
<peterm6881> Welcome to Speedsaver
<peterm6881>
<peterm6881> speedsaver login: root
<peterm6881>
<peterm6881> Last login: Tue Dec 20 18:16:53 UTC 2022 on ttyS1
<peterm6881>
<peterm6881> Password:
<peterm6881>
<peterm6881> Last login: Tue Dec 20 18:17:12 on ttyS1
<peterm6881>
<peterm6881> Welcome to Speedsaver
<peterm6881>
<peterm6881> speedsaver login:
<peterm6881>
<peterm6881> Same problem for both Lichee Zero and Orange Pi Zero LTS
<peterm6881>
<peterm6881> And MangoPi-R3c
<peterm6881>
<y_morin> peterm6881: Are you using bash?
<peterm6881>
<y_morin> If so, try to backport 2dff6e93ca2a675cebe5cfb6d864ff5da78a4ef4
<peterm6881>
Xogium commented as follows:
<peterm6881>
<Xogium> Yann meant to backport a commit from master to the 2023.02 buildroot
<peterm6881>
<Xogium> as in, you take this commit and pick it and put it on the 2023.02 buildroot. Thing is you're not using git for buildroot itself. Zoltan might need to give you this commit as a patch to apply
<zolk3ri>
so you logged in, and then it gave you the last login message, and then it seemingly "restarted"?
<zolk3ri>
yeah I could do that
<peterm6881>
correct, it behaves exactly as pasted
<peterm6881>
started with 2023.02, which is still the currecnt LTS version
<peterm6881>
2022.11 is fine, never seen that problem before. I just didnt understand the response
<zolk3ri>
or as I said, alternatively, for now, create /etc/locale.conf with the content "LANG=C"
<Xogium>
that's a way to work around yeah
<zolk3ri>
it should work with LANG being en_US.UTF-8 as well
<zolk3ri>
but don't forget to to run locale-gen
<peterm6881>
so is this modifying an existing conf file or creating one from scratch?
<Xogium>
I think the locale-gen utility isn't included in the generated system, since the locales are added and built during the system compilation
<zolk3ri>
or wait, I suppose you don't need to, in this case
<zolk3ri>
okay I see
<Xogium>
that's why there's the localisation options in the menuconfig
<zolk3ri>
I think you could use "en_US.UTF-8" instead of "C"
<Xogium>
I even forget what mine are set to
<zolk3ri>
I have never checked that out yet, only the defconfig files
<peterm6881>
whe you guys figure out exactly what I should change let me know hehe
<peterm6881>
when *
<zolk3ri>
if you run "locale", it should give you everything you need
<Xogium>
ah, en_US.UTF-8 for whitelist and en_US for generation
<Xogium>
menuconfig is the best way to configure buildroot btw, because it changes every setting you need to use one thing or another instead of you having to possibly add them manually
<Xogium>
it handles depends/selects for you
<zolk3ri>
peterm6881: add those two lines to the config and re-build buildroot, or whatever you want it to be, I've not yet ran menuconfig, so no clue what else you can modify with regarding to this, but it has to be identical to what you set the locale to
<zolk3ri>
yeah I've written one by now, and I can imagine how it looks like based on the files
<Xogium>
but for those two it should be ok
<zolk3ri>
just never needed it personally
<zolk3ri>
not yet
<peterm6881>
Xogium, can we adapt our side of things to make this change?
<Xogium>
what do you mean ?
<peterm6881>
since its affecting every repo
<Xogium>
it's just 2 lines added in the defconfig
<peterm6881>
yes but can we do it in menuconfig or amke a patch?
<peterm6881>
make *
<Xogium>
you either edit the defconfig manually or do it in menuconfig. The patch is to fix the bug itself. You don't need this if you're working around the bug
<zolk3ri>
I dunno what repo uses the BR 2023.x, but you can literally just add those two lines to the config file, and push
<peterm6881>
no point editing a file if we have to do it every time till Buildroot decide to make a patch
<Xogium>
you don't ?
* Xogium
scratches head
<peterm6881>
:)
<Xogium>
the defconfig is a one time edit...
<peterm6881>
is that the better way?
<peterm6881>
or would you go down the menuconfig route
<zolk3ri>
> package/readline: add upstream patch to fix crash with invalid locale specification
<zolk3ri>
you just have to have the valid LANG and L_CTYPE set
<Xogium>
I mean either would work. It should make you work around the bug, then the bug in question will get fixed and you'll just never notice it because you already worked around it
<zolk3ri>
which is done through the config file
<zolk3ri>
you don't need to worry about Buildroot making a patch of any sort
<zolk3ri>
16:41:56 < Xogium> the defconfig is a one time edit... <- yup
<Xogium>
this commit isn't yet in 2023.02, but by the time it will be, you'll already have worked around the problem
<zolk3ri>
yeah, the issue is the patch not being in BR, peterm6881
<Xogium>
that's what Yann when he said, backport
<zolk3ri>
inserting those two lines into the config file solves it
<Xogium>
it's already there, just not for your current version, yet
<peterm6881>
im trying to understand if theres a change we can make to our repos that makes this problem go away permanently, rather than tweaking something on my local machine, if its not a think we need to wait on Buildroot for
<Xogium>
but there's another workaround possible which is to use those lines in the defconfig
<peterm6881>
thing * ofc
<zolk3ri>
peterm6881: yes
<zolk3ri>
I told you
<zolk3ri>
add those two lines to the config file, and push the changes to whichever repo
<zolk3ri>
it will make the problem go away permanently, whether BR has the fix or not
<peterm6881>
I will definitely make a mess of that, would you mind doing the needful
<peterm6881>
with todays date, because im done pushing anything, ever
<zolk3ri>
what's History.md?
<peterm6881>
no idea, git did that to me
<zolk3ri>
hmm
<peterm6881>
because its a fuck imho
<zolk3ri>
I mean, I'd have to change the defconfigs too in those repos I suppose, and along with that I could create a tag that would point to that commit
<peterm6881>
its ok, something bad alsways has to happen after a win, its yin and yang
<peterm6881>
history is the list of stuff that changed since the last release
<peterm6881>
so, i guess
<zolk3ri>
you can do "git add History.md"
<peterm6881>
peter@asus:~/buildroot-speedsaver-mangopi$ git status
<peterm6881>
Changes to be committed:
<peterm6881>
Your branch is up-to-date with 'origin/main'.
<peterm6881>
(use "git restore --staged <file>..." to unstage)
<peterm6881>
On branch main
<peterm6881>
new file: History.md
<zolk3ri>
and then 'git commit -m "Add History.md"' or something, or "git commit" and it will open your text editor for the commit message, then git push
<peterm6881>
"or something" is worrying
<zolk3ri>
no, it's fine, but I think you should do "git commit" instead