<khem>
IMO we should revert the opkg-utils upgrade for now
sakman1 has joined #yocto
sakman has quit [Ping timeout: 264 seconds]
sakman1 is now known as sakman
davidinux has quit [Ping timeout: 255 seconds]
davidinux has joined #yocto
Daanct12 has joined #yocto
yudjinn has quit [Read error: Connection reset by peer]
yudjinn has joined #yocto
goliath has quit [Quit: SIGSEGV]
Saur has quit [Ping timeout: 245 seconds]
Saur has joined #yocto
kpo_ has quit [Ping timeout: 245 seconds]
xmn has joined #yocto
skokkonda has joined #yocto
Guest55 has joined #yocto
<Guest55>
I'm encountering an issue during the build process where the packagegroup-rust-cross-canadian-qemux86-64-1.0-r0.x86_64_nativesdk package is reporting a dependency problem with rust-cross-canadian-x86-64, specifically requiring libstdc++.so.6(GLIBCXX_3.4.30)(64bit). Upon investigation, I found that the rust-cross-canadian-qemux86-64 binary files
<Guest55>
contain the necessary symbol, while other packages like binutils and gcc cross-canadian do not generate GLIBCXX_3.4.30. I attempted to address this by adding libstdc++ as a dependency in the rust-cross-canadian recipe, but the issue persists. I am seeking for guidance on ensuring consistent GLIBCXX_3.4.30 generation across rust package during the
<Guest55>
cross-compilation process.
Guest456123 has joined #yocto
Guest456123 has quit [Quit: Client closed]
xmn has quit [Read error: Connection reset by peer]
xmn has joined #yocto
camus has quit [Remote host closed the connection]
camus has joined #yocto
Guest55 has quit [Ping timeout: 250 seconds]
linfax has joined #yocto
Guest55 has joined #yocto
MarioMariollini has joined #yocto
vladest1 has joined #yocto
vladest has quit [Ping timeout: 268 seconds]
vladest1 has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
<RP>
khem: good to have at least some start on it!
<RP>
khem: I suspect the acl changes.
<RP>
khem: dvergatal may be interested to know that, not sure if he can help
linfax has quit [Remote host closed the connection]
<MarioMariollini>
RP: good morning, seems the irc logs don't include 2024 yet, and my client disconnected. Not sure if you had messaged me back or not yesterday, I am going to keep working on my issue today :)
Guest55 has quit [Ping timeout: 250 seconds]
<RP>
MarioMariollini: you said you faced an uphill battle and I didn't really have anything I could add :/
<MarioMariollini>
Oh ok cool haha so let's start climbing I guess thanks
vladest has joined #yocto
zpfvo has joined #yocto
brrm has quit [Ping timeout: 264 seconds]
brrm has joined #yocto
linfax has joined #yocto
lexano has quit [Ping timeout: 276 seconds]
olani- has joined #yocto
olani- has quit [Ping timeout: 260 seconds]
olani- has joined #yocto
lexano has joined #yocto
xmn has quit [Ping timeout: 256 seconds]
Guest55 has joined #yocto
alessioigor has joined #yocto
alperak has joined #yocto
alessioigor has quit [Remote host closed the connection]
Guest81 has joined #yocto
alessioigor has joined #yocto
Guest55 has quit [Ping timeout: 250 seconds]
tnovotny has joined #yocto
Guest81 has quit [Ping timeout: 250 seconds]
prabhakarlad has joined #yocto
olani- has quit [Remote host closed the connection]
olani- has joined #yocto
samkent has joined #yocto
Guest55 has joined #yocto
olani_ has joined #yocto
nweafliab has joined #yocto
leon-anavi has joined #yocto
nweafliab has quit [Client Quit]
olani- has quit [Quit: Using Circe, the loveliest of all IRC clients]
olani_ has quit [Client Quit]
olani- has joined #yocto
<abelloni>
khem: yeah, I add a rebase failure
<abelloni>
actually I had two rebases in the same folder so I lost a bunch of patches
sakman has quit [Ping timeout: 256 seconds]
<abelloni>
Ah no, this isn't what happened
<abelloni>
I would really like people to send series as series
<KanjiMonster>
khem: looking at the bisected commit, I see it adding a "--numeric-owner" to one of the tar invocations at the bottom, which I would guess is the source of the regression
mvlad has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
zpfvo has joined #yocto
Guest55 has quit [Ping timeout: 250 seconds]
<RP>
KanjiMonster: could you comment in the bug please. That sounds right
Guest55 has joined #yocto
florian has joined #yocto
samkent has quit [Remote host closed the connection]
samkent has joined #yocto
olani- has quit [Ping timeout: 256 seconds]
Vonter has quit [Ping timeout: 256 seconds]
Vonter has joined #yocto
tleb has quit [Write error: Connection reset by peer]
raghavgururajan_ has quit [Write error: Connection reset by peer]
jonesv has quit [Remote host closed the connection]
raghavgururajan has joined #yocto
tleb has joined #yocto
jonesv has joined #yocto
<alessioigor>
MarioMariollini: I am just curious... Are you using powerpc o powerpcspe?
<MarioMariollini>
powerpc, specifically the e5500 cpu in 64-bit mode
<MarioMariollini>
seems the problem I was having with gdb compilation comes from the same root cause of the first one, where a certain folder does not exist, so I am trying to see how this paths are being built if maybe the error comes from there
<MarioMariollini>
the tune for the machine is powerpc64, the tune for lib32 is powerpc, but it is not populating the powerpc directories (but looks for things there, like python for gdb compilation)
<RP>
MarioMariollini: it is possible multilib config for powerpc isn't entirely correct/working since I think we've only ever tested multlib for mips/arm/x86
<MarioMariollini>
RP: seems like it. I have a day or two to look at it and potentially fix it, so if you have any tips on where to look or start looking it'd be greatly appreciated
<RP>
MarioMariollini: I'd be doing what you're doing, trying it, see how it fails and then trying to work out why
Guest55 has quit [Quit: Client closed]
xmn has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
goliath has joined #yocto
neofutur_ has quit [Ping timeout: 245 seconds]
neofutur has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.1.2]
JerryM has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Average_Joe has joined #yocto
<Average_Joe>
hello world
<alperak>
cve check reporting "Found unpatched CVE" but it already fixed in upstream. what should i do to solve this warning? should i do something like
<alperak>
CVE_STATUS[CVE-xxxx-xxxx] = "fixed-version: The CPE in the NVD database doesn't reflect correctly the vulnerable versions."
sakman has joined #yocto
<mcfrisk>
alperak: contact NVD to fix the version range https://nvd.nist.gov/info/contact-form and if the fix doesn't get applied in a week or two then submit the CVE_STATUS patch to upstream meta layer. Note that the CVE_STATUS applies to the current recipe version, so comment should tell why this version of recipe is not affected. Patch being applied upstream is different thing.
<alperak>
mcfrisk thanks a lot
linfax has quit [Ping timeout: 264 seconds]
MarioMariollini has quit [Ping timeout: 250 seconds]
samkent has quit [Remote host closed the connection]
vladest has quit [Ping timeout: 268 seconds]
simonew has joined #yocto
Average_Joe has quit [Quit: Leaving]
<rburton>
alperak: mail cpe_dictionary@nist.gov, tell them the CVE and make your case. basically point them at the patches and what version they're in (github makes this convenient as it shows the tags a commit is in). They'll fix the version info in the database.
<rburton>
alperak: feel free to mail me what you'll be sending if you'd like me to check, i must have sent quite a few by now.
vladest has joined #yocto
MarioMariollini has joined #yocto
olani- has joined #yocto
<alperak>
rburton you're always here to help. THANKS!
<Xogium>
so, I've had an idea for my setup here, and I'm wondering if something like this would make sense or not. Say I have a production system deployed that will only ever get updated via rauc, to keep things minimal. Would it make sense to for example create a development version of this system where one can actually install packages to test things more easily than they could be tried on a system that is mostly
<Xogium>
immutable and using rauc to get upgraded ?
Guest4041 has quit [Ping timeout: 246 seconds]
ctraven has joined #yocto
Estrella has joined #yocto
<rburton>
zeddii: did you break meta-virt? 2024-01-04 14:30:54 - opkg_prepare_url_for_install: Couldn't find anything to satisfy 'kernel-module-xen-blkback'.
<zeddii>
are you building the 6.6 kernel ? if so you need the very recent .inc update I pushed.
<zeddii>
and I deleted the 6.5, in antipation of it going from oe-core
<zeddii>
so it is more likely that.
<zeddii>
I'm forcing everyone off the EOL as my new year's gift
<rburton>
just trying to build master of everything and it blows up
<rburton>
so yeah, arguably that deletion was a bit eager? :)
* zeddii
is holding the line :)
neofutur_ has quit [Ping timeout: 264 seconds]
<zeddii>
because if i don't, I'll get the mad scramble of patches send that inform me of a kernel change that I sent to oe-core.
<zeddii>
since i never know exactly when things do land.
JerryM has quit [Quit: Konversation terminated!]
<RP>
zeddii: you know by the flood of email? :)
neofutur has joined #yocto
paulg has joined #yocto
<zeddii>
that's usually my trick! so I decided to get the flood of email up front!
<zeddii>
but in reality, it's just a tiny bit of coordination. I'm exagerrating. I can always revert my removal. I had just prepped them both to go in at the same time and pushed it.
jmiehe has joined #yocto
<RP>
zeddii: I'm hoping we can get the kernel in soon, I just need a successful test build
Vonter has quit [Ping timeout: 245 seconds]
<zeddii>
Agreed. That's definitely a requirement!! I'll fix my ambitious removal if we run into more issues
Vonter has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
<RP>
zeddii: on the plus side, meta-virt didn't fail in my test build :)
zpfvo has joined #yocto
skokkonda has quit [Quit: Client closed]
zpfvo has quit [Ping timeout: 260 seconds]
zpfvo has joined #yocto
<zeddii>
it is seeing the future!
jmiehe has quit [Quit: jmiehe]
<fray>
join #yp-tsc
<fray>
oops
alperak has quit [Quit: Client closed]
zpfvo has quit [Remote host closed the connection]
leon-anavi has quit [Quit: Leaving]
chep has quit [Ping timeout: 256 seconds]
neofutur has quit [Ping timeout: 252 seconds]
neofutur1 has joined #yocto
paulg_ has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
florian_kc has joined #yocto
kpo_ has joined #yocto
kpo_ has quit [Ping timeout: 276 seconds]
alessioigor has quit [Quit: alessioigor]
jmd has joined #yocto
alessioigor has joined #yocto
DrChandra has joined #yocto
alperak has joined #yocto
florian_kc has quit [Ping timeout: 255 seconds]
paulg_ has quit [Remote host closed the connection]
paulg has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
florian has quit [Killed (NickServ (GHOST command used by florian_kc!~florian@dynamic-078-048-139-098.78.48.pool.telefonica.de))]
florian_kc is now known as florian
florian_kc has joined #yocto
jmiehe has quit [Quit: jmiehe]
prabhakarlad has quit [Quit: Client closed]
chep has joined #yocto
Guest88 has joined #yocto
<Guest88>
Hi
<Guest88>
Is there raspberry pi (5) support yet in the meta-raspberrpi layer? I noticed a few commits have been made recently. I just don't see it yet on any of the branches is why I ask. Maybe i'm looking in the wrong place?
<RP>
zeddii: the master-next kernel build was green. Clearly the autobuilder broke ;-)
<zeddii>
😂
<RP>
zeddii: 6.6 is in :)
<zeddii>
The next thing up will probably be strange intermittent issues, but we have some runway to find and fix those
<RP>
zeddii: right,we're not going to get anywhere with it sitting on a branch beyond here though
<RP>
zeddii: but upstream always just merges fixes so it will be fine ;-)
<zeddii>
Agreed. And now I can check with Kevin and get the references updated and we can drop 6.1. which means we are basically set for release kernels. I'll just do -dev for newer ones (unless a compelling reason shows up for a versioned recipe).
<zeddii>
Right. 6.6 has been out and is perfect! ;)