Source package for https://github.com/Felitendo/bt-volume-step: a daemon that
corrects the coarse internal volume grid of Bluetooth audio devices on
PipeWire. Nothing is compiled; the upstream Makefile installs the script and
a systemd user unit.
The AUR clone runs unconditionally, so every maintenance window turns the
whole matrix red - including the packages that had nothing to publish.
Tolerate connectivity failures when the run produced no commit; a pending
push and non-transient errors stay fatal.
The AUR rejected the push - "package already provided by [extra]: bazaar".
Upstream 0.9.1 landed in the official repositories, which rules the package
out of the AUR entirely, so the source-package conversion from 0229020 has
nowhere to go. Nothing to replace it with: pacman -S bazaar.
README now lists the official repositories as the first thing to check.
These three have no upstream Linux binary to point at, but also no
equivalent in the AUR or the official repositories - so unlike the packages
dropped in 46ddf59 they can legitimately exist, just as source packages.
bazaar-bin -> bazaar
timetable-bin -> timetable
chromium-widevine-helper-bin -> chromium-widevine-helper
bazaar and timetable now build their meson projects in build(); the
checksum-only CI path still applies, since the source is upstream's release
tarball.
chromium-widevine-helper compiles nothing (Python script, JSON manifests and
extension assets). Upstream publishes neither releases nor tags, so the
package pins the main commit carrying the version from the Fedora spec and
verifies the two agree in prepare() - being tied to a specific version, it
needs no -git suffix. refresh_checksums() moves the pin.
The AUR repos for the new names are created by the first push; the old -bin
packages are left to the pending deletion requests.
update-package.sh no longer builds anything or publishes GitHub release
assets: every package now tracks an upstream deliverable, so the only work
left on a new version is pkgver + checksums. BUILD_DEPS survives for the
CI test build of packages that compile in the PKGBUILD.
Removes the seven packages that cannot be made compliant: upstream ships no
Linux binary to point at, and a maintained source package for each already
exists in the AUR, so a rebuilt version would just be a duplicate.
gearlever-bin, gnome-network-displays-bin, librepods-bin, planify-bin,
protonplus-bin, thonny-bin, trayscale-bin
README documents the rule and why, so the pattern does not come back.
The AUR does not allow packages to ship a binary tarball built by the
maintainer - a -bin package must repackage a deliverable published by
upstream. These six packages now do that:
snapx-bin upstream's self-contained Linux tar.zst
zapzap-bin upstream's pure-Python wheel
faugus-launcher-bin upstream's arch-independent .deb
wiiudownloader-bin upstream's AppImage
waydroid-helper-bin upstream's AppImage
chiaki-ng-bin upstream's AppImage
All six drop build_artifact() and switch to refresh_checksums(), so CI no
longer builds or hosts anything - it only tracks upstream's assets.
Where the asset name carries build metadata that does not follow from
pkgver (snapx, faugus-launcher), refresh_checksums() resolves it via the
GitHub API and syncs an _asset variable in the PKGBUILD.
Dependency lists are re-derived from what the bundles actually resolve
outside themselves; the AppImage payloads land in /opt with wrappers in
/usr/bin, because their entry points resolve paths relative to argv[0].
Felitendo
github-actions[bot]
Felitendo