The gufw-pkexec script hardcodes the path to the python module; this made it error out: python3: can't open file '/usr/share/gufw/gufw/gufw.py': [Errno 2] No such file or directory The issue was missed when the package was updated. Using python entry points should be suggested to upstream, since that's the standard way of distributing python programs with setuptools.
20 lines
663 B
Bash
20 lines
663 B
Bash
# Template file for 'gufw'
|
|
pkgname=gufw
|
|
version=21.04.0
|
|
revision=2
|
|
wrksrc="gufw-${version}"
|
|
build_style=python3-module
|
|
hostmakedepends="python3-distutils-extra intltool"
|
|
depends="python3-gobject net-tools ufw gtk+3 webkit2gtk"
|
|
short_desc="GTK+ frontend for ufw"
|
|
maintainer="Enno Boland <gottox@voidlinux.org>"
|
|
license="GPL-3.0-or-later"
|
|
homepage="https://gufw.org/"
|
|
distfiles="https://github.com/costales/gufw/archive/refs/tags/$version.tar.gz"
|
|
checksum=b57892ec9817ca1520b2fef31cc3ef404b243ef1230bdccfdc6d75ed4e461841
|
|
|
|
pre_configure() {
|
|
vsed -i -e \
|
|
"s|/usr/share/gufw/gufw/gufw.py|/usr/lib/python${py3_ver}/site-packages/gufw/gufw.py|" \
|
|
bin/gufw-pkexec
|
|
}
|