<yocton>
Guest5: They announced instability for around a week starting today if I remember correctly
<svuorela>
Guest5: what info are you looking for?
<svuorela>
they a month ago announced downtime from yesterday until saturday
davidinux has joined #yocto
mathieudb has joined #yocto
mathieudb has quit [Changing host]
mathieudb has joined #yocto
<rburton>
Guest5: that link literally has a breakdown of the tasks and status, not sure what else we could add!
<rburton>
hopefully our source mirrors have everything important...
enok71 has joined #yocto
enok has quit [Ping timeout: 260 seconds]
enok71 has quit [Ping timeout: 248 seconds]
mbulut_ has joined #yocto
<kilobyte_ch>
I have Matchbox as WM. My backlight (/sys/class/backlight/rpi_backlight/bl_power) returns 4. This means POWERDOWN. Any idea how to get this working? Do I need to change something in mini-x-session?
<kilobyte_ch>
When changing bl_power to 0, the backlight starts to work.
frieder has quit [Ping timeout: 244 seconds]
<rburton>
RP: do you think that license files that are used by _one_ recipe because it has the recipe name embedded in should be in common-licenses, or we should use NO_GENERIC_LICENSE more liberally and put it alongside the recipe?
<rburton>
(looking at the docbook-xml v4 recipe which has bespoke license that isn't spdx)
frieder has joined #yocto
enok has joined #yocto
<RP>
rburton: I think we should be migrating common-licenses to be two sets, our own and SPDX
<RP>
rburton: and using no generic license more would probably make sense
<RP>
rburton: I did ignore a couple of custom refs :/
<rburton>
fecking gpl3
<rburton>
your LICENSE doesn't say gpl3 but the readme says "The command line tool, self tests, examples, and other auxiliaryfiles, are licensed under the GNU General Public License version 3.0
<rburton>
or later - see the file [COPYING](COPYING)."
<RP>
rburton: idn?
<rburton>
oh yeah sorry
<rburton>
why is there an idn commit in the xkbcommon changelog :)
<rburton>
qschulz: look stop being pedantic exactly like i am when i review patches, it hurts
savolla has quit [Quit: WeeChat 4.4.3]
<qschulz>
rburton: :upside_down:
<qschulz>
rburton: i'm more "concerned" about the license change
<qschulz>
Yocto isn't that pedantic about commit splitting, especially for recipes, so up to you :)
<qschulz>
not sure if that was proper English but you got the gist I assume
<rburton>
yeah i was torn on splitting the packaging up so the pam module was in a separate package
<qschulz>
I would assume the libcap cleanup could be backportable
<qschulz>
especially the license part
<qschulz>
but splitting into different packages, that is a bit harder for current releases
<qschulz>
(simply an addition RDEPENDS but still...)
<qschulz>
additional*
goliath has joined #yocto
frieder has quit [Remote host closed the connection]
ptsneves has quit [Ping timeout: 252 seconds]
sappy has joined #yocto
sappy has quit [Client Quit]
sappy has joined #yocto
<sappy>
Is it always the case that if there's a layer with higher priority having a recipe with lower PV, then the lower version will be picked up in the build? Obviously, no preferred version is mentioned.
<JaMa>
sappy: yes
<sappy>
Thanks
enok has joined #yocto
sappy has quit [Read error: Connection reset by peer]
Guest5 has quit [Quit: Client closed]
rfuentess has quit [Remote host closed the connection]
rudynotfound has joined #yocto
sappy has joined #yocto
sappy has quit [Client Quit]
rudynotfound has quit [Quit: Client closed]
<rburton>
qschulz: sent a v2 :)
mckoan is now known as mckoan|away
<rburton>
argh forgot the license updated tag AGAIN
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
leon-anavi has quit [Quit: Leaving]
mathieudb has quit [Quit: leaving]
mathieud1 has joined #yocto
mathieud1 is now known as mathieudb
mathieudb has quit [Changing host]
mathieudb has joined #yocto
vthor_ has quit [Excess Flood]
vthor_ has joined #yocto
mbulut_ has joined #yocto
tgamblin has quit [Remote host closed the connection]
enok has quit [Quit: enok]
tgamblin has joined #yocto
enok has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
mbulut_ has quit [Ping timeout: 245 seconds]
enok has quit [Ping timeout: 252 seconds]
khem has quit [Quit: WeeChat 4.5.2]
alcroito has joined #yocto
<alcroito>
Hi. I have a yocto-related spdx sbom question. Afaik yocto generates spdx 3.x documents, in contrast to 2.3 that many other projects generate. Is there any commercial or opensource tooling that is able to consume 3.1 documents yet? I'm wondering what's the use case for 3.x documents, aside from manual inspection.
enok has joined #yocto
<rburton>
alcroito: if you _need_ 2.x then you can switch the class to 2. there is a lack of tooling for 3 at the moment yes
<rburton>
3 documents are standard, the 2 documents are non-standard in various ways
<alcroito>
i don't need 2.x. I'm asking because i'm working on another project that currently generates 2.x docs, and wondering if there's any sensible way to consume 3.x ones. Yocto is one of the only open source projects that i know generates 3.x, so that's why i thought to ask here
<rburton>
that would be because the person who wrote our spdx code was also contributing to the 3 specification :)
druppy has joined #yocto
<rburton>
i wouldn't be surprised if we were the first thing to produce 3.x documents for that reason to be honest
<alcroito>
ok, so could that be interpreted as a "yocto is ready for 3.x, but there is no reason yet to use it'
<rburton>
well if you don't need them then there's no reason to use either, right? but if you want to archive a sbom then a the spdx3 document will actually be fully compliant and cover everything. our spdx2 files tend to break tooling...
<rburton>
something about they don't expect several hundred megs of interlinking spdx2
enok has quit [Ping timeout: 248 seconds]
<alcroito>
well i might want to need them, if i found out there is tooling that can actually consume it, and gives some value out of it (vuln scanners, validators, etc) :)
enok has joined #yocto
<alcroito>
yes, i can imagine the issue with the big interlinking case
<JPEW>
alcroito: The biggest hurdle to getting SPDX 3 more widely adopted ATM is that most of the "common" tools are all web based go code, and the go binding still need some work (I've done all the binding work so far, but I'm not a go person)