The sixty-second edition of my weekly collection of news about #LinuxPhones (@PINE64 #PinePhone, @purism #Librem5 and such), #LinBits, is out!

#MMS support landing in #Manjaro, #libhandy 1.4.0, #NemoMobile needs translators and more!

@linmob @PINE64 @purism

That is my branch of Chatty by the looks of it. While they are welcome to package and ship it (It is free software after all!), I just caution that MMS support in Chatty is very much experimental, and many things do not work yet.

I just I don't want folks to be disappointed when things do not work as expected.


@kop316 @linmob @PINE64 @purism Manjaro does that often without making this explicit, and we then get plenty of invalid bug reports upstream :( There's usually a good reason why stuff that isn't merged yet isn't merged yet. It's fine to have a distro that includes experimental stuff around for those bravest, but I'd like to see Manjaro clearly state which things they pull in are still unfinished so users are well aware of what to expect.

@dos @kop316 @linmob @PINE64 @purism oof, yeah... that's scary that users aren't alerted to the fact that they are receiving patches that are still in review/WIP, especially since folks are trying to "daily drive" this stuff.

@dos @kop316 @linmob @PINE64 @purism They do the same with some stuff developed by postmarketOS devs and then our devs get invalid bug reports as well. It's fine doing it in dev builds where they ship all kinds of nightly stuff, but it really shouldn't happen in "stable" builds without explicitly warning the user about it.

@bart @dos @kop316 @PINE64 @purism With regard to this MMS feature, it's only in Manjaro Phosh dev (I thought about making this more clear in my headline, but didn't). Maybe, to avoid invalid bugreports, they could put in a First Run note (like a simple webview) that links the repos they are using so that bugs get reported there (and then get cherrypicked for upstream if that's where they belong)?

@linmob @bart @dos @PINE64 @purism

I guess that's their beta branch?

My point is more, I don't want folks thinking its a complete feature set, as it is not. They are welcome to package whatever they like!

@dos @kop316 @linmob @PINE64 @purism Ugh, we're dealing with a broken AUR package for Tenacity whose maintainer has ignored our build instructions upstream and shipping a totally broken package.

@dos @kop316 @linmob @PINE64 @purism Despite that we've explicitly said to *not* package before we make a release.

@be @dos @kop316 @linmob @PINE64 @purism I feel like this is a good reason to relabel your master branch 'development' and say if the build I not from a release branch it's not supported.

@dean @dos @kop316 @linmob @PINE64 @purism I disagree. master/main = development. That's normally how it works. There has never been a release. Packaging software that has never been released is irresponsible IMO.

@dean @be @dos @linmob @PINE64 @purism

Ummm....the branch being used is actually called "wip/mms_settings". It isn't in my main branch as I haven't finished working on it.

They are welcome to use what they want ,like I said, this is free software! I just think folks will be disappointed when they realized that MMS support isn't complete.

@be @dos @kop316 @PINE64 @purism Honestly, I don't see AUR PKGBUILDs as "packaging". They are a recipy to install something to try it out with no warranties and hopefully with a way to cleanly uninstall it, if it doesn't work out. This is especially the case for "-git" packages. Users that expect those to work obviously don't know what they're doing – "-git" packages are like hitting "I'm feeling lucky" on Google: Sometimes it works, often it doesn't.

@linmob @dos @kop316 @PINE64 @purism Whatever you say it is doesn't really matter. What matters is that upstream keeps getting annoying bug reports for a broken package we have no control over and the package maintainer has made no effort to fix nor work with us.

@be @dos @kop316 @linmob @PINE64 @purism well the AUR isn't exactly a benchmark is it?

Literally anyone can throw things at it, whether they are qualified for doing so or not.

The general package quality varies a lot, from outright broken to perfect, usually nearer to the former than the latter
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml