Tonight's π² FAIRPHONE 6οΈβ£ update brings the same simplification to bootloader unlocking that the FP3 received in March: No more unlocking code needed (OEM unlocking in developer options and unlocking via ADB and Fastboot are still required). Apart from that, the update promises a couple of fixes as well, e.g. for the curse of mysteriously disappearing photos just taken. /u
https://forum.fairphone.com/t/software-update-fp6-qrel-16-69-0-20260430160633/131953?u=wearefairphone
Unlocking codes will no longer be necessary for FAIRPHONE 4οΈβ£ bootloader unlocking either. After tonight's π² FP4 UPDATE, only the FP5 will still need a code β let's see if the next FP5 update completes the elimination. /u
"pmbootstrap will now perform strict builds of packages by default, which was previously opt-in behavior enabled either by invoking it with the --strict flag or by setting pmb:strict in the APKBUILD for a package. The change for this was merged to pmbootstrap's main branch today and will be shipping in the next minor release, probably 3.11.0."
Thanks to @aelin for implementing this and writing the devel blog post!
https://postmarketos.org/devel/2026/06/01/pmbootstrap-strict-builds/
If you have a CoC but don't apply it to your own longtime members/contributors, you don't have a CoC.
ποΈ Next talk at #EmbeddedRecipes2026!
Laurent Pinchart takes the stage with a panoramic talk: "Linux and cameras: past, present and future".
#EmbeddedRecipes2026 #EmbeddedLinux #Camera #ISP #LibCamera #V4L2 #OpenSource #EmbeddedSystems
Embedded Recipes: Tomeu Vizoso presenting "Four NPUs, One Stack, Zero Blobs: Edge AI Acceleration in Mainline", with a look at ongoing work on the #RK3576.
@pabloyoyoista from postmarketOS is now talking about the distributed phone CI that is being worked on for postmarketOS!
#EmbeddedRecipes2026 #postmarketOS #MobileLinux #LinuxMobile
A security vulnerability labelled CVE-2026-27771 affecting Forgejo and Gitea is being widely reported recently.
Packages in Forgejo are visible to unauthenticated users if they are published under a public owner, as designed. It is not a security vulnerability, but a misunderstanding about the permissions and a good opportunity for users to review that they are not in a misconfigured state.
Please see the statement issued by the security team here for more details: https://codeberg.org/forgejo/website/issues/839#issuecomment-15980039