Morning @carsten.schoenert I was told that this ticket should be brought to your attention.
Unbreak Now! (4)
Needs Triage (5)
Freedom Issue (6)
Mon, Sep 20
Tue, Sep 14
Mon, Sep 13
I can handle this low priority for the moment, i found ways to build geary for the moment but i expect this issue to become more urgent during the byznatium cycle again (if not for geary then for other packages using vala). Issue here is that this will likely involve a glib upgrade as well.
Sat, Sep 11
What would be the preferred way to get this done?
Fri, Sep 10
Wed, Sep 8
We could probably have debug symbols packages for our self-built packages with a bit more space (the dbgsym packages are *insanely* huge, they dwarf the size of the actual archive), but for the full archive, so syncing the debug symbols from Debian to make them available easily in PureOS, we'd need quite a lot of space (I need to look at Debian to actually give a - then very good - estimate).
At time, PureOS holds dbgsym packages for everything that we have built in the landing suite, but byzantium doesn't have own debug symbols. You can however use the ones from landing, which are either equal to the versions in byzantium, or newer.
This is probably a duplicate of https://tracker.pureos.net/T873 (see last comment by Guido).
Tue, Sep 7
Fri, Sep 3
The name "Hephaestus" is going to be deprecated in favor of just the version number, e.g. PureOS 9 Amber, Pureos 10 Byzantium, etc.
I am not intimately familiar with the ISO building process, but suspect that this is harmless, caused by post-processing of the ISO file to support UEFI or something similar.
A second user confirmed the first report.
Wed, Sep 1
Wed, Aug 25
Aug 20 2021
Sorry, this is not a helpdesk.
In my understanding, the builtin default values are nowadays sensible for general use.