Arch Linux User Repository

Package now switched to the new Go based client:

https://github.com/transifex/cli

For information on how to migrate:

https://github.com/transifex/cli#migrating-from-older-versions-of-the-client

As per issue #170 in transifex/cli repo, adding -ldflags "-X 'github.com/transifex/cli/internal/txlib.Version=${pkgver}'" to go build -o build enables the -v | --version flags to the tx binary.

This flag is needed to use sphinx-intl with Transifex.

Can you please add it to the PKGBUILD?

I noticed that the packaged tx doesn't seem to have the -v|--version flag, while installing from the official binary there is. Any idea how this happened?

$ pacman -Qo /usr/bin/tx
/usr/bin/tx is owned by transifex-client 1.6.4-1
$ /usr/bin/tx -v
Incorrect Usage. flag provided but not defined: -v
(...)
$ curl -o- https://raw.githubusercontent.com/transifex/cli/master/install.sh | bash
(... some output regard downloading ...)
$ ./tx -v
TX Client, version=1.6.5

Martchus: You're right, that was a leftover from the Python -> Go conversion.

Unfortunately I don't have an easy way to test on i686 or aarch64, so I'll leave it at only x86_64 for now.

This is an arch-specific package. So archs should be x86_64, see https://wiki.archlinux.org/title/Arch_package_guidelines#Architectures. (I'd say for AUR packages it is also acceptable to add further archs such as i686 and aarch64 if the package is known to compile for those. However, one must not any if the resulting package contains arch specific contents.)

Package now switched to the new Go based client:

https://github.com/transifex/cli

For information on how to migrate:

https://github.com/transifex/cli#migrating-from-older-versions-of-the-client

To build 4.0.9 until it is fixed in community. Download https://raw.githubusercontent.com/archlinux/svntogit-community/packages/python-gitdb/trunk/PKGBUILD, edit version number to 4.0.9 and execute makepkg --install -s -r --skippgpcheck.

Package is currently broken due to a dependency conflict until the python-gitdb package is upgraded to 4.0.9. (Package has been flagged as out of date since October 25th.)

In the meantime, you could try to build python-gitdb 4.0.9 yourself, however the signature on PyPI cannot be verified: https://github.com/gitpython-developers/gitdb/issues/77

@yan12125, amazing. I've applied your patch in 0.14.2-2. Thank you so much!

Before upstream fixes the slugify issue, it can be work-arounded by

prepare() {
  cd "${pkgname}-${pkgver}"
  sed -i 's#python-slugify<5.0.0#python-slugify#' requirements.txt
}

Same issue here. Reported to upstream: https://github.com/transifex/transifex-client/issues/323