<aduskett>
hey, is there a way to force bitbake to verbosely show the URL it's attempting to download a recipe from? I am trying to setup a mirror and want to make sure I got the mirror correct.
<aduskett>
odd that even "-vvv" doesn't print out what URL is being attempted
davidinux has joined #yocto
Saur_Home16 has quit [Quit: Client closed]
Saur_Home16 has joined #yocto
<aduskett>
mckoan: does SRC_URI get populated with mirrors?
<RP>
aduskett: did you try -DDv ?
<RP>
or look at the do_fetch log itself
<aduskett>
ahhh -DDv does work!
<aduskett>
Now to figure out how to get premirrors working
SEGFAULT-berlin has joined #yocto
<aduskett>
and they work! Thanks for the help RP!
geoff__ has quit [Remote host closed the connection]
bhstalel has joined #yocto
<bhstalel>
Hello All, I know that ".so" symlinks goes only to "-dev" package, so if BitBake finds ".so" symlinks in other packages during do_split_package, does it ignore it ?
huntercao69 has joined #yocto
huntercao69 has left #yocto [#yocto]
<RP>
bhstalel: bitbake does what the FILES:* variables say
huntercao has joined #yocto
<bhstalel>
RP I mean if a symlink .so is found in -dev and in -lib packages, it only gets installed in -dev package, and not in -lib, does BitBake makes sure no file duplication in the packages provided by the same recipe ?
<RP>
bhstalel: files only go into one package in a given recipe
<RP>
bhstalel: it iterates through PACKAGES, matching files with FILES:<pkg> and the first match claims the file/symlink
<bhstalel>
RP Yes, that is the answer I am looking for. Thanks
SEGFAULT-berlin has quit [Quit: Client closed]
Abp has quit [Ping timeout: 252 seconds]
Abp has joined #yocto
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
Jones42 has quit [Ping timeout: 245 seconds]
jclsn has quit [Quit: WeeChat 4.4.3]
OnkelUll_ has joined #yocto
Saur__ has joined #yocto
huntercao has quit [Remote host closed the connection]
huntercao has joined #yocto
Abp has quit [*.net *.split]
ablu has quit [*.net *.split]
leon-anavi has quit [*.net *.split]
aduskett has quit [*.net *.split]
merit has quit [*.net *.split]
mjm has quit [*.net *.split]
OnkelUlla has quit [*.net *.split]
sakman has quit [*.net *.split]
tlwoerner has quit [*.net *.split]
marka has quit [*.net *.split]
Saur_ has quit [*.net *.split]
v0n has quit [*.net *.split]
dario has quit [*.net *.split]
mansandersson has quit [*.net *.split]
dlan has quit [*.net *.split]
duracrisis has quit [*.net *.split]
iokill has quit [*.net *.split]
jstephan has quit [*.net *.split]
alinucs_ has quit [*.net *.split]
Saur__ is now known as Saur_
leon-anavi has joined #yocto
Abp has joined #yocto
aduskett has joined #yocto
ablu has joined #yocto
mjm has joined #yocto
merit has joined #yocto
marka has joined #yocto
tlwoerner has joined #yocto
v0n has joined #yocto
dario has joined #yocto
dlan has joined #yocto
mansandersson has joined #yocto
duracrisis has joined #yocto
iokill has joined #yocto
jstephan has joined #yocto
alinucs_ has joined #yocto
sakman has joined #yocto
albeu has joined #yocto
gsalazar has joined #yocto
jmiehe has joined #yocto
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
jmiehe has quit [Client Quit]
jmiehe has joined #yocto
Abp has quit [Ping timeout: 260 seconds]
Abp has joined #yocto
jmiehe has quit [Quit: jmiehe]
huntercao has quit [Remote host closed the connection]
huntercao has joined #yocto
OnkelUll_ is now known as OnkelUlla
Saur has quit [Ping timeout: 245 seconds]
olani has quit [Ping timeout: 260 seconds]
davidinux has quit [Quit: WeeChat 4.3.1]
Saur has joined #yocto
frgo has quit [Remote host closed the connection]
cyxae has joined #yocto
mbulut has joined #yocto
rob_w has quit [Remote host closed the connection]
Abp has quit [Ping timeout: 276 seconds]
Abp has joined #yocto
Xagen has joined #yocto
leon-anavi has quit [Remote host closed the connection]
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
dgriego has quit [Quit: Computer going to sleep]
dgriego has joined #yocto
albeu has quit [Quit: albeu]
olani has joined #yocto
rfuentess has quit [Remote host closed the connection]
florian has quit [Quit: Ex-Chat]
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #yocto
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #yocto
aduskett has quit [Quit: Konversation terminated!]
huntercao has quit [Remote host closed the connection]
huntercao has joined #yocto
nerdboy has quit [Ping timeout: 248 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Tyaku has quit [Quit: Lost terminal]
mckoan is now known as mckoan|away
naspar has joined #yocto
<naspar>
HI!
<naspar>
A real quick question: Could yocto be used to build/bake existing official linux distribution (i.e. ubuntu,fedora,arch) as an intermediate layer to customize the final image to satisfy specific requirements (security, usage, vertical OS to cope with specific needs and regulations) ?
<naspar>
In short:
<naspar>
1. run the yocto build taking an existing linux version as input
<naspar>
2. configure and cusotmise it by leverange the excellent yocto build process
<naspar>
3. test and use all the beauty from yocto ecosystem
<naspar>
Thanks for answering .. appreciate you help and point of view!
Kubu_work has quit [Quit: Leaving.]
<RP>
naspar: no, we don't have the metadata to match fedora/ubuntu/arch. Yocto Project is its own Linux distro. If you want the others, use them!
<RP>
naspar: the others are native compile build processes, yocto project cross compiles so they are very different
florian has joined #yocto
<rburton>
there are projects that try and "build debian with yocto" and you're basically forcing a round peg into a square hole and not being able to reuse anything useful.
<naspar>
i dont want to use the others, i would like to leverage the solid Yocto build process and its ecosystem without reinventing the wheel ..
<naspar>
clear enough .. thanks for answering!
Articulus has quit [Quit: Leaving]
<rburton>
if you want to use the solid yocto build process and eco system then use yocto
<rburton>
if you want ubuntu, then use ubuntu
<naspar>
I think I haven't understood the project yet, my fault for not having read the docs or spent more time on researching
<naspar>
makes sense rburton, thank you!
naspar has quit [Quit: Client closed]
Ad0 has quit [Ping timeout: 252 seconds]
jmd has joined #yocto
zpfvo has quit [Quit: Leaving.]
jclsn has joined #yocto
Ad0 has joined #yocto
druppy has joined #yocto
gsalazar has quit [Remote host closed the connection]
huntercao has quit [Remote host closed the connection]
huntercao has joined #yocto
prabhakalad has quit [Ping timeout: 265 seconds]
prabhakalad has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
prabhakalad has quit [Ping timeout: 255 seconds]
prabhakalad has joined #yocto
druppy has quit [Ping timeout: 248 seconds]
frieder has quit [Remote host closed the connection]
Kubu_work has joined #yocto
ptsneves has joined #yocto
ptsneves has quit [Client Quit]
bhstalel has quit [Ping timeout: 256 seconds]
huntercao has quit [Ping timeout: 256 seconds]
mischief has quit [Ping timeout: 244 seconds]
mischief has joined #yocto
<JPEW>
RP: Hopefully the bitbake exception stuff looks good. I think that will need backported? It also doesn't do the call stack filtering for ExpansionError like the old code did, but I _think_ it's still possible with `traceback` if we want
<JPEW>
Other than that it seems functionally equivalent (and simpler to maintain!)
<RP>
JPEW: I'm really happy to get rid of that code!
<RP>
JPEW: I was running it through testing but ran into unrelated failures. It will need another test run but then it will need backporting, yes
<RP>
JPEW: the ExpansionError case is kind of important as it stopped us showing huge back traces with zillions of lines in them :/
<JPEW>
OK. I didn't notice that when I tested it (it was just one line of backtrace) but I'll see if I can figure out how to make traceback do that
<RP>
JPEW: i'm guessing something like A = "${B}"; B = "${C}" C= "${D}"; D = "${@<invalidpython>}"
<JPEW>
Ya, I think I only test with one level
<RP>
JPEW: basically we're saying that for an expansion error, skip all the looping within bitbake itelf
<JPEW>
Right makes sense
mbulut has quit [Remote host closed the connection]
* JPEW
will gladly be distracted from his YP summit presentation....
<RP>
haha, that bad! :)
Kubu_work has quit [Quit: Leaving.]
jmd has quit [Remote host closed the connection]
amitk has joined #yocto
<JPEW>
RP: I think I've got it. Do you want a V2 or a new pacth?
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<RP>
JPEW: whichever. I'll replace what I have in -next with it :)
<RP>
JPEW: it depends whether it is a complete rewrite or an incremental thing
Abp has quit [Ping timeout: 276 seconds]
<JPEW>
It's mostly just a little more code in the exception handler, but I'll send a V2 so it's easier to backport all together
<RP>
JPEW: thanks
<RP>
JPEW: right, a replacement patch makes sense. I wasn't quite sure what you were asking
<JPEW>
mmm, the trick will be that it used Python 3.7 functionality, which will be fine on master. Have to be careful on the backports
<JPEW>
(master is 3.8)
<JPEW>
Prior to 3.7, the backtraces are immutable, so we can't filter them
<RP>
JPEW: bitbake 2.0 is python 3.6 :(
druppy has joined #yocto
<JPEW>
Ya, I think it will just depend on which release has the websockets password support
<RP>
I guess kirkstone doesn't?
<JPEW>
Correct
<JPEW>
password support was added Nov 2023
<JPEW>
Ya, we should be fine. scarthgap is the first release with passwords and it's Python 3.8
<JPEW>
nanbield is 3.8 also FWIW
<RP>
JPEW: good to know, thanks!
amitk has quit [Ping timeout: 245 seconds]
Abp has joined #yocto
<RP>
JPEW: the exit handling in there is interesting. Does the parser always exit upon exception?