Package Details: python-rarfile 4.2-1

Git Clone URL: https://aur.archlinux.org/python-rarfile.git (read-only, click to copy)
Package Base: python-rarfile
Description: Python module for RAR archive reading
Upstream URL: https://github.com/markokr/rarfile
Licenses: ISC
Submitter: sleduc
Maintainer: qubidt
Last Packager: qubidt
Votes: 29
Popularity: 0.046740
First Submitted: 2016-05-05 16:34 (UTC)
Last Updated: 2024-04-09 14:38 (UTC)

Dependencies (19)

Sources (1)

Latest Comments

chowbok commented on 2024-04-10 21:29 (UTC)

"test_unar_tool fails: rarfile.BadRarFile"

I got this error as well.

Lili1228 commented on 2024-04-10 12:13 (UTC) (edited on 2024-04-10 12:56 (UTC) by Lili1228)

test_unar_tool fails: rarfile.BadRarFile: Corrupt file - CRC check failed: stest1.txt - exp=3317163682 got=2931710230

EDIT: On second thought, it worked on my second machine, so I suppose there's something wrong with my configuration.

qubidt commented on 2024-01-27 02:26 (UTC)

I don't see the logic to force unrar as a mandatory dependency as it is not required to use the package. The package works perfectly fine with any of the decompression backends, albeit with degraded performance/functionality. This might be an acceptable tradeoff for some use-cases. I see no benefit of restricting the user of making the decision that is more appropriate for their situation. Requiring unrar defeats the purpose of having the other backends as optional depends to begin with.

I also don't see any justification for similar cases in the official packages. And frankly, making unrar a mandatory dependency is simply incorrect.

MarsSeed commented on 2023-12-17 14:43 (UTC)

Also I think it would be best to declare unrar as a mandatory depend. As this is the recommended rar implementation to use, and the one that supports the full range of features offered by this library.

Otherwise most people's machines will stick to libarchive's bsdtar, which does not support multi-volume RAR archives, solid archives and password-protected archives of this format.

MarsSeed commented on 2023-12-17 14:34 (UTC)

It seems that actually python-cryptography is the preferred backend for decrypting password-protected, AES-encrypted headers, because it is a faster implementation that relies on native binary libraries of openssl instead of running a pure-Python computation with python-pycryptodome.

Both are optional dependencies, but if cryptography is installed, that will be used instead of pycryptodome.

yochananmarqos commented on 2022-06-27 20:07 (UTC)

@MarsSeed: Thanks for the heads up.

MarsSeed commented on 2022-06-27 18:46 (UTC)

Hi,

I recommend to not make this package optdepend on python-crypto, but rather on python-pycryptodome, which is the continuation fork.

Someone created a wrong package in AUR providing "python-crypto". So it's much better if you declare python-pycryptodome, to ensure the proper dependency is suggested to users.

Cheers.

dr3mro commented on 2019-11-05 11:57 (UTC)

latest version is 3.1 not 3.0 and the same for python2-rarfile