Package Details: imhex 1.36.2-1

Git Clone URL: https://aur.archlinux.org/imhex.git (read-only, click to copy)
Package Base: imhex
Description: A Hex Editor for Reverse Engineers, Programmers and people that value their eye sight when working at 3 AM
Upstream URL: https://imhex.werwolv.net
Licenses: GPL-2.0-or-later
Conflicts: imhex-patterns-git
Provides: imhex-patterns
Submitter: KokaKiwi
Maintainer: KokaKiwi
Last Packager: KokaKiwi
Votes: 62
Popularity: 0.72
First Submitted: 2020-12-04 11:19 (UTC)
Last Updated: 2024-12-28 19:45 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

SunRed commented on 2023-06-10 13:24 (UTC)

Since this is not a git package, could you please set every git source to a specific commit or tag to also make this package reproducible and to not let paru classify this as a development package.

Cheers.

KokaKiwi commented on 2023-05-04 08:51 (UTC)

@targodan oops :D

targodan commented on 2023-05-04 08:48 (UTC)

imhex-patterns-git is listed as optional dependency and as conflicting. I don't know if imhex-patterns-git is a replacement or a complementing package, but one of the two things (optional dependecy, or conflict) is wrong. :)

optdepends=(
  'imhex-patterns-git: ImHex base patterns'
)
provides=('imhex-patterns')
conflicts=('imhex-patterns-git')

KokaKiwi commented on 2023-05-02 08:54 (UTC)

@k1gen You need to either delete all the /usr/lib/libimhex.so.* files or add --overwrite /usr/lib/libimhex.so.1.28.0 to pacman when upgrading imhex (only once, future update won't need this as the file is now part of the package)

seqfault commented on 2023-04-30 18:01 (UTC) (edited on 2023-04-30 18:02 (UTC) by seqfault)

I have this when updating:

error: failed to commit transaction (conflicting files)
imhex: /usr/lib/libimhex.so.1.28.0 exists in filesystem
Errors occurred, no packages were upgraded.

VorpalWay commented on 2023-04-29 11:41 (UTC)

I get the file /usr/lib/libimhex.so.1.28.0 on my system that is not associated with any package. If I understand this correctly, it should be installed by the package. That is how it works for all other packages.

I guess you could create the symlink by something like: ldconfig -n "$pkgdir/usr/lib", however I don't know if this is the preferred way of doing things.

KokaKiwi commented on 2023-01-09 10:07 (UTC)

@headassbtw You can already instruct makepkg to use all available cores by modifying the /etc/makepkg.conf file (there's a line specifically for this commented out)

headassbtw commented on 2023-01-08 08:39 (UTC)

hey, could you update the pkgbuild to use all cores to compile? having a 24-thread CPU and it taking 20x longer to compile is mildly inconveniencing

tesnos6921 commented on 2022-10-25 12:41 (UTC) (edited on 2022-10-25 12:42 (UTC) by tesnos6921)

prepare() now fails due to git security change ( https://github.blog/2022-10-18-git-security-vulnerabilities-announced/#cve-2022-39253 )

==> Starting prepare()...
Submodule 'lib/external/capstone' (https://github.com/capstone-engine/capstone) registered for path 'lib/external/capstone'
...
Submodule 'lib/external/yara/yara' (https://github.com/VirusTotal/yara) registered for path 'lib/external/yara/yara'
Cloning into '/home/tesnos6921/.cache/paru/clone/imhex/src/imhex/lib/external/capstone'...
fatal: transport 'file' not allowed
fatal: clone of '/home/tesnos6921/.cache/paru/clone/imhex/src/capstone' into submodule path '/home/tesnos6921/.cache/paru/clone/imhex/src/imhex/lib/external/capstone' failed
Failed to clone 'lib/external/capstone'. Retry scheduled
Cloning into '/home/tesnos6921/.cache/paru/clone/imhex/src/imhex/lib/external/libromfs'...
fatal: transport 'file' not allowed
fatal: clone of '/home/tesnos6921/.cache/paru/clone/imhex/src/libromfs' into submodule path '/home/tesnos6921/.cache/paru/clone/imhex/src/imhex/lib/external/libromfs' failed
...

AlexApps99 commented on 2022-10-13 01:11 (UTC) (edited on 2022-10-27 07:36 (UTC) by AlexApps99)

This package fails to build when CMAKE_GENERATOR=Ninja because it assumes make is used as the build system.

This can probably be fixed by using cmake --build.

Edit: this seems to have been fixed, thanks

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »