Package Details: python-pylzma 0.5.0-5

Git Clone URL: https://aur.archlinux.org/python-pylzma.git (read-only, click to copy)
Package Base: python-pylzma
Description: Platform independent python bindings for the LZMA compression library
Upstream URL: https://www.joachim-bauch.de/projects/pylzma/
Licenses: LGPL2.1
Conflicts: pylzma
Submitter: yan12125
Maintainer: Rhinoceros
Last Packager: Rhinoceros
Votes: 13
Popularity: 0.000000
First Submitted: 2018-09-27 11:25 (UTC)
Last Updated: 2024-11-17 00:54 (UTC)

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

1 2 3 Next › Last »

Rhinoceros commented on 2024-12-23 00:52 (UTC)

This is broken for me again when trying to rebuild for the latest python 3.13.1-1.

src/pylzma/pylzma_aes.c:158:5: error: initialization of ‘long int’ from ‘void *’ makes integer from pointer without a cast [-Wint-conversion]
  158 |     NULL,                                /* printfunc  tp_print;   */
      |     ^~~~
src/pylzma/pylzma_aes.c:158:5: note: (near initialization for ‘CAESDecrypt_Type.tp_vectorcall_offset’)
error: command '/usr/bin/gcc' failed with exit code 1

I also tried reverting the workaround, but I still get the same error. Any suggestions would be welcome!

Rhinoceros commented on 2024-11-17 00:55 (UTC)

Thanks for reporting @realroot. I can replicate this bug in a clean chroot. I think upstream has abandoned this project, but I've added the workaround to this problem.

realroot commented on 2024-11-16 17:22 (UTC) 

src/pylzma/pylzma_aes.c:158:5: error: initialization of ‘long int’ from ‘void *’ makes integer from pointer without a cast [-Wint-conversion]
  158 |     NULL,                                /* printfunc  tp_print;   */
      |     ^~~~
src/pylzma/pylzma_aes.c:158:5: note: (near initialization for ‘CAESDecrypt_Type.tp_vectorcall_offset’)
error: command '/usr/bin/gcc' failed with exit code 1
==> ERROR: A failure occurred in build().

Rhinoceros commented on 2024-10-18 04:01 (UTC) (edited on 2024-11-17 00:31 (UTC) by Rhinoceros)

Thanks @Redoxahmii. Hopefully archive.org will be back up soon. I tried to find a workaround in the meantime, but I can't even get this package to build without the file. Happy to take input if anyone has anything useful. Otherwise we'll just have to wait.

E: archive.org is back up, although this is very slow for me.

Redoxahmii commented on 2024-10-18 02:17 (UTC)

does not seem to be working anymore. the stack exchange link uses way internet archives which is down at the moment.

Rhinoceros commented on 2024-02-21 04:13 (UTC)

Thanks for the comment @ruzko. I am also annoyed by the testing data, also because the checksum seems to change occasionally. Unfortunately upstream has hardcoded this specific massive file for their tests. I think it would be best for upstream to change the file they use, but unfortunately they aren't particularly responsive, and I'm not even sure if the project is dead. I haven't looked in detail, but conceivably we could patch the upstream scripts instead. I'm happy to accept any changes if you wanted to propose a smaller, stable alternative.

ruzko commented on 2024-02-17 19:24 (UTC)

Thanks for packaging this :) Could we use some smaller data for testing? Testing data is 103M big. On my crippled network connection, downloading the testing data from stackexhange takes ~20 minutes, while downloading the program itself takes ~3 seconds

Cheers

ignapk commented on 2021-06-30 07:03 (UTC)

That's a good idea, and yes it must have been very annoying that they kept changing it. Thank you for the quick fix and maintaining this package in general :)

Rhinoceros commented on 2021-06-29 00:07 (UTC)

Thanks for letting me know @ignapk. I'm just going to skip the checksum now, since it's only for testing anyway. It's super annoying that they keep changing it!

ignapk commented on 2021-06-28 15:42 (UTC)

Unfortunately, the upstream seems to have changed the data again:

==> Validating source files with sha256sums...
    pylzma-0.5.0.tar.gz ... Passed
    ux.stackexchange.com.201214.7z ... FAILED
==> ERROR: One or more files did not pass the validity check!

Can be workarounded with --skipchecksums makepkg flag

1 2 3 Next › Last »