Package Details: polyfile 0.5.0-1

Git Clone URL: https://aur.archlinux.org/polyfile.git (read-only, click to copy)
Package Base: polyfile
Description: A utility to identify and map the semantic structure of files, including polyglots, chimeras, and schizophrenic files.
Upstream URL: https://github.com/trailofbits/polyfile
Licenses: LGPL3
Submitter: dkasak
Maintainer: None
Last Packager: FabioLolix
Votes: 1
Popularity: 0.000000
First Submitted: 2020-09-11 13:25 (UTC)
Last Updated: 2022-12-18 20:51 (UTC)

Latest Comments

hurufu commented on 2023-01-11 12:27 (UTC)

Right now after an upgrade the program fails with the following error:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 581, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 909, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 800, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (pdfminer.six 20221105 (/usr/lib/python3.10/site-packages), Requirement.parse('pdfminer.six==20220524'), {'polyfile'})

Please can you specify exact pdfminer version in the PKGBUILD, so user will not break it during an upgrade? Just replace pdfminer with pdfminer=20220524 in the depends array.

dkasak commented on 2022-07-04 20:07 (UTC)

Right, I guess I could've also pinned particular submodule commits as well.

Alright, I'm cancelling the delete request and disowning the package.

FabioLolix commented on 2022-07-04 19:32 (UTC)

If I use git tags/commits, does this then not make the package a VCS one, so that the naming scheme must be *-git?

No because you're building a fixed version instead of pulling the latest

I don't really have time to fiddle with this right now

You can orphan the pkgbuild so someone else can pick it up

dkasak commented on 2022-07-04 18:48 (UTC)

@FabioLolix: I don't really have time to fiddle with this right now, but... If I use git tags/commits, does this then not make the package a VCS one, so that the naming scheme must be *-git?

Anyway, the above is what I did for polyfile-git.

FabioLolix commented on 2022-07-04 14:07 (UTC)

There is no need to delete the pkgbuild, you can use git tags or git commits in source=() to build the program

dkasak commented on 2022-07-04 11:54 (UTC)

It's not really possible to package polyfile as a non-VCS package due to release tarballs failing to compile because they rely on submodules (see https://github.com/trailofbits/polyfile/issues/3362).

So I'm discontinuing this package in favour of polyfile-git instead. I'll file a deletion for this one.