Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#63099 - [bash-bats] Switch package to maintained upstream

Attached to Project: Community Packages
Opened by Danila Kiver (licryco) - Thursday, 04 July 2019, 16:45 GMT
Last edited by Balló György (City-busz) - Sunday, 01 September 2019, 10:05 GMT
Task Type General Gripe
Category Packages
Status Assigned
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 5
Private No


The bash-bats package ( uses an unmaintained upstream (, abandoned by its owner in early 2016 (announced and discussed in Last bats version, released from this upstream, is 0.4.0, which is essentially broken because of few serious bugs (e.g. - this one breaks any test relying on the default value of IFS variable). There will be no more releases in this upstream (extremely likely).

As discussed in git issue #150 (see the link above), the project is continued in community-maintained fork (, which includes many crucial fixes and already reached stable version 1.1.0.

This ticket is a request to switch the bash-bats package from abandoned upstream to the new one.
This task depends upon

Comment by Jorge Luis Martinez Gomez (jol) - Friday, 19 July 2019, 16:45 GMT
Here's an updated PKGBUILD (not official; I'm not a maintainer) for the meantime. I renamed the package as was done with the repo to bats-core. I also set pkgrel to 0, despite documentation saying it should be at least 1, hoping that will cause an automated update when the official PKGBUILD is updated.

To anyone that doesn't know how to use these. Put both files in a new directory and run:

$ makepkg

That will create a package you can then install with:

$ sudo pacman -U bash-bats-core-1.1.0-0-any.pkg.tar.xz