<thomas_>
Good morning. I try to build a new image with an updated kernel (It just changed the git commit of the kernel), and I got a lot of these errors: https://dpaste.com/5VY4FVBKY.txt
<thomas_>
I don't understand the version backwards complain - the version didnt go backwards
<thomas_>
How I can fix this, or what is the better approach to make "microadjustments" of the kernel, which do not justify an increase of the kernel version?
<kroon>
thomas_, id be interested to hear what others say, but reason is probably the git hash number being treated as a version number going backwards. I have ERROR_QA:remove = "version-going-backwards" in my distro configuration
<thomas_>
kroon, yeah - that would suppress the warning. But I would not like to suppress for every package - just in the case if anything bad happen and I would not notice it..
<kroon>
thomas_, I think you could do it with a per recipe override, like ERROR_QA:pn-linux-ti-staging:remove = "..."
<kroon>
or in a .bbappend for the kernel
<thomas_>
Hmm.. yes. But would this error pop up for every package which uses AUTOINC?
tomzy_0 has joined #yocto
leon-anavi has joined #yocto
<thomas_>
The documentation says, that an enabled PR service handle this, and would replace "git{i}" with an increasing number
rob_w has joined #yocto
<thomas_>
But I'm not sure, if this also works when I manually set the SRCREV
goliath has joined #yocto
<thomas_>
Ok, now I can ask more specific: I have PR service enabled in my local conf. I have a kernel recipe append: https://dpaste.com/BUT8XMNJ3.txt When I change manually SRCREV and rebuild the kernel FOR THE FIRST TIME, I got these errors: https://dpaste.com/5VY4FVBKY.txt
<thomas_>
When I rebuild it after I changed the SRCREV the second time, I got no errors.
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
<thomas_>
I would expect, that the AUTOINC variable would increment from 0 to 1, after I changed the SRCREV. But it seems not to happen. What could be the reason for that?
F_Adrian has quit [Quit: Leaving]
nemik has quit [Ping timeout: 240 seconds]
tre has joined #yocto
nemik has joined #yocto
creich has joined #yocto
PaowZ has quit [Remote host closed the connection]
PaowZ has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
creich has quit [Quit: Leaving]
rob_w has quit [Ping timeout: 260 seconds]
PaowZ has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
frieder has joined #yocto
oleksandr has joined #yocto
PaowZ has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
F_Adrian has joined #yocto
PaowZ has joined #yocto
PaowZ has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
PaowZ has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
PaowZ has joined #yocto
guysoft42 has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
PaowZ has joined #yocto
gsalazar has joined #yocto
rfuentess has joined #yocto
beneth has joined #yocto
PaowZ has quit [Read error: Connection reset by peer]
PaowZ has joined #yocto
PaowZ has quit [Ping timeout: 252 seconds]
PaowZ has joined #yocto
dev1990 has joined #yocto
ardo has joined #yocto
mvlad has joined #yocto
davidinux has quit [Quit: WeeChat 2.8]
GillesM has joined #yocto
GillesM has quit [Client Quit]
amahnui1 has joined #yocto
tomzy_0 has quit [Quit: Client closed]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
florian has joined #yocto
Schiller has joined #yocto
mvlad has quit [Remote host closed the connection]
mvlad has joined #yocto
selff has joined #yocto
<selff>
hello everyone. i am trying to create root, boot and swap space in the ".wks" file. however, when i create a swap area and do a "free -m" at run time, the swap area shows 0. here is my partitions :
<michalkotyla>
Did someone try to put the system image into another system image? I want to build .iso for image A, copy it to the rootfs of image B, and build .iso for image B. I can add image A to DEPENDS var in image B, and what's next? I can add do_install append in image B recipe and copy .iso from recipe A workdir - but I think mixing workdirs between recipes is not a recommended way to do that?
GNUmoon has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
<mckoan>
michalkotyla: see multiconfig
<LetoThe2nd>
yo dudX
<qschulz>
o/
<mckoan>
hey
xmn has quit [Quit: ZZZzzz…]
<ptsneves>
michalkotyla On your imageB do_rootfs[depends] += "Image:A:image_complete" Then in some rootfspostproc func copy the iso manually
<LetoThe2nd>
qschulz: \o
<LetoThe2nd>
mckoan: ho, lets got.
<ptsneves>
LetoThe2nd no youtube link to the song?
<LetoThe2nd>
ptsneves: i know that mckoan is highly competent, therefore able to find a link himself if desired. free metal links are only provided for rburton
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<agherzan>
Is there a matrix room for the Yocto summit?
nemik has quit [Ping timeout: 240 seconds]
starblue has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
<LetoThe2nd>
agherzan: it isn't listed on the official brige, but can be reached. AFAIK shoragan[m] did so last time too.
starblue has joined #yocto
<agherzan>
As a bridge, yes.
<agherzan>
I thought we have one official too with a bridge set up. But I'm fine
<LetoThe2nd>
yeah but no "official" one, at least not so far. maybe halstead can look into it, but no promises.
<agherzan>
I don't think it is a must
<LetoThe2nd>
certainly not a must, but it might be useful. so nothing bad in suggesting it.
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<Schiller>
Hello to everyone. In the YPAutobuilder i have hooks to own repositories on our servers. I configured this in the config.json and config.py. Only problem is that when i start a build manual then i can select meta-openembedded , branch=dunfell , but revision is always HEAD. How can i chose from our existing revisions?
<Schiller>
nevermind. he seems to take them now. idk what was wrong before but it now displays my set rivision. Maybe typo and he switched to default HEAD or smth.
seninha has joined #yocto
tre has quit [Ping timeout: 252 seconds]
<selff>
mckoan i added the following line for swap in fstab:
<selff>
rburton i used "LABEL=swap none swap defaults 0 0 " instead of "/swapfile none swap defaults 0 0 " in fstab and added "part swap --ondisk mmcblk0 --fstype=swap --label swap --align 4096 --size 2000M" to ".wks" file. problem gone and successfully created 2gb swap. thank you so much.
<zeddii>
RP: I'm finishing up meta-virt stuff this morning, then can check 5.10-stable for gcc fixes. I assume master-next is the right branch for me to try a build against gcc12?
<kanavin>
landgraf, it's better if you ask this on the mailing list, and not poke RP directly
<kanavin>
if it's broken, check if it is still broken with latest master, and better yet, propose a fix
adrian__ has joined #yocto
jwillikers has joined #yocto
adrian_ has quit [Ping timeout: 276 seconds]
<zeddii>
RP: I do see a fix for the warning in greg's queue (by scanning lkml), I'll see if it made the -stable release and otherwise try cherry-picking it.
jwillikers has quit [Ping timeout: 250 seconds]
<RP>
landgraf: we shouldn't break the zephyr case so that wasn't intentional
<RP>
zeddii: I dropped it from next as it can't fix it at this point
<Schiller>
In YPAutobuilder i want to set my branch and rivision but revision seems to always go to HEAD. I eddited config.py and config.json for builds.
<rburton>
zeddii: would you be happy merging that xen patch i posted from suse for the short term? I can get a patch up.
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
<zeddii>
rburton: I'll grab it and try a patch here. I have myself setup, so its probably easier to just spin it in myself.
<rburton>
ok, cool. i started a build but i don't have anything from master built in the last few days, so it's from scratch
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<Schiller>
for example the repo-defaults in the config.json got rivision HEAD
<jaskij[m]>
`ERROR: iputils-20211215-r0 do_packagedata: QA Issue: Package version for package iputils-src went backwards which would break package feeds (from 0:s20200821-r0 to 0:20211215-r0) [version-going-backwards]`
<jaskij[m]>
Does this look like a bug to anyone else?
<jaskij[m]>
ah, it's the missing s before the datecode
<jaskij[m]>
I should probably do a clean rebuild when switching branches?
<landgraf>
qschulz: I like sources list (last one) :)
xmn has joined #yocto
BCMM has joined #yocto
<bigendian>
putting defconfig in machine named subdir seems perfect for me. thanks again qschulz and rburton of course
<jclsn[m]>
But when I open the file, there is no std::experimental::std::experimental. It is just std::experimental::filesystem
<jclsn[m]>
It does this for multiple entries in that file
<jclsn[m]>
Has anyone ever seen something like this before? Seems like a broken Cmake
florian_kc has joined #yocto
selff has quit [Quit: Client closed]
<Schiller>
anyone knowing how to set a default revision in the ypautobuilder? Branch works Revision is always HEAD.
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
ptsneves has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
sakoman has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
otavio has quit [Ping timeout: 260 seconds]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
otavio has joined #yocto
otavio has quit [Ping timeout: 240 seconds]
Schiller has quit [Quit: Client closed]
otavio has joined #yocto
thomas_ has quit [Ping timeout: 256 seconds]
goliath has quit [Quit: SIGSEGV]
<dvorkindmitry>
I have one recipe and two GIT mirrors. Need to have an option to choose between mirrors in outer config file. One man said about SRC_URI:pn-myrecipe... Any examples or other ideas?
adrian__ has quit [Ping timeout: 250 seconds]
otavio has quit [Ping timeout: 252 seconds]
otavio has joined #yocto
ptsneves has quit [Quit: Client closed]
<rburton>
SRC_URI:pn-myrecipe = "git://...."
<rburton>
alternatively, set the recipe to use the external mirror in the recipe, and then use a config file that sets a PREMIRROR to redirect it to the internal one
<agherzan>
khem: nice. Any idea how much that usually takes? No rush but I'd like to plan accordingly
Tokamak has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
amahnui1 has quit [Quit: Connection closed for inactivity]
<khem>
usually point releases are roughly 6-8 weeks so it will take some time for it to get into kirkstone
<shoragan[m]>
<LetoThe2nd> "Andrei Gherzan: it isn't..." <- I still have #yocto-summit-2021.11:libera.chat in my list, so it was just the automatic bridge.
kevinrowland has joined #yocto
prabhakarlad has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
Tokamak has quit [Ping timeout: 246 seconds]
Tokamak has joined #yocto
gsalazar has quit [Remote host closed the connection]
<kergoth>
Any objection to making it so 'bitbake -e' doesn't obey BBTARGETS? Having it do so really doesn't make sense, and makes it harder to look at global env data, and breaks for multiple targets
seninha has joined #yocto
amahnui1 has joined #yocto
<kergoth>
Hmm, thinking about starting a thread on the layer setup and configuration thing to solicit thoughts and start brainstorming
RP has joined #yocto
Tokamak_ has quit [Ping timeout: 246 seconds]
Tokamak has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 248 seconds]
camus1 is now known as camus
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
florian_kc has joined #yocto
davidinux has joined #yocto
davidinux has quit [Ping timeout: 246 seconds]
Tokamak has quit [Ping timeout: 256 seconds]
Tokamak has joined #yocto
mvlad has quit [Remote host closed the connection]
<kergoth>
Hmm, YOE is interesting, definitely goes a different direction in configuration, addresses one of the things I dislike about kas, which is how the use of yaml configuration is putting a layer obscuring how things normally work with oe
<kergoth>
I like the reframing of the use of local.conf, I think that's absolutely necessary to avoid the bad pattern of overuse of local.conf for everything and not having your workspace configuration manageed
<kergoth>
I don't love that you essentially need to fork the yoe-distro repo to start work on your own product based on it, though. Works, but..
* kergoth
juggling various ideas between yoe, whisk, and kas in his head
GNUmoon has quit [Ping timeout: 240 seconds]
<RP>
kergoth: I need to look at what YOE is doing
<kergoth>
https://github.com/YoeDistro/yoe-distro -- i don't love the heavy reliance on sourcing into the user's shell, i kind of want to *reduce* that, not push harder in that direction, though i can see the upsides, simple to just source a script and not even have to set the machine beyond that.. it uses shell functions instead of a separate tool provide workflow aids
<kergoth>
I like that it avoids the yaml config approach, and I like the reframing of local vs site configuration. But I like whisk's concept of a product and all-targets stuff to ease multiconfig usage, and I like kas's subcommand-based approach with plugins, though I dislike that it can't load them from layers.
amahnui1 has quit [Quit: Connection closed for inactivity]
<kergoth>
Trying to come up with a coherent proposal to somehow combine those. my head hurts :)
<RP>
kergoth: did you look at what the autobuilder code does?
<kergoth>
Good point, I definitely need to take a closer look at that! I've seen the configuration files for the jobs but I think that's all
<RP>
kergoth: its another variation, tailored for a specific use but there are some ideas in there I like too, just to complicate things
<RP>
The inheritance in the json works nicely
<kergoth>
I was explaining to my wife yesterday how hard it is to do much of anything given how flexible we need to be and the vast number of use cases, none of which are listed anywhere, that we need to support :) Anything you add has to be able to work for eeeevvverything. or at least avoid limitations as much as possible
<RP>
kergoth: this is why I keep putting off the layerconfig/setup stuff :/
<RP>
kergoth: I think the best approach may be just to "standardise" on the several current standards and allow bitbake-setup to drive them somehow in a more generic way as they ultimately all do roughly the same things, just in different ways
<kergoth>
control repository and moving toward configuration management for your product/project configuration, actively avoiding shoving build configuration into local.conf and an uncontrolled build directory.
<kergoth>
I can see that. Perhaps we need a very lightweight tool that's easy to extend that can call out to underlying mechanisms with its subcommands, so you can easily customize the commands for your workflows, I think this is important, and it should be as easy as adding a prefixed shell script to the PATH the way you do with git.. and certain common elements to all of the current tools, such as creation of a product/project source