[Slackbuilds-users] Call for Help

[Willy Sudiarto Raharjo]

>> what is the significance of the "raw" lists as opposed to "WIP: 
>> Overview"?
>>
>> I see graphics/Blender in "raw list i585" but it builds fine here in a
>> clean up to date VM.
>>
> 
> Sorry, it wasn't quite clean - earlier 32bit patch is not needed and I'd 
> already removed it so build succeeded.
> 
> The question still is about difference between raw lists and WIP overview.

The RAW list are those who hasn't been triaged, so it's just a list of 
failing scripts, without being inspected further.
They could be false alarm as mentioned on my original email.

There are also some occasion where the CI can't properly test the script 
because of some special requirements, such as installing packages from 
slackware's extra (ispc need newer llvm) or can't be installed on a 
container (qt6ctl can't properly detect qt6 due to conditional situation 
in the code). There's no hint available for such cases, so manual 
inspection need to be done (i approved ispc after testing them manually 
on a clean VM outside github CI engine)

Maybe Andrew can give more detail explanation about this


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240426/4ec63e09/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240426/4ec63e09/attachment-0001.asc>