A core aspect of open source is that if someone claims that “it’s not hard to fix” then the response can be … “patches welcome”.
However if it were me trying to submit a patch to Purism, I would make sure that I am running current software first. I don’t want to waste my time fixing a problem upstream from byzantium if the problem has already been fixed upstream from crimson.
At the same time, there is no way that I would be asking you to reflash to crimson. For example, there “may” be functionality that works in byzantium but is not yet working in crimson - so this might not be a great option for you right now anyway.
The best customers to be submitting patches to Purism would be customers who have two phones - one for daily driving with stable software (byzantium) and one for “crash and burn” with bleeding edge software (crimson).
Oooooh Nope. I wouldn’t go so far as to provide the patch, a coded bleh! Through a variety of trial and error, I found the probable causes. The PureOS Store was tweaked and missed the target.
I can’t fix it because I do not have the Admin access, don’t want it either, and I’ve already posted what the problem is and that it can be fixed (IMO). The link on the Dtop needs to be redirect to the same landing page as softare.pureos.net. ↴
I think people that read this take in to account my obvious lack of Linus skills and the complexity of my presentation and put no faith in it.
Crimson will be a long time coming before it’s ready for beta testing (AKA release). And a longer time And as such, for some older people, myself too, I’d like to see something working without wondering what/who will outlast the other. The person responsible for coding the links should take a look. Let’s get Byzantium working before fixing it with Crimson.
~s~
