- PureOS-project - Purism Mailing Lists

PureOS Crimson Development Report: November 2024
by praveen＠onenetbeyond.org 16 Dec '24

16 Dec '24

Now published at https://puri.sm/posts/pureos-crimson-development-report-november-2024/

1 0

The "dawn" suite (PureOS 12) is open and development target
by Matthias Klumpp 09 May '24

09 May '24

Hi! Today I switched the PureOS development target from crimson to dawn, which will eventually become PureOS 12. That does *not* mean PureOS 11 (Crimson) is released yet, though it does mean that both versions are developed in parallel. All uploads to the crimson suite will be redirected to crimson-p-u, while any uploads to dawn will end up in landing. The normal migration procedures for packages are followed as usual. Happy hacking! Matthias

1 0

Vote for the PureOS 12 codename!
by Matthias Klumpp 12 Oct '23

12 Oct '23

Hi! I should have created this survey a while ago, but better late than never: We need to decide on a codename for PureOS 12! This will be the next in-development version of PureOS after crimson, and while its release is still way into the future, it is still advantageous to have its codename ready. For a while, we have been collecting color names that start with "d" as potential PureOS 12 names, and I have now created a surves out of them. It should be super quick to vote, just use this link: https://matk.limesurvey.net/571644 The survey will run for at least 5 days, and if the result is close, we will do a second round of votes between the top-3 names. Otherwise, whatever gets the most amount of votes wins. Happy voting! Matthias

1 2

PureOS 11 (Crimson) open for development!
by Matthias Klumpp 16 Jun '23

16 Jun '23

Hello! The initial synchronization with Debian has finished, and `crimson` is now open for development! Consequently, packages from `landing` are migrating to the `crimson` suite now. You can upload packages for crimson by simply targeting "crimson" in your debian/changelog and upload them to the usual place. Please check your dput.cf file for the right configuration, as with the switch to the latest Laniakea version we no longer accept FTP uploads but only uploads via HTTPS instead (which has many security benefits). Currently, both landing and crimson are still very much broken in terms of package installability, but we will be working on resolving these kinds of issues in the next days and weeks. You can find a list of packages that need to be merged with Debian at: https://master.pureos.net/sync/7/issues A list of current issues in the landing suite can be found here: https://master.pureos.net/depcheck/pureos/landing/binary/amd64/1 Cheers, Matthias

1 0

PureOS 11 open for development on 12.06., landing receiving crimson packages
by Matthias Klumpp 08 Jun '23

08 Jun '23

Hello! This is a short reminder that with the Laniakea migration completed, we will be opening PureOS 11 (crimson) for development on 12.June (next Monday). This also means that from that point on, the landing suite of PureOS will receive packages from Debian again, and will be the development testing ground for crimson. In addition to that, migration delays from landing to crimson will be reduced to two days or less. Furthermore, we will deprecate PureOS 9 (amber) soon, but details for that will be made public later. In any case, if you haven't upgraded yet, upgrading to PureOS 10 is highly recommended. Thank you & happy hacking! Matthias Klumpp

1 0

Laniakea Upgrade on Repo/Master Server Imminent
by Matthias Klumpp 02 Jun '23

02 Jun '23

Hello! In order to greatly modernize our infrastructure, we will be upgrading to a newer version of Laniakea[1], the tool that manages the PureOS archive. Previous versions of Laniakea were based on dak, the Debian Archive Kit. This caused numerous inefficiencies and was a lot harder to maintain compared to the new solution, where Laniakea has integrated all archive management capabilities. Upgrading will also allow us to iterate on PureOS a lot faster. The new system has been tested for a while on a scratch instance and has been running well, so we might switch in the following days on our production instance. This weekend I will be running some tests and kick off the migration in case no issues are found (and otherwise revert and try again a week later). During the upgrade time, software.pureos.net, master.pureos.net and the upload service will not be available. After the upgrade, you will need to adjust your dput.cf file to upload to the new location, since we will be decommissioning FTP uploads as well (and make our security people very happy in the process). There are a few known issues with the new Laniakea version: * Laniakea implements the Debian Archive / APT repositories based on the modern layout specification. Unfortunately we found out far too late that debootstrap did not support the modern layout yet, so in order to bootstrap PureOS, you will need to get our patched debootstrap version: https://repo.pureos.net/pureos/pool/main/d/debootstrap/ Alternatively you can also use mmdebstrap. APT itself and all other tools can already understand the "new" archive layout for multiple Debian releases. * Changelog files on the metadata server will initially not be available until support for this feature is restored in Laniakea. * In the first days post-migration there might be issues with receiving e-mails from the archive server - we will resolve those as soon as possible. The Matrix bot will not be affected. This update is extremely large and potentially very disruptive, so please keep an eye out for any unusual issues and let me know about them. Cheers, Matthias [1]: https://github.com/lkhq/laniakea

1 0

Stuff done March 2022
by Carsten Schoenert 09 Apr '22

09 Apr '22

Hi, some information about packaging and other work I've done last month within PureOS. After a break in February I've been able to do again various packaging stuff for PureOS. * gnome-boxes I've looked at the version delta between Debian and PureOS in gnome-boxes. Due as usual great and useful help from Guido while looking into the stuff under the hood it turns out the PureOS specific patching isn't needed any longer as users in Debian bullseye (and by this also users of PureOS byzantium) are now a member of the group kvm by default and can access /dev/kvm without extra actions. Matthias dropped the old PureOS package of gnome-boxes and synced the version from Debian stable. Thanks to Chris who has prepared and maintained the old patch for gnome-boxes! https://source.puri.sm/pureos/packages/gnome-boxes/-/merge_requests/1 * initramfs-tools An update/sync for this packages was requested by Sebastian as the old version in PureOS was blocking other packages. While updating the underlying source I've updated also the used branch name and metadata to get this in sync to the common standard in PureOS. https://source.puri.sm/pureos/core/initramfs-tools/-/merge_requests/1 https://source.puri.sm/pureos/core/initramfs-tools/-/issues/2 * gdm3 The Gnome Display Manager got a CVE related update in Debian and I've synced the latest version from Debian stable into byzantium. Currently the update of the Jenkins CI for this package is awaiting approval. https://source.puri.sm/pureos/packages/gdm/-/merge_requests/1 https://source.puri.sm/Librem5/deb-build-jobs/-/merge_requests/406 Like in the past months I've also done some more smallish things probably not really worth to mention. Package maintenance work in Debian I've done also some maintenance task within Debian and worked on the following packages (so far I remember). 1 django-simple-captcha 2 drf-yasg-nonfree 3 kicad* 4 libpam-radius-auth 5 mssql-django 6 ponyprog 7 pydoctor 8 pygments 9 python-cmarkgfm 10 python-django-analytical 11 python-django-modelcluster 12 python-lunr 13 python-mkdocs 14 python-readme-renderer 15 svgwrite 16 systemc 17 thunderbird 18 wcag-contrast-ratio -- Regards Carsten Schoenert

1 0

DEP14 branch naming for backported security updates from Debian in PureOS
by Carsten Schoenert 06 Apr '22

06 Apr '22

Hi, I've looked into the Synchronization issue list in landing and noticed that util-linux, which has PureOS specific modifications, has got a security update in Debian bullseye by version 2.36.1-8+deb11u1. PureOS has currently version 2.36.1-8pureos3. Backporting this security update isn't that difficult. But while working on this I came to the point to commit the modifications. :-) But I feel the branch pureos/latest wouldn't be the correct branch as latest implies that the data is quite the most recent stuff. Yeah, we are talking about landing which follows bullseye, but looking a bit further there a lot of backported versions for PureOS are put into $latest or into pureos/byzantium (correctly in my eyes) within the L5 world I'm thinking putting such security backporting work within packages that have PureOS specific modifications should be done also within a branch pureos/byzantium called. Before doing more work in that corner it would be good to have some consensus about that topic. :-) What do others thinks? Maybe I've overseen some already similar revised packages. -- Regards Carsten Schoenert

3 3

Stuff done January 2022
by Carsten Schoenert 08 Feb '22

08 Feb '22

Hi, some information about packaging and other work I've done last month within PureOS. Due some time constraints grounded on lots of stuff I needed to do at my usual day job I wasn't able to do all the things I'd liked to have done within PureOS. But well, at least some things I was getting done. :) * gnome-clocks Reviewed and later merge in of MR15 and MR16 from Steve, prepared a new version 40.0-2pureos1. Further email discussions with Steve about other adjustments for gnome-clocks. https://source.puri.sm/Librem5/debs/gnome-clocks/-/merge_requests/15 https://source.puri.sm/Librem5/debs/gnome-clocks/-/merge_requests/16 * choose-mirror Tagged version 2.111pureos1 and pushed afterwards to GitLab. * util-linux Tagged version 2.36.1-8pureos3 and pushed afterwards to GitLab. * gnome-initial-setup Merge in MR4, pulling in latest Debian stable version, updating and preparing PureOS packaging, start a new MR5 which will need so more testing which I wasn't able to do so far until now. https://source.puri.sm/pureos/core/gnome-initial-setup/-/merge_requests/4 https://source.puri.sm/pureos/core/gnome-initial-setup/-/merge_requests/5 * librem5-dev-tools Give some more feedback to the still open MR20 from me, unfortunately I still impossible to get this completely ready. https://source.puri.sm/Librem5/librem5-dev-tools/-/merge_requests/20 * gnome-desktop Merge in MR1, further updating PureOS specific packaging resulting in an new MR2 for getting a new version 3.38.5-3pureos1. It's the same as for gnome-initial-setup, needs at least some testing before do some merge and further finalizing packaging. https://source.puri.sm/pureos/packages/gnome-desktop/-/merge_requests/1 https://source.puri.sm/pureos/packages/gnome-desktop/-/merge_requests/2 Again also some more smallish things probably not really worth to mention. Besides this I've done also some Debian packaging work, so far I've did hade made some notes to myself I've uploaded new versions for the following packages to NEW, unstable, stable-security and some backports queues. 1 django-cors-headers 2 django-graphene 3 django-graphiql-debug-toolbar 4 django-taggit 5 drf-yasg-nonfre 6 graphql-core 7 graphql-relay 8 kicad* 9 libvime 10 mssql-django 11 ngspice 12 pydoctor 13 python-django-modelcluster 14 python-graphene 15 python-ilorest 16 python-tablib 17 social-auth-core 18 thunderbird 19 wcag-contrast-ratio -- Regards Carsten Schoenert

1 0

Stuff done December 2021
by Carsten Schoenert 09 Jan '22

09 Jan '22

Hi, I'm not a full time contributor to Purism so writing my actions and doings per week makes not that much sense, so I'll try to give an overview of my activities once per month. So let's start with a summery of my doings for December 2021. * mobile-broadband-provider-info I've look at MR4 and prepared an new version 20210805-1pureos1. https://source.puri.sm/Librem5/debs/mobile-broadband-provider-info/-/merge_… * choose-mirror Looked at the differences between Debian bullseye and PureOS byzantium, merged in the version 2.111 from Debian and prepared a new version PureOS as MR to review. https://source.puri.sm/pureos/core/choose-mirror/-/merge_requests/2 * util-linux Mostly the same as for choose-mirror, resulting in another MR for review. https://source.puri.sm/pureos/core/util-linux/-/merge_requests/2 * gnome-clocks Discussing a MR from a contributor, moved over to a conversion by email with the author of the MR to explain a gbp based update process (not only) for this the package. https://source.puri.sm/Librem5/debs/gnome-clocks/-/merge_requests/14 * seahorse Prepared another update to the package. https://source.puri.sm/pureos/packages/seahorse/-/merge_requests/4 * librem5-dev-tools Reworked the current patch for the script check-pureos-pkg-repo after some feedback within the MR, not yet finished nor pushed as this has less priority for me right now. https://source.puri.sm/Librem5/librem5-dev-tools/-/merge_requests/20 * vvmd and vvmplayer Prepared a backport for both packages. Awaiting inclusion into automatic deb build jobs. https://source.puri.sm/pureos/packages/vvmd https://source.puri.sm/pureos/packages/vvmplayer https://source.puri.sm/Librem5/deb-build-jobs/-/merge_requests/391 * kodi Start looking at differences between Debian and PureOS And some more small things probably not really worth to mention. -- Regards Carsten Schoenert

2 1

2025

2024

2023

2022

2021

2020

2019

2018

PureOS-project