<JPEW>
RP: I went on a tear today; got poc for the garbage collection and hash existence check in the hashserver working. Won't be able to finish until next week because of the holiday, but it looks good
KhazAkar has quit []
bq is now known as dp
dp is now known as Guest6931
Guest6931 is now known as bq
lexano has quit [Ping timeout: 256 seconds]
Daanct12 has joined #yocto
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
sakman has quit [Ping timeout: 252 seconds]
Minvera has quit [Ping timeout: 264 seconds]
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #yocto
hcg has joined #yocto
kpo has joined #yocto
kpo has quit [Remote host closed the connection]
kpo has joined #yocto
mckoan_ has joined #yocto
mckoan|away has quit [Ping timeout: 245 seconds]
kpo has quit [Quit: Konversation terminated!]
adrian_s has quit [Ping timeout: 252 seconds]
adrian_s has joined #yocto
sakman has joined #yocto
dvergatal has quit [Ping timeout: 264 seconds]
dvergatal has joined #yocto
vladest has quit [Quit: vladest]
jmd has joined #yocto
vladest has joined #yocto
linfax has joined #yocto
ray-san has joined #yocto
ptsneves has quit [Ping timeout: 255 seconds]
<ray-san>
hi there, i try to make a file immutable via "chattr +i ...". is there a direct way to archive this directly in the recipe without writing a systemd unit, which sets the flag on the first boot or something like that?
<LetoThe2nd>
yo dudX
<LetoThe2nd>
ray-san: have you tried adding the chattr in the do_install task?
<ray-san>
LetoThe2nd: not yet because i thought it is just a file somewhere in the filesystem during the build stage, and my guess is, that this attribute doesn't persist the way into my completed image....but i can give it a shot
JerryM has joined #yocto
<LetoThe2nd>
ray-san: please do, because thats exactly what pseudo should take care of.
frieder has joined #yocto
alperak has joined #yocto
<ray-san>
meh, bitbake complains that the command chattr is not found although i have given "e2fsprogs-native" as DEPENDS, which should provide chattr i guess
<LetoThe2nd>
ray-san: isn't it in corutils somewhere? just guessing now.
<ray-san>
on my target system it is either provided by busybox or by e2fsprogs
<LetoThe2nd>
ray-san: nah its e2fsprogrs, you're right.
mvlad has joined #yocto
<LetoThe2nd>
ray-san: no idea right off then other than inspecting the recipe sysroot.
<ray-san>
ok, nevermind...thought it would be nice to have in my image, not a strong requirement :)
mckoan_ is now known as mckoan
<ray-san>
i found out with in the devshell the command is "chattr.e2fsprogs", but then bitbake complains "chattr.e2fsprogs: Operation not permitted while setting flags on /path/to/my/file", so i guess it isn't possible to set this flag during build time :)
vladest has quit [Quit: vladest]
rfuentess has joined #yocto
<LetoThe2nd>
ray-san: ok i see. sorry, out of ideas then.
<ray-san>
thanks for your time anyway :)
<LetoThe2nd>
ray-san: NP, have fun. side note, most people go for read-only rootfs if they want to keep things kind-of immutable.
Kubu_work has joined #yocto
hcg has quit [Ping timeout: 250 seconds]
<ray-san>
yeah, i already thought about that, but RO rootfs comes with a lot of additional hassle, and i'm quite new to this....for example, how do i install updates in the field, at the moment i can just install a rpm, some software i need come with hardcoded paths for files which have to be modified (ugh)....my goal is to have a file with version information about the image and i try to prevent somebody overwriting/changing it by accident....but maybe in the
<ray-san>
future
ecdhe has quit [Read error: Connection reset by peer]
<LetoThe2nd>
ray-san: software updates in the field are an art of their own, and seriously, using package management for that should be absolutly avoided.
<LetoThe2nd>
ray-san: i definitely suggest using an existing solution instead of homebrewing something that copies files back and forth. such exist, like https://mender.io/ - and for the record and full disclosure, i work for them.
<LetoThe2nd>
ray-san: plus, using it with RO is totally not a problem :-)
ecdhe has joined #yocto
grma has joined #yocto
kulos75 has joined #yocto
zpfvo has joined #yocto
<chep>
Saur_Home: yes I saw that but it's not my layer. anyway I found how not to use it so until it works without it, everything is fine
alessioigor has joined #yocto
zpfvo has quit [Ping timeout: 263 seconds]
camus1 has joined #yocto
vladest has joined #yocto
camus has quit [Ping timeout: 276 seconds]
camus1 is now known as camus
florian__ has joined #yocto
Wouter0100670440 has quit [Ping timeout: 276 seconds]
zpfvo has joined #yocto
KhazAkar has joined #yocto
<ray-san>
LetoThe2nd: i had looked into solutions like that (rauc in my case) and it looked like, they are very machine specific (which makes sense to me, because you have to interface with the bootloader), and at the moment i'm builing for "genericx86-64", which didn't had a solution
<LetoThe2nd>
ray-san: heh, actually i'm just working on an example for genericx86-64, because of $reasons. rauc is also an excellent update client on the device, indeed. the key part to understand is the difference between a device-only client and an actually managed solution - which is what you want if you are deploying to a reasonably sized device fleet.
adrian_s has quit [Ping timeout: 256 seconds]
alperak has quit [Quit: Client closed]
alperak has joined #yocto
<ray-san>
LetoThe2nd: i see the benefits of a managed solution, but the vast majority of my devices are deployed in a airgapped network from my customer, where often i'm not able to install some sort of update server, so i guess at the moment my way to go solution would be a device only client, at least for the moment
warthog9 has quit [Remote host closed the connection]
Rich_1234 has quit [Quit: Connection closed]
Guest97 has joined #yocto
Guest97 is now known as Rich_1234
leon-anavi has joined #yocto
warthog9 has joined #yocto
<LetoThe2nd>
ray-san: yeah that is definitely a common challenge. going with a client focused solution for the first round is probably a good approach - rauc, swupdate and mender should be all suitable
<LetoThe2nd>
ray-san: side note: in my experience most networks are nowhere near as airgapped as people pretend they are, but that might be just me :-)
mbulut_ has joined #yocto
<LetoThe2nd>
now stupid me: is there a generic variable that holds /opt and friends to be used for FILES, or does that hierarchy just go in verbatim?
<kanavin>
RP: the test expects changes in gcc-source tasks, but bitbake prints:
<kanavin>
Task gnu-config-native:do_configure couldn't be used from the cache because:
<kanavin>
We need hash fe9ccd7132f7e8aa33587f807b210792da2c8ab7c363472f459629502ec71c9d, most recent matching task was 492e2b0ac161069f340036aad9b35c6a17d33d26a5b0a9cb37105210f0a78c9f
<kanavin>
Hash for task dependency gnu-config-native:do_patch changed from 116e7c2189ff17af9b84ffcbdf2d84fbf1e27ceb9d0458b4093d75ee71c9b0e6 to 6fd64d81a794dc3b634631208cb7f48435cad4ca19718658d3df6222b8e0ee9a
<kanavin>
basehash changed from d30c1e4c8a67155b18b9d4ecbcce251fee20b5b9af0aa5ea0c33a9e342e73179 to 36d0617c68a33050bb71c8be346f7b9cb4a9239145d3722917a1bd4f67593473
<smurray>
RP: I appear to have underestimated the fickleness of the Rust ecosystem, and likely will now need to create a Rust 1.70 mixin for kirkstone :/
lexano has joined #yocto
<RP>
smurray: this was always the worry with rust, you appear to need latest everything. We can't get much more recent with master :(
<smurray>
RP: I suspect this one crate (anstyle) changing its reqs probably has a big effect, it has a lot of dependents
<smurray>
it'd have been nice if they'd not changed the Rust version req in a point version (1.0.2 -> 1.0.3), sigh
<RP>
smurray: people often just don't think :/
<smurray>
RP: sadly. Life does seem like it's going to be "interesting" when it's more than just a couple of things that build with Rust
<RP>
smurray: indeed :/
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
prabhakarlad has quit [Ping timeout: 250 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.1]
prabhakarlad has joined #yocto
<smurray>
RP: I may be okay, I see a potential path to patch in a downgrade of the clap crate, which is the top-level dependency that causes the chain
<LetoThe2nd>
smurray: i had some good laughs at LPC when the rust people were like "our stable baseline lies in the future"
alperak has quit [Quit: Client closed]
mbulut_ has joined #yocto
alperak has joined #yocto
belsirk has joined #yocto
rfuentess has quit [Ping timeout: 260 seconds]
olani- has quit [Remote host closed the connection]
Minvera has joined #yocto
mvlad has quit [Remote host closed the connection]
belsirk has quit [Remote host closed the connection]
yannd has joined #yocto
mvlad has joined #yocto
<zeddii>
emphasis on the "lies" !
<zeddii>
LIES!!
<LetoThe2nd>
zeddii: the next drink is on you then i won't tell anybody that you were sitting and laughing right next to me... erm... oops.
* zeddii
chuckles again
leon-anavi has quit [Ping timeout: 256 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
jmd has quit [Ping timeout: 276 seconds]
alussier-cullen has joined #yocto
<rburton>
"someone pass me a drink and say that again so I can spit it out in surprise"
<smurray>
lol
alussier-cullen has quit [Quit: Client closed]
speeder has quit [Remote host closed the connection]
hcg has quit [Ping timeout: 250 seconds]
Bardon has quit [Read error: Connection reset by peer]
Bardon has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Bardon_ has joined #yocto
Bardon has quit [Read error: Connection reset by peer]
linfax has quit [Ping timeout: 264 seconds]
Bardon_ has quit [Ping timeout: 255 seconds]
leon-anavi has joined #yocto
* LetoThe2nd
hands rburton a 🥃
Bardon has joined #yocto
<rburton>
spent the morning in the same room as the cambridge debian miniconf, need a drink :)
frieder has quit [Remote host closed the connection]
shane84 has joined #yocto
<shane84>
Hi ~ When I setup a build environment via `oe-init-build-env`, step away and say exit my terminal then come back later ... how do I easily return to my build environment? Sorry, kind of a stupid question I need to ask. My understanding is I just type `source oe-init-build-env <name-of-build-folder>` again and that gets everything setup again?
Minvera has quit [Quit: Leaving]
<yocton>
shane84: that's right :)
<shane84>
cool, thank you
<rburton>
shane84: use something like tmux and you can never exit the terminal unless you reboot
<rburton>
my build machine is remote and the tmux session, thus the environment settings, is only restarted when the machine reboots
alussier-cullen has joined #yocto
alussier-cullen has quit [Client Quit]
<shane84>
(y) , thank you will check that out. is it common for people to alias `source oe-init-build-env` in their bashrc? bit of a mouthful to type `source oe-init-build-env ...` each time.
<Rich_1234>
source o<tab> :)
mrpelotazo has quit [Ping timeout: 240 seconds]
ptsneves has quit [Ping timeout: 255 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mrpelotazo has joined #yocto
mckoan is now known as mckoan|away
shane84 has quit [Quit: Client closed]
paulg has quit [Ping timeout: 264 seconds]
kulos75 has quit [Quit: Konversation terminated!]
paulg has joined #yocto
<alperak>
good night everyone.
alperak has quit [Quit: Client closed]
sakman has quit [Quit: Leaving]
mbulut_ has quit [Ping timeout: 255 seconds]
wicki has joined #yocto
zpfvo has quit [Quit: Leaving.]
wicki has quit [Remote host closed the connection]
<moto-timo>
rburton: welcome to the djark side
mbulut_ has joined #yocto
sakman has joined #yocto
shane51 has joined #yocto
<LetoThe2nd>
moto-timo: LOLZ
<khem>
zeddii: heh see it lies in future but tells the truth at present
<khem>
Which means it lies in future :)
wicki has joined #yocto
leon-anavi has quit [Ping timeout: 255 seconds]
shane51 has quit [Quit: Client closed]
lexano has quit [Ping timeout: 255 seconds]
lexano has joined #yocto
florian has joined #yocto
dvergatal has quit [Ping timeout: 252 seconds]
dvergatal has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
jmd has joined #yocto
<mischief>
how does bitbake -u ncurses work? i just get an exception :(
<mischief>
got it to work on my vanilla mickledore tree, though it doesn't seem to accept any input.
Vonter has quit [Ping timeout: 260 seconds]
Vonter has joined #yocto
goliath has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
<rburton>
Maybe it doesn’t :)
prabhakarlad has quit [Quit: Client closed]
mbulut__ has joined #yocto
alessioigor has quit [Quit: alessioigor]
mbulut_ has quit [Ping timeout: 255 seconds]
mbulut__ has quit [Remote host closed the connection]
mraza has joined #yocto
mraza has quit [Quit: Client closed]
Kubu_work has quit [Quit: Leaving.]
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
<RP>
mischief: break for me too. it wasn't that good anyway
<RP>
mischief: add a params.updateToServer(server, os.environ.copy()) into main() in ncurses.py before params.updateFromServer(server) and it kind of works
mvlad has quit [Remote host closed the connection]
<rburton>
RP can I send a patch to delete it :)
<RP>
rburton: no
* RP
did wonder but it quite cute once you fix the missing line
<RP>
mischief: I've sent a patch
jmd has quit [Remote host closed the connection]
Dracos-Carazza has quit [Ping timeout: 256 seconds]
<mischief>
well, i'm stuck on kirkstone so that wont help me for now, but thanks! :-D
<mischief>
rburton: it does indeed not, but the code and the drawn ui seem to have been created with input in mine. i guess the author(s) just never got around to actually doing it.. it's a shame it doesn't have more features, i like curses UIs