I was intructed on the pureos-project mailinglist that if the latest package in Debian is a clean backport and I haven't seen any regressions, then the simplest solution is to simply backport that from unstable to byzantium.

I am working on getting this into Debian - There's already a Ubuntu PPA, whos maintainer I have mailed and asked if they are interested in maintaining it in Debian - If they are not, I'll ITP it, and maintain it myself.

I am just about to package 1.2.13 in Debian, which got a fix for

@user22492 Is this with the PureOS package?

@jeremiah.foster I have now pushed another commit to salsa, containing a man-page. I'll provide it to upstream in a pull request too.

@jeremiah.foster I'll take care of it.

And there you have it:

I have made an upload - I will push the git repo to the Debian Python Applications Packaging team on salsa when I can see that it is in the NEW queue.

Hmm, now I found https://puri.sm/posts/music-player-lollypop-added-to-pureos-store-for-librem-5-phone-and-laptops/ .
It isn't already packaged, right?

I have started looking at packaging this - I can provide a packaging repo containing my work soon. I guess packaging in Debian is the preferred way, and not in pureos. I'll take ownership of that RFP.

Which version of Gnucash are you trying to build? libgoffice-0.8 is removed from Debian testing (which PureOS is based on), but there is a newer version of Gnucash (2.7.3) in the Debian Experimental repositories, which require libgoffice-0.10.

I have update the page, ended up with this:

I am a member of the debian-www team, and have write access to those pages. What text would you like to present PureOS?