Package Details: libervia-backend-hg 0.8.0.rev501.g07439bc0ed3c-1

Git Clone URL: (read-only, click to copy)
Package Base: libervia-backend-hg
Description: Libervia, multi-frontends multi-purposes XMPP client (core)
Upstream URL:
Licenses: AGPL3
Conflicts: sat-xmpp-hg
Provides: libervia-backend
Submitter: jnanar
Maintainer: jnanar
Last Packager: jnanar
Votes: 1
Popularity: 0.000000
First Submitted: 2021-08-21 14:25 (UTC)
Last Updated: 2024-02-25 18:51 (UTC)

Latest Comments

1 2 3 Next › Last »

MarsSeed commented on 2023-05-14 10:58 (UTC) (edited on 2023-05-14 11:05 (UTC) by MarsSeed)

The dependency python-langid got deleted, because it is a Python 2 only library. (Last release was in 2016, and the project got discontinued in 2017.)

If libervia needs this functionality, it should call for the Python 3 compatible fork called py3langid. (It's not currently available in Arch/AUR repos.)

MarsSeed commented on 2022-07-09 12:01 (UTC) (edited on 2022-07-09 12:05 (UTC) by MarsSeed)

+1 suggestion. You could use the following code to improve upon the pkgver generation:

# _version=0.8.0    # -- remove this hard-coded main version

pkgver() {
    cd "$_realname"
    hg log -r . --template '{latesttag}.rev{latesttagdistance}.g{node|short}\n' | sed 's/^v//;s/_/./g'

This will generate a pkgver that automatically picks up the base version from the latest Mercurial tag (which is similar to a git tag), and also count the number of revisions (commits) only after that last tag.

The code will generate something like this: pkgver=0.8.0.rev114.g23b53ac87e0f.

The change in the format from .rREVISION to .revREVISION is a necessary compromise, because with the code I propose, the changeover to count only new commits since the last tag, as opposed to the earlier counting of all existing commits, leads to a lower REVISION number generated. *

(The other alternative for changes leading to a lower pkgver would be to bump to epoch=1, but I don't really like that option and I think that is best to reserve to situations where no other viable alternatives exist to keep the pkgver to increase monotonically.)

Nevertheless, I think it is more informative for users to be able see in the package version the actual number of commits that have been added on top of the latest stable tag. :)

EDIT: * With this format change, the monotonicity of pkgver will be kept; i.e., the new version generated by my proposed code will be considered by pacman to be higher, so there will be no need to bump to epoch=1.

MarsSeed commented on 2022-07-09 11:39 (UTC)

Thanks for the update. :)

Please also kindly bump pkgrel to 2, because for people who already have updated to the latest VCS commit version, their AUR helpers won't update to your new PKGBUILD, so they won't have the new set of dependencies.

Also, please kindly refresh the .SRCINFO afterwards. (Without such, the AUR package database is not updated, and nothing of your changes get visible on the AUR page, as well as for AUR helper clients.)

jnanar commented on 2022-07-09 11:26 (UTC)

@MarsSeed I updated the PKGBUILD according to your helpful comment. Thanks a lot. Unfortunately, a lot of dependencies and requirements depends on obsolete versions. I am discussing with @goffi to let him know that dependencies should be updated but I know that he is very busy right now with the ActivityPub - XMPP gateway. Don't hesitate to try and comment if you have some time.

MarsSeed commented on 2022-07-08 17:25 (UTC) (edited on 2023-07-12 18:30 (UTC) by MarsSeed)

@goffi, thank you for your response and clarifications. It's also good to hear that you are planning to modernize your project's build management by using newer tools like poetry.

@jnanar, thank you for maintaining this AUR package. Looks like you can remove depends=python-pycrypto altogether, as per @goffi's statement. (I've included this in my list below as well.)

Also please kindly check the's requirements as I did, and align this build accordingly.

Summary of changes needed (as per

Please kindly add the following:

Also please make the following replacements:

And please remove:

goffi commented on 2022-07-08 08:11 (UTC)

Hi, this should not depend on the discontinued and deprecated pycrypto (python-pycrypto) module.

Actually, the current doesn't even mention it - only the requirements.txt. Which is a discrepancy in itself.

Hi MarsSeed, I'm the upstream developer.

PyCrypto is indeed not used anymore for years, but it's still present in the requirements.txt because it is (was? it seems that it has been updated upstream) a dependency of python-otr. That can be safely removed (Libervia can work without OTR, and OMEMO is implemented and the recommended e2ee algorithm nowadays).

"requirements.txt" is produced from pip freeze and is intended for developers anyway, "" is the source to follow for dependencies.

I plan to move to Poetry in close future, that will hopefully help maintaining the dependencies.

MarsSeed commented on 2022-07-07 14:28 (UTC) (edited on 2022-07-07 14:30 (UTC) by MarsSeed)

Though I would not add a different git remote to an existing directory at the start.

Instead, I would delete the python-txdbus directory and use the following command:

git clone ssh://

MarsSeed commented on 2022-07-07 14:25 (UTC)

Hi @jnanar,

Yes, it seems that the python-txdbus package itself has been deleted, but its AUR-git repo exists.

If you update it locally, commit it and push it, the AUR package will be automatically recreated.

jnanar commented on 2022-07-06 18:55 (UTC)

Hello @MarsSeed Thanks for your comments. I could not respond earlier as I was in holidays. I will try to take all your points into account. I tried to create a python-txdbus but there is already one. I did:

git remote add origin ssh://
git fetch

And it fetched a package for txdbus:

Maintainer: Hugo Osvaldo Barrera
Contributor: Daniel Nagy <danielnagy at gmx de>

But it does not seems to exist: It was deleted ? Do you know what is happening?

I am discussing with upstream about the incoherences in the requirements.txt. Thanks for brining that point to my attention :-).