|
Any way to enable automatic package-index if rpms are changed?
Not really, I don’t think bitbake has a way to build a recipe after all other recipes. Alex
Not really, I don’t think bitbake has a way to build a recipe after all other recipes. Alex
|
By
Alexander Kanavin
· #49064
·
|
|
boost monthly download limits
I wouldn't be super concerned about that, as Yocto servers carry copies of oe-core tarballs, and there is a fallback for that scenario. If it does occur, we should explore alternatives, but there's no
I wouldn't be super concerned about that, as Yocto servers carry copies of oe-core tarballs, and there is a fallback for that scenario. If it does occur, we should explore alternatives, but there's no
|
By
Alexander Kanavin
· #49004
·
|
|
Mechanism behind pkg_postinst_ontarget_${PN}
#yocto
I am not sure about deb-postinsts. What I see the script doing is: eval dpkg --configure -a $append_log Alex
I am not sure about deb-postinsts. What I see the script doing is: eval dpkg --configure -a $append_log Alex
|
By
Alexander Kanavin
· #48950
·
|
|
Mechanism behind pkg_postinst_ontarget_${PN}
#yocto
Actually, that depends on which package format you use. The script that executes the postinsts on target can be found in meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts. Alex
Actually, that depends on which package format you use. The script that executes the postinsts on target can be found in meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts. Alex
|
By
Alexander Kanavin
· #48948
·
|
|
Mechanism behind pkg_postinst_ontarget_${PN}
#yocto
You can start by inspecting your image's rootfs, the scripts to run on first boot should be in /etc/ somewhere. Are they? Alex
You can start by inspecting your image's rootfs, the scripts to run on first boot should be in /etc/ somewhere. Are they? Alex
|
By
Alexander Kanavin
· #48946
·
|
|
What are the key factors for yocto build speed?
I have to say that AMD aggressively pursuing core count increase on consumer level CPUs is awesome news for the YP. Previously, you had to buy some hugely overpriced Xeons or similar to be able to wor
I have to say that AMD aggressively pursuing core count increase on consumer level CPUs is awesome news for the YP. Previously, you had to buy some hugely overpriced Xeons or similar to be able to wor
|
By
Alexander Kanavin
· #48813
·
|
|
git fetcher: does not execute git fetch --tags or similar when HEAD has not changed
Right, now I see what you mean. The build process does not rely on static metadata in the source tree to determine the version, and is instead poking the git checkout to determine what the version is?
Right, now I see what you mean. The build process does not rely on static metadata in the source tree to determine the version, and is instead poking the git checkout to determine what the version is?
|
By
Alexander Kanavin
· #48775
·
|
|
git fetcher: does not execute git fetch --tags or similar when HEAD has not changed
'devtool upgrade' updates SRCREV to match the version tag that you specify: devtool upgrade -V <tag> If you omit -V, it will upgrade to the latest tag. It updates PV as well. Why is it unsuitable for
'devtool upgrade' updates SRCREV to match the version tag that you specify: devtool upgrade -V <tag> If you omit -V, it will upgrade to the latest tag. It updates PV as well. Why is it unsuitable for
|
By
Alexander Kanavin
· #48765
·
|
|
git fetcher: does not execute git fetch --tags or similar when HEAD has not changed
You can trivially script SRCREV updates ('devtool upgrade'/'devtool finish'). The disadvantage of using tags is that you lose reproducibility, as tags can be moved or deleted, and so I wouldn't encour
You can trivially script SRCREV updates ('devtool upgrade'/'devtool finish'). The disadvantage of using tags is that you lose reproducibility, as tags can be moved or deleted, and so I wouldn't encour
|
By
Alexander Kanavin
· #48762
·
|
|
[OE-core] Yocto Project Status WW09'20
Patch for gettext also sent :) glibc-locale and procps I could not reproduce :-/ Alex
Patch for gettext also sent :) glibc-locale and procps I could not reproduce :-/ Alex
|
By
Alexander Kanavin
· #48706
·
|
|
[OE-core] Yocto Project Status WW09'20
I sent a patch for this. Alex
I sent a patch for this. Alex
|
By
Alexander Kanavin
· #48687
·
|
|
Building CentOS based filesystem
#yocto
If a customer wants CentOS, they should be using CentOS. I really wouldn't want to embark on that path, you'll be constantly dealing with incompatibilities and incorrect assumptions. Alex
If a customer wants CentOS, they should be using CentOS. I really wouldn't want to embark on that path, you'll be constantly dealing with incompatibilities and incorrect assumptions. Alex
|
By
Alexander Kanavin
· #48588
·
|
|
Lots of basehash related errors
It's an issue with a recipe in your custom layer. If you can show the layer, we may be able to help. Are you sure a current timestamp isn't sneaked into the build by something in that layer? Alex
It's an issue with a recipe in your custom layer. If you can show the layer, we may be able to help. Are you sure a current timestamp isn't sneaked into the build by something in that layer? Alex
|
By
Alexander Kanavin
· #48537
·
|
|
[OE-core] Yocto Project Status WW07'20
What are the current plans for centos 7? Alex
What are the current plans for centos 7? Alex
|
By
Alexander Kanavin
· #48488
·
|
|
Issue while adding the support for TLS1.3 in existing krogoth yocto
#yocto
#apt
#raspberrypi
Backporting core pieces across many yocto releases is basically impossible. You more or less end up having to move and integrate half of the stack, which is a herculean task. The correct way to approa
Backporting core pieces across many yocto releases is basically impossible. You more or less end up having to move and integrate half of the stack, which is a herculean task. The correct way to approa
|
By
Alexander Kanavin
· #48466
·
|
|
do we have a slack channel for yocto?
There is irc. #yocto @freenode. Alex
There is irc. #yocto @freenode. Alex
|
By
Alexander Kanavin
· #48457
·
|
|
master/master-next missing from poky repo?
Something is wrong, as master and master-next are missing here? http://git.yoctoproject.org/cgit/cgit.cgi/poky/ Alex
Something is wrong, as master and master-next are missing here? http://git.yoctoproject.org/cgit/cgit.cgi/poky/ Alex
|
By
Alexander Kanavin
· #48429
·
|
|
Incrementally building constantly changing application source in a workflow-friendly way with
#yocto
Can you issue a 'bitbake-dumpsig -t fetch recipename' (writing from memory, so exact syntax may vary). This should show what goes into the task signature for the fetcher, and all individual files in s
Can you issue a 'bitbake-dumpsig -t fetch recipename' (writing from memory, so exact syntax may vary). This should show what goes into the task signature for the fetcher, and all individual files in s
|
By
Alexander Kanavin
· #48420
·
|
|
Incrementally building constantly changing application source in a workflow-friendly way with
#yocto
This should simply work; what exactly doesn't work for you? Do wipe tmp/ before proceeding further, as -f 'taints' the build. Alex
This should simply work; what exactly doesn't work for you? Do wipe tmp/ before proceeding further, as -f 'taints' the build. Alex
|
By
Alexander Kanavin
· #48416
·
|
|
Incrementally building constantly changing application source in a workflow-friendly way with
#yocto
Try placing the sources into recipes-my-application/files/src, then SRC_URI = "file://src/" should work. Alex
Try placing the sources into recipes-my-application/files/src, then SRC_URI = "file://src/" should work. Alex
|
By
Alexander Kanavin
· #48410
·
|