Packages must not enable units themselves: the Arch default preset is
"disable *", and a user unit cannot be enabled from a pacman transaction
anyway, which runs as root without the user's session bus.
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.