Package Details: readpe 0.85.1-2

Git Clone URL: https://aur.archlinux.org/readpe.git (read-only, click to copy)
Package Base: readpe
Description: PE file analysis toolkit
Upstream URL: https://github.com/mentebinaria/readpe
Keywords: analysis pe pev reverse windows
Licenses: LicenseRef-GPL-2.0-or-later-with-OpenSSL-exception AND LGPL-3.0-or-later
Conflicts: pev
Submitter: peelz
Maintainer: peelz
Last Packager: peelz
Votes: 20
Popularity: 0.000546
First Submitted: 2023-06-02 03:17 (UTC)
Last Updated: 2026-07-24 00:12 (UTC)

Dependencies (2)

Required by (2)

Sources (1)

Latest Comments

C0rn3j commented on 2026-07-23 19:50 (UTC)

About nvchecker: I've never used it. Does it automate PKGBUILD modifications, or read from the PKGBUILD somehow?

Yes and yes. All official packages use it (well, some still need attention, but that's the end goal) - it lets you do pkgctl version check and pkgctl version upgrade - for official packages, it automates update notifications too, by automatically creating GitLab issues.

By the way, it would also be nice to add a license for the package itself - pkgctl license setup - see https://rfc.archlinux.page/0040-license-package-sources/#aur

I'd rather not bump it to 0.85.1. That release was just them fixing the version string they forgot to update in the source code.

I'd still bump it, it's both a release and a tag, it's not a very useful version bump, but that's what the upstream came up with :shrug:

the maintainers have deleted and re-created tags multiple times in the past

Oof, did someone inform them why that's a bad idea™? I'd switch it to tags and if that happens again, kindly ask them not to do that again - surely they won't do it on purpose then?

The checksum verification works fine nowadays, so I wouldn't worry about that part of it.

peelz commented on 2026-07-23 19:00 (UTC)

Hey C0rn3j,

I'll update the License, thanks.

About pinning to a commit: I do that because the maintainers have deleted and re-created tags multiple times in the past, and tags can be mutated. Also git sources used to have broken checksum verification, so pinning to a specific commit is safer since commits are immutable.

About the version: I'd rather not bump it to 0.85.1. That release was just them fixing the version string they forgot to update in the source code. The tool still has the 0.85 version string internally, so I'd prefer to keep the package version consistent with what the tool actually reports (i.e. readpe --version).

About nvchecker: I've never used it. Does it automate PKGBUILD modifications, or read from the PKGBUILD somehow?

C0rn3j commented on 2026-07-23 17:44 (UTC)

I think the SPDX license I came up with in AUR/readpe-git is more accurate - https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=readpe-git

It's also fairly odd to target a specific commit instead of a tag - it also prevents you from setting up .nvchecker.toml for easy upgrades and version checking.

severach commented on 2025-04-30 16:29 (UTC)

git is not used in this package. diff pev and pev-git PKGBUILD and you'll see that they are the same with a few lines changed. This shows that they do the same thing and makes patches and updates easy to transfer from one to the other.

mxlgv commented on 2025-04-30 12:48 (UTC)

Why is there a condition in PKGBUILD under which it is not the release that is downloaded, but the GIT version? There is a GIT package for this: https://aur.archlinux.org/packages/pev-git

fusca commented on 2021-03-02 17:45 (UTC)

The PEV repository has been changed to https://github.com/merces/pev/

severach commented on 2020-04-28 21:18 (UTC) (edited on 2020-04-28 21:18 (UTC) by severach)

The original does not get a conflicts or provides. All the alternates do. This package would get a conflicts if there were deprecated package names that need to be pushed off.

jojo4u commented on 2020-04-28 12:39 (UTC)

This could need "conflicts=('pev-git')"