Description of problem: fedora tx version is to old for latest transifex API changes Version-Release number of selected component (if applicable): transifex-client-0.13.7-11.fc38 How reproducible: The following command tx pull -af shows the following error: tx ERROR: not enough values to unpack (expected 2, got 1) see https://github.com/transifex/cli/issues/110 Steps to Reproduce: 1. 2. 3. Actual results: tx-client is broken Expected results: a working tx-client Additional info: The actual version of tx client is 1.6.7 which works fine with latest transifex API changes in f38.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Sadly, no reaction from maintainer!!! Any way, transifex-client needs an urgent update to work with transifex.
Current version in rawhide is transifex-client-0.13.7-16.fc41
Opened a non-responsive maintainer process as I tried to contact Luis Enrique several times. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XO6DBPZTNMQS3Q4H2BM55MRGQUBWVB7L/
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.