[SOLVED] Need help adapting PKGBUILD for abandoned AUR package

emk2203 · 2026-10-16 08:06:07

I want to use a package from the AUR which is abandoned (flagged out-of-date for more than 6 months without reaction) and adapt the PKGBUILD for the latest version for needed features.

I am stumped how to do this since I rarely deal with this particular PKGBUILD feature, the PKGBUILDs I modified in the past were basic and easily adaptable.

The PKGBUILD is from the package turing-smart-screen-python: https://aur.archlinux.org/cgit/aur.git/ … een-python

I can deal with changing the version numbers and adding the new dependency of libusb, also updating the checksum for the first file.

What I don't know is where the last 4 files with checksums come from, and because of this, I cannot adjust the checksums except for the first file (archive from github).

Help is appreciated. I don't expect that someone changes the PKGBUILD for me, just a pointer in the right direction would be great.

Last edited by emk2203 (2026-10-16 11:04:45)

WorMzy · 2026-10-16 08:22:12

They are local files, included in the AUR package's repo along with the PKGBUILD. If you've not modified them, you shouldn't need to update the checksums, but if you do, you can generate them with `makepkg -g` (see `man makepkg | less -p geninteg`). Alternatively use updpkgsums (from pacman-contrib) to update the checksums in place in the PKGBUILD.

Mod note: moving to AUR Issues.

killertofus · 2026-10-16 08:29:05

1) was flagged out of date 15 days ago, not 6 months ago, the release was 6 months ago
2) updpkgsums is better to use, because makepkg -g generates the pkgsums and also add a duplicate line of pkgsums, while updpkgsums does not

emk2203 · 2026-10-16 10:38:27

OK, after I fixed the checksum, makepkg -si gives me ==> ERROR: install file (turing-smart-screen-python.install) does not exist or is not a regular file.

Is there also an easy fix for this? Cannot find this anywhere in the AUR description.

mpan · 2026-10-16 10:54:33

When you cloned the repository, the file has been cloned together with PKGBUILD and all other files: current view.

A side note: checksums are only relevant if you plan to reuse or publish your PKGBUILD. There is no point in recreating them for a single, private build. And GitHub also doesn’t guarantees automatic archives to be byte-to-byte exact, which means checksums may change. In 2003 they made a promise to try to keep them intact for a. But it’s 2026 and it’s being observed archives can no longer be assumed to be unchanging.

emk2203 · 2026-10-16 11:04:07

Thanks, that was the missing piece. I overlooked it because it wasn't mentioned as source (did a manual download).

mpan · 2026-10-16 16:45:24

Then consider reading the entire AUR article, if you didn’t do so yet. In particular the red box at the top.

Arch Linux

#1 2026-10-16 08:06:07

[SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#2 2026-10-16 08:22:12

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#3 2026-10-16 08:29:05

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#4 2026-10-16 10:38:27

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#5 2026-10-16 10:54:33

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#6 2026-10-16 11:04:07

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

#7 2026-10-16 16:45:24

Re: [SOLVED] Need help adapting PKGBUILD for abandoned AUR package

Board footer