<moto-timo>
kanavin: looks like we need to update perl-rdepends.txt ERROR: perl-5.34.0-r0 do_package_qa: QA Issue: /usr/lib/perl5/5.34.0/x86_64-linux/auto/DB_File/DB_File.so contained in package perl-module-db-file requires libdb-5.3.so()(64bit), but no providers found in RDEPENDS:perl-module-db-file? [file-rdeps]
rber|res has joined #yocto
RobertBerger has quit [Ping timeout: 265 seconds]
kpo has quit [Read error: Connection reset by peer]
kpo has joined #yocto
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
camus has joined #yocto
sakoman has quit [Quit: Leaving.]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
camus1 has joined #yocto
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
sakoman has joined #yocto
jmiehe1 has joined #yocto
jmiehe has quit [Ping timeout: 260 seconds]
jmiehe1 is now known as jmiehe
tgamblin has quit [Remote host closed the connection]
camus has quit [Ping timeout: 265 seconds]
camus has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has joined #yocto
tgamblin has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
nucatus has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
sakoman has quit [Quit: Leaving.]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
camus has quit [Ping timeout: 260 seconds]
camus has joined #yocto
nucatus has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has quit [Ping timeout: 265 seconds]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
sstiller has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
Flumpy33 has joined #yocto
tgamblin has joined #yocto
<JosefHolzmayrThe>
yo dudX
tgamblin has quit [Remote host closed the connection]
roussinm has quit [Quit: WeeChat 3.3-dev]
camus1 has joined #yocto
tgamblin has joined #yocto
camus has quit [Ping timeout: 265 seconds]
camus1 is now known as camus
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
Schlumpf has joined #yocto
tgamblin has quit [Remote host closed the connection]
rob_w has joined #yocto
tgamblin has joined #yocto
nucatus has joined #yocto
creich_ has quit [Quit: Leaving]
creich has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
mckoan|away is now known as mckoan
<mckoan>
good morning
camus1 has joined #yocto
Tokamak has quit [Ping timeout: 252 seconds]
tgamblin has joined #yocto
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
zpfvo has joined #yocto
rfuentess has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
ant__ has quit [Quit: Leaving]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
leon-anavi has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
Flumpy33 is now known as Sion
<Sion>
Morning
tgamblin has quit [Remote host closed the connection]
tre has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
camus has quit [Ping timeout: 260 seconds]
camus1 has joined #yocto
xmn has quit [Quit: ZZZzzz…]
rob_w has quit [Remote host closed the connection]
camus1 is now known as camus
F_Adrian has joined #yocto
<qschulz>
o/
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
nucatus has quit [Remote host closed the connection]
zeddiii has quit [Ping timeout: 264 seconds]
nucatus has joined #yocto
tgamblin has quit [Remote host closed the connection]
florian has joined #yocto
zeddii has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has quit [Ping timeout: 265 seconds]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
zeddii has quit [Ping timeout: 245 seconds]
tgamblin has joined #yocto
zeddii has joined #yocto
tgamblin has quit [Remote host closed the connection]
nucatus has joined #yocto
pgowda_ has joined #yocto
<gourve_l>
Hi! I have a small problem with DEFAULT_PREFERENCE and PREFERRED_RPROVIDER_virtual/recipe. I am on Dunfell, I have 2 recipes, "recipe-dev" and "recipe-prod". Each provides RPROVIDES_${PN} += "virtual/recipe". With PREFERRED_RPROVIDER_virtual/recipe ?= "recipe-prod" I can choose the recipe to build and by default I would prefere to embed recipe-prod. But, if I override the PREFERRED_RPROVIDER with a mistake in
<gourve_l>
the name like PREFERRED_RPROVIDER_virtual/recipe = "recipe-test", there's no warning and the recipe embedded is the "-dev" even if I put DEFAULT_PREFERENCE = "-1" in the -dev recipe. I understand that there's no warning, but is there a way to define a preferred version?
Schlumpf has quit [Quit: Client closed]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
rob_w has joined #yocto
<kanavin>
moto-timo, could be, but I am going to disable that module anyway
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
<JosefHolzmayrThe>
kanavin: what is gizmo? (other than a gremlin, ofc)
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
<JosefHolzmayrThe>
kanavin: ya sure, i've used it myself too (it refers to the Independence Day movie also), but I though you meant something specific for the mixin layer, thats why i asked
<kanavin>
JosefHolzmayrThe, customer project :) they want a certain 'gizmo' backported to dunfell
<JosefHolzmayrThe>
hehe
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
Ad0 has quit [Ping timeout: 245 seconds]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
fbre has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
Ad0 has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
Tokamak has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
Schlumpf has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
Schlumpf has quit [Quit: Client closed]
tgamblin has joined #yocto
<CocoJoe>
does anyone know a hardening layer for ssh?
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
<JosefHolzmayrThe>
CocoJoe: what would you such a layer expect to do?
<CocoJoe>
JosefHolzmayrThe tweaks to the sshd_config for better security
tgamblin has quit [Remote host closed the connection]
<JosefHolzmayrThe>
a layer just to slap in a config file which one would probably have to override anyways doesn't exactly sound useful to me...
<RP>
CocoJoe: our general policy is that if there are good security things we should be doing, we'd do them in the core
rob_w has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
zpfvo has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
schirma has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin has quit [Remote host closed the connection]
goliath has joined #yocto
mckoan is now known as mckoan|away
nucatus has quit [Remote host closed the connection]
camus1 has joined #yocto
nucatus has joined #yocto
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
jwillikers has joined #yocto
jwillikers has quit [Remote host closed the connection]
<JPEW>
rburton: ya, I'm suspected there might be a few errors in three l that code after I was looking though it
<rburton>
i basically ran bitbake core-image-sato -n in a loop with a clean build tree,and most of the time it was getting 99% reuse but occasionally (like, one in ten) would drop to 70% or so. found that at the bottom of cookerlog in the broken case.
<rburton>
should it just be an update instead of insert?
artri has joined #yocto
khem has quit [Read error: Connection reset by peer]
barath has quit [Write error: Connection reset by peer]
fabatera[m] has quit [Read error: Connection reset by peer]
falk0n[m] has quit [Read error: Connection reset by peer]
lexano[m]1 has quit [Write error: Connection reset by peer]
glembo[m] has quit [Read error: Connection reset by peer]
t_unix[m] has quit [Write error: Connection reset by peer]
scjg has quit [Write error: Connection reset by peer]
kayterina[m] has quit [Read error: Connection reset by peer]
Barry[m] has quit [Read error: Connection reset by peer]
michaelo[m] has quit [Read error: Connection reset by peer]
behanw[m] has quit [Read error: Connection reset by peer]
Markus[m]1 has quit [Read error: Connection reset by peer]
jmlemetayer[m] has quit [Read error: Connection reset by peer]
ericson23141 has quit [Write error: Connection reset by peer]
janvermaete[m] has quit [Read error: Connection reset by peer]
PascalBach[m] has quit [Write error: Connection reset by peer]
hmw[m] has quit [Write error: Connection reset by peer]
moto_timo[m] has quit [Write error: Connection reset by peer]
jonesv[m] has quit [Write error: Connection reset by peer]
ramprakash[m] has quit [Write error: Connection reset by peer]
saYco[m] has quit [Read error: Connection reset by peer]
DanielWalls[m] has quit [Read error: Connection reset by peer]
Nate[m]1 has quit [Read error: Connection reset by peer]
jaskij[m] has quit [Read error: Connection reset by peer]
SalamaSalama[m] has quit [Write error: Connection reset by peer]
berton[m] has quit [Read error: Connection reset by peer]
jwillikers[m] has quit [Write error: Connection reset by peer]
Jari[m] has quit [Read error: Connection reset by peer]
Spectrejan[m] has quit [Write error: Connection reset by peer]
dwagenk has quit [Read error: Connection reset by peer]
Emantor[m] has quit [Read error: Connection reset by peer]
k4wsys[m] has quit [Write error: Connection reset by peer]
cryptollision[m] has quit [Write error: Connection reset by peer]
azstevep[m] has quit [Write error: Connection reset by peer]
ejoerns[m] has quit [Write error: Connection reset by peer]
Alban[m] has quit [Write error: Connection reset by peer]
shoragan[m]1 has quit [Write error: Connection reset by peer]
coldspark29[m] has quit [Read error: Connection reset by peer]
jordemort has quit [Write error: Connection reset by peer]
meck[m] has quit [Write error: Connection reset by peer]
ezzuldin[m] has quit [Read error: Connection reset by peer]
JosefHolzmayrThe has quit [Write error: Connection reset by peer]
agherzan has quit [Write error: Connection reset by peer]
olani[m] has quit [Write error: Connection reset by peer]
hpsy[m] has quit [Write error: Connection reset by peer]
<rburton>
bye, matrix!
<JPEW>
rburton: it should be `INSERT OR IGNORE`
<rburton>
so, pass ignore=true in copy_from_upstream?
<JPEW>
Ya
<rburton>
i wish the test cycle wasn't ten minutes long
jmlemetayer[m] has joined #yocto
<JPEW>
rburton: Well, I just completely reworked the server.... want to test that :D
jordemort has joined #yocto
<rburton>
ha
<rburton>
yeah why not
Spectrejan[m] has joined #yocto
lexano[m] has joined #yocto
meck[m] has joined #yocto
Alban[m] has joined #yocto
Emantor[m] has joined #yocto
scjg has joined #yocto
kayterina[m] has joined #yocto
shoragan[m] has joined #yocto
khem has joined #yocto
<rburton>
i took a wireshark log of the chatter to see if there's anything obviously bad like slow responses or lots of new connections, but nothing stood out
<JPEW>
NOTE: It will delete the tasks_v2 table from an existing database!
ezzuldin[m] has joined #yocto
JosefHolzmayrThe has joined #yocto
<rburton>
ah i'm pointing at the typhoon server, so i can't test it right now
atril has joined #yocto
ramprakash[m] has joined #yocto
janvermaete[m] has joined #yocto
Markus[m]1 has joined #yocto
cryptollision[m] has joined #yocto
olani[m] has joined #yocto
SalamaSalama[m] has joined #yocto
kpo has quit [Read error: Connection reset by peer]
michaelo[m] has joined #yocto
berton[m] has joined #yocto
jaskij[m] has joined #yocto
kpo has joined #yocto
hpsy[m] has joined #yocto
saYco[m] has joined #yocto
ericson2314 has joined #yocto
jwillikers has quit [Remote host closed the connection]
artri has quit [Ping timeout: 265 seconds]
<JPEW>
rburton: typhoon as an upstream?
<rburton>
yeah
<rburton>
unless that is still a useful case
jwillikers has joined #yocto
<JPEW>
It "should" be compatible with the older server, so you can mix and match old upstream, new local, vise versa
<JPEW>
... not well tested though
<RP>
JPEW: looks good in theory!
<RP>
JPEW: question is what to do for release
<JPEW>
Well, I was thinking: I split out the test case for the "diverging report race", so we could make a quick fix to the old server (basically, the same thing you did client side, but on the server) to make that test case pass, then test the re-write after release
<JPEW>
It's nice when you have a test case that actually fails on the bug you are trying to fix :)
<RP>
JPEW: I noticed the test cases, they definitely help!
<RP>
JPEW: If we going to change this soon after release, I'm leaning towards changing now. There is a second factor which may sway this
<rburton>
testing a six-character fix now, but as the test cycle is so slow expect that to take a while
<RP>
rburton: tell me about the test cycles :/
<RP>
but cool, you're already both on it :)
<JPEW>
I... don't think I'm comfortable releasing a complete rewrite without a lot more testing, so I'd rather do the quick fix now and test more later (backport if necessary)
* JPEW
checks the release date
<RP>
JPEW: I just don't know how we're going to test this other than changing the main server and setting the autobuilder at it. After release, new users will be attempting to use it, before release, we just break the autobuilder :/
<RP>
it is late, but if we are changing it, there is a certain logic to doing it now and then sorting the release once it is tested/ready
<JPEW>
Hmm, OK. Do you want me to comment our deleting the old tables so we don't loose them during testing?
<RP>
JPEW: I think I can just move the DB out the way for testing as I'll have to change the PR server code anyway
<RP>
JPEW: We're about the enter the AB maint window so I think I'll switch the server over and queue up master-next to the new version and we can see how it works after maint
xmn has quit [Quit: ZZZzzz…]
<RP>
JPEW: having the tests does give us some confidence things should be ok
<override>
any bmap pros out here? im trying to show the write progress of a rootfs being written using bmap. any ideas how that can be done?
<override>
like with a normal file I can use something like seek, and divy up the file in chunks, write those and track progress
shanoth has joined #yocto
shanoth has left #yocto [#yocto]
zyga-mbp has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kiran has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
sakoman has joined #yocto
<smurray>
override: bmaptool shows a %age written, so perhaps take a look at how it manages that
fbre has quit [Quit: fbre]
<rburton>
JPEW: with that ignore=true at least one run was bad
<rburton>
i'll try and get another log
nucatus_ has joined #yocto
nucatus has quit [Ping timeout: 268 seconds]
zyga-mbp has joined #yocto
schirma has quit [Quit: Leaving]
<ykrons_>
Hello all
<ykrons_>
I'm trying to use a Dunfell recipe in Thud and I get an error related to a too old version of GCC for the native recipe (WARNING: C++ compiler (CXX=g++ , 5.4.0) too old, need g++ 6.3.0 or clang++ 8.0.0)
<ykrons_>
So I understand the gcc installed on my system is too old, but if I build the recipe in Dunfell, everything goes well.
<ykrons_>
Did Thud use the system gcc whereas Dunfell rebuild is one native gcc?
<ykrons_>
Did Thud uses the system GCC whereas Dunfell rebuilds is own native GCC?
<rburton>
JPEW: still happens, but no exception, so that wasn't the cause
<RP>
rburton: I'm puzzled about why there are duplicates in the first place
sstiller has quit [Quit: Leaving]
tre has quit [Remote host closed the connection]
<RP>
rburton: ah, I tracked it down as I see that in my build too. It is from the tasks when they run
<RP>
rburton: think we need to compare the equiv dbs in the two builds
rfuentess has quit [Remote host closed the connection]
<rburton>
i have two tmp/ directories to hand
Sion has quit [Quit: Konversation terminated!]
<RP>
rburton: cache/bb_unihashes.dat is a pickled dict
<RP>
2021-10-08 13:29:37,409 - oe-selftest - INFO - Building reproducibleA (sstate allowed)...
<RP>
2021-10-08 13:43:17,446 - oe-selftest - INFO - Building reproducibleB (sstate NOT allowed)...
<RP>
That is how sstate reuse should work :)
zyga-mbp has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ykrons_>
GCC was just a warning and is not blocking, that was another dependency that break the build. Imported from Dunfell and now it is fixed
<RP>
halstead: we have a new test hash equivalence server in bitbake master-next. We probably need to switch to this before release which is risky but the other choice is to switch after release which I don't like even more
<RP>
halstead: Can we stop the hashequiv server we have and move it and it's database somewhere safe, then bring up a version using master-next with a clean DB?
<RP>
halstead: hopefully this lets us clean out a load of old data but I would like a path back in case something goes wrong. We'd then test master-next with this on the AB after maint
F_Adrian has quit [Ping timeout: 265 seconds]
chrfle has quit [Ping timeout: 245 seconds]
florian has quit [Quit: Ex-Chat]
chrfle has joined #yocto
mckoan|away is now known as mckoan
mckoan is now known as mckoan|away
<halstead>
RP, yes. I'll create a new server for hashequiv and keep the current one for rollback.
<RP>
halstead: thanks. Keep in mind the new code would wipe data in the db file so don't run that against it! :)
florian has joined #yocto
jmiehe has quit [Ping timeout: 260 seconds]
florian has quit [Ping timeout: 252 seconds]
whuang0389 has joined #yocto
<whuang0389>
when i do a menuconfig in yocto
<whuang0389>
where are the changes saved?
<whuang0389>
bitbake virtual/kernel -c menuconfig
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
mischief2 has quit [Ping timeout: 264 seconds]
behanw has quit [Quit: Connection closed for inactivity]
ant__ has joined #yocto
<halstead>
JPEW, RP: the new bitbake master-next hashserv is in place. The previous hashserv is ready to roll back to if needed.
<whuang0389>
is there a way to list machine overrides ?
<vd898>
whuang0389 make bitbake print the MACHINEOVERRIDES variable ;-)
<whuang0389>
got it! :D
jwillikers has quit [Remote host closed the connection]
jwillikers has joined #yocto
jwillikers has quit [Remote host closed the connection]
jwillikers has joined #yocto
jwillikers has quit [Remote host closed the connection]
CocoJoe has quit [Quit: Client closed]
florian has joined #yocto
nucatus_ has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
<Tokamak>
has anyone here ever dealt with meta-mender? I've noticed they seem to be sidestepping yocto's patch mechanism for their own bash script hat patches. :(
<Tokamak>
running into an issue where i'm trying to patch a file they lay down, but do_patch is running before whatever kicks off their script.. :/
<Tokamak>
is there a way to tell yocto not to apply a patch automatically?
<vd898>
Tokamak if meta-bender placed their hacks in recipes or classes, you may use BBMASK to tell bitbake not to parse them
<Tokamak>
if i disable their hacks, i'm worried their stuff will break. for now, just trying to do a little test leaving their layer mostly alone. is it possible to disable my patch from being automatically applied?
alessioigor has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
<vd898>
Tokamak: how's your patch applied currently?
<Tokamak>
i'm just adding my local env.patch file to SRC_URI as a local file://0005-env.patch
<vd898>
then don't add it? or append SRC_URI conditionally
alessioigor has quit [Client Quit]
<Tokamak>
a bit confused. i want to make my patch available during build so their patch script picks it up
<vd898>
but you said "is it possible to disable my patch from being automatically applied"
<Tokamak>
i'm definitely frustrated they aren't doing things the yocto way (while still new to yocto myself - thus just frustrates things)
<Tokamak>
yes. i want the file present in the source dir. but not applied by do_patch
<vd898>
Tokamak: if that patch only adds a singular file, you don't have to write a patch for it, you can simply add the file to SRC_URI and specify where to place it with ;subdir=some/dir
<Tokamak>
unfortunately my patch is a delta over a file they lay down. thus the error is 'can't find include/env_default.h' (a file they lay down during configure)
<Tokamak>
is it possible to move do_patch to after the do_configure step?
<vd898>
like a custom kernel device tree is often added like this to the kernel sources: SRC_URI_append = " file://custom.dts;subdir=git/arch/${ARCH}/boot/dts"
<Tokamak>
right. i guess i'm fighting the automatic behavior when a file you add is a *.patch
<vd898>
Tokamak: no do_patch after do_configure doesn't make sense. You may copy their file over as well, instead of patching it. A bit ugly but that's not the worst.
florian has quit [Ping timeout: 252 seconds]
<Tokamak>
they are autogenerating the uboot enviornment file depending on a lot of mender_* variables. partially in uboot's config step, partially in their manual patch script
<Tokamak>
its definitely a mess..
<vd898>
I'm pretty sure they added a way to add your own environment. You should look into their u-boot recipe.
<Tokamak>
correction, not the environment file, but the built-in default environment w/in the uboot object
<vd898>
otherwise use your own u-boot fork (from theirs) and override their SRC_URI to use your own u-boot fork
<Tokamak>
thanks for the thoughts. frustrating in that these are rather extremem paths to test little changes.
<Tokamak>
meta-mender-core/recipies-bsp/u-boot-mender.inc is the pertinent behavior
<vd898>
what is it you're trying to add customize exactly?
<vd898>
-add
<RP>
kanavin: bringup is a test which failed to test it was present. I added it now
<Tokamak>
at the end of the day, just trying to redefine CONFIG_MENDER_BOOTCOMMAND in include/env_mender.h (laid down by one of their patches, triggered by do_mender_uboot_auto_configure task (i believe)
<Tokamak>
my patch is on the resulting file they lay down, but as you suggest, i'm looking to see if there is another way i can patch that define without touching their files..
<RP>
kanavin: I mean I added rsync to the worker. We need to fix bringup and the docs
<Tokamak>
the reason they may have taken this manual patch approach is u-boot seems to dynamically create include/env_default.h?
<Tokamak>
i suppose this is a normal autotools pattern. but they've chosen to patch a generated file instead of changing autotool's generation inputs?
jwillikers has joined #yocto
<RP>
Tokamak: Normally we would patch the inputs.
<Tokamak>
yes, indeed that seems more sane..
<ant__>
RP: hi there. I've been asked about about an old patch
<Tokamak>
so if env_default.h is generated by autotools configure step. i'm wondering if its crazy to define our own env_override.h that gets parsed by the c preprocessor after their env_mender.h, to override any defines as needed?
vd898 has quit [Quit: Client closed]
<ant__>
RP: the Q is
<ant__>
"
<ant__>
<ant__>
As I see it, this means that all kernel modules that are build as external modules and later installed from the feed don't run depmodmapper, and therefore require a reboot to make them work.
<ant__>
<ant__>
image.bbclass is a step in the build, so it only applies to kernel modules included in the image.
vd898 has joined #yocto
<ant__>
Am I correct?"
<ant__>
RP: I alnost never see external modules nor install images containing that so dunno...
<RP>
ant__: no, that isn't correct due to the if [ -z "$D" ] at the start of that function
<RP>
ant__: during rootfs/image, $D is set, on target it won't be
<ant__>
yes, on device it isn'set
<ant__>
..but why that Q?
<ant__>
after 6 years?
<ant__>
:/
<RP>
ant__: I have no idea
<ant__>
:)
<ant__>
thanks
florian has joined #yocto
dev1990 has joined #yocto
<Tokamak>
the rabit hole gets deeper. mender is automatically generating patches between source trees on the fly as well... :/
nucatus has quit [Remote host closed the connection]
florian has quit [Ping timeout: 252 seconds]
florian has joined #yocto
<RP>
moto-timo: thanks for the ptest-runner fix :)
<moto-timo>
RP: you are very welcome. Today I just said “nope! Fix this”
<moto-timo>
RP: I hope it helps us with the ptest timeouts
<RP>
moto-timo: I had seen the failure but not gotten to doing anything about it. Yes, I hope we can debug some of these better too
<moto-timo>
I’ve seen it multiple times but didn’t digest what was happening
jmiehe has joined #yocto
<moto-timo>
RP: the output might need some decorating, but at least it works now
<RP>
moto-timo: I've not been worrying about ptests for a bit, I've had other concerns :/
<moto-timo>
RP: understatement of the release
<RP>
moto-timo: you know me :)
atril has quit [Ping timeout: 250 seconds]
jwillikers has joined #yocto
gioyik has joined #yocto
<Tokamak>
so circling back. it seems that i was mistaken an their patches are being applied by do_patch. just for some reason yocto wants to apply my patches (added in my layer) before running the patches in their later? is there a way to order my patch after their patches?
<Tokamak>
e.g. i assumed patch ordering was preserved across layers by the 000N-* naming. but it seems that they are ordered in another way across layers?
xmn has joined #yocto
<moto-timo>
Tokamak: I’m guessing layer priority is affecting the order?
<Tokamak>
that also came to mind
<moto-timo>
Patches are applied in the order they appear in the SRC_URI variable
<Tokamak>
ohh, thanks
<moto-timo>
No sorting of any kind
<Tokamak>
was just going to ask if there was a sort function by chance ;)
<Tokamak>
but that definitely helps. i'm just doing SRC_URI += 'my.patch'. but i assume because of layer priority, their SRC_URI is appended after mine?
<vd898>
When is honister scheduled to be released?
atril has joined #yocto
<Tokamak>
interesting. so this is one way in which SRC_URI_append differs from SRC_URI += ?