Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this page for instructions on how to get full permissions. Sorry for the inconvenience.
This version is adaptive, has end to end encryption and voice calls. Given the experimental matrix support is nowhere near usable state, this will make the default experience much better.
I'm not a nheko user and don't have the bw to maintain this so I'll ping @carsten.schoenert . That said if you want to prep a repo and "maintain" it that would be great (I can handle the upload).
Preparing a new packaging repository isn't that difficult and I can work on this. What is the wanted PureOs archive the version from Debian testing (or bullseye-backport) should get uploaded? My current guess would be it should go into landing. Forgive a maybe stupid question, I was nearly 2 months off now and haven't followed this thread and around.
@carsten.schoenert thanks for handling that! I'd just grab the salsa repo and gbp-import-dsc@praveen 's work on top of it (so we keep the credit).
If it goes to landing or to octarine first I don't really bother, both works for me. If @praveen uses it a lot and it's stable for him I'd go for landing right away.
The repository looks like it's a copy of the upstream project. I haven't found some information about my assumption.
The file d/README.source refers to a target make-orig-source to create the additional needed tarballs, but the execution of this target fails due non existing folders. For sure the source for the additional tarball could be added to the tree, but this isn't enough to get also the pristine-tar approach working.
$ LANG= make -f debian/rules make-orig-sourcetar czf ../nheko_`dpkg-parsechangelog | grep ^Version | sed 's/Version: \(.*\)-[^-]*/\1/'`.orig.tar.gz --exclude-vcs --exclude-backups --exclude /debian --exclude /mtxclient /lmdbxx -C .. `basename /home/carsten/gitprojects/purism/scratch/nheko`tar: Removing leading `/' from member namestar: /lmdbxx: Cannot stat: No such file or directorytar: Exiting with failure status due to previous errorsmake: *** [debian/rules:33: make-orig-source] Error 2
The included config for git-buildpackage is missing the information about needed component tarballs.
The pristine-tar branch for rebuilding all tarballs is missing, I'm unable to rebuild the package from this repository.
Currently I'm unsure how to proceed as the current state of the repository on Salsa makes working with it for PureOS a bit PITA and cumbersome. On the other hand doing the packaging work for nheko for PureOS different to other cloned packages isn't something I'd suggest and Need to work with.
Best in my eyes would be to "clean up" and tune the Salsa tree into the correct direction. Means basically
Use a pristine-tar branch so we can rebuild all required tarballs from the git tree.
Drop the usage of a native git tree pulled in from the upstream repository.
Adjust the d/gbp.conf entries so the file is a real help for users of git-buildpackage.
Rewrite d/README.source so other users and packagers knows how to work with the package.
Packaging for PureOS should be done outside the Salsa tree.
I can try to work on this, but not before the next weekend. But before I jump into some work I'd like to know how about you feel the situation.
The pipeline passes now after pristine-tar can find the required tagged versions within the package tree.
Given the feedback from @kyle.rankin I think there is no real reason to push the prepared version into octarine first and it can go into landing then. @guido.gunther Do you see something I've missed? If all agree I'd move the current tree within my namespace into https://source.puri.sm/pureos/packages and prepare an entry for the deb-build-jobs tree.
I'll be on a businesses trip next week again, I can't promise that I can do some effective work on this today.
I have run into stability issues with the version of nheko packaged by PureOS by default with recent Matrix server versions. There seems to be some backwards incompatibility issue that causes nheko to crash after connecting, consistently, rendering it unusable.
I just tested the bullseye-backports nheko package on my system and it resolved that issue such that I can use nheko again. So at least in my mind it would be OK to roll the bullseye-backports version directly into PureOS. It adds some new dependencies when you install it, but they are dependencies that are already present in PureOS. Since the current version now seems to not function on recent Matrix servers there is more urgency and in my mind less concern about bugs in the updated version as the existing version does not work at all.