@dos If you want the best place in the house (or garden) you've got to move the cat.
We are proud that mobian developer kop316 has now gone for a real fork of the unmaintained mmsd and will be trying to get it into Debian. Also @purism will be using his code on the Librem5. It goes both ways! This will hopefully become the basis for The Next Generation of mmsd:
https://gitlab.com/kop316/mmsd
Receiving MMS messages on the #librem5 is getting closer to working by default. In #PureOS byzantium the needed #libqmi and #ModemManager fixes are already there now, we just need to add #mmsd and purple-mm-sms manually: https://source.puri.sm/Librem5/chatty/-/issues/30#note_157487 Thanks to Chris T and @craftyguy #GNU #Linux #chatty #freesoftware @purism
Building on top of https://social.librem.one/@agx/106165637941088397 and about 80 commits later we passed the magic 50% test coverage hurdle (meaning we test about half of #phosh automatically which each commit).
@goatwildernesscollective @brainblasted Such requests should go to https://gitlab.gnome.org/GNOME/gnome-logs
To ease debugging issues on the road i made #gnome-logs shrink to smaller screen sizes. This is based on @brainblasted 's work to make #gnome-logs use #libhandy initially.
@bart "new feature" is at least as subjective as "larger changes" (one persons bug fix is another persons feature ↔️ ). Somebody depending on #phosh for every day use wants to know: "is this update safe" and for that it matters how invasive changes are since that' has a greater chance of affecting stability negatively 💥.
So on a middle version bump you want to be more cautious/test more than on a minor version bump before pushing things out to users. That matters more to me than 'new feat'.
@bart Larger changes (usually introducing new features) bump the middle number while mostly bugfix releases bump the last version.
@mobian @purism its #phosh 0.10.2 (we're not at verson 10 just yet). For PrntScrn you need https://source.puri.sm/Librem5/phoc/-/merge_requests/249 .
#phosh 0.10.2 is out 🚀 : https://source.puri.sm/Librem5/phosh/-/releases/v0.10.2
This is another (stability and ui) bugfix release. It also updates several translations and adds initial built-in screenshot support.
See above release notes for the full list of changes and contributors.
A tutorial on creating stable backports packages for debian.
https://peertube.debian.social/videos/watch/82befec2-04f6-4369-8955-3b28a843fc6b
And new volunteers to help maintain gitlab dependencies in backports welcome (gitlab itself is in https://fasttrack.debian.net).
I've tagged another git snapshot of #feedbackd with a bunch of fixes.
Here's the list of changes: https://source.puri.sm/Librem5/feedbackd/-/releases/v0.0.0%252Bgit20210426
#feedbackd is used by #phosh, #calls and others to provide haptic, audio and led feedback.
For what it's worth, here's a likely very incomplete THANKS file:
https://gitlab.gnome.org/GNOME/geary/-/blob/mainline/THANKS
Geary is Free Software, being built by people, for people. ✌️ ❤️ 💻
@merge summarized @purism's 5.12 #linux kernel work: https://puri.sm/posts/purism-and-linux-5-12/ which includes the #devkit now booting mainline : https://social.librem.one/@agx/105542421589465994
@eliasr @joao @martijnbraam yes, it's a fork of upstream megapixels with hacked in support for the API the current CSI drivers export to userspace (which is currently being reworked): https://source.puri.sm/dorota.czaplejewicz/megapixels/-/commits/master
The software engineering research community has a problem with (lack of) ethic approval culture when experimenting on free/open source software developers.
#megapixels running on a #purism #Librem5. Credits go to the devs who have been working on enabling the cameras on the #librem5
Geary 40 release candidate has been released, at long last! It is available to install as a nightly build for testing before the final release: https://wiki.gnome.org/Apps/Geary/GetIt
Please do test it out, and let us know if you find any show stoppers: https://wiki.gnome.org/Apps/Geary/ReportingABug
Thanks!