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 Morten Linderud (Foxboron) - Wednesday, 03 March 2021, 16:50 GMT
Opened by Danila Kiver (licryco) - Thursday, 04 July 2019, 16:45 GMT
Last edited by Morten Linderud (Foxboron) - Wednesday, 03 March 2021, 16:50 GMT
|
Details
The bash-bats package
(https://www.archlinux.org/packages/community/any/bash-bats)
uses an unmaintained upstream
(https://github.com/sstephenson/bats), abandoned by its
owner in early 2016 (announced and discussed in
https://github.com/sstephenson/bats/issues/150). Last bats version, released from this upstream, is
0.4.0, which is essentially broken because of few serious
bugs (e.g.
https://github.com/sstephenson/bats/issues/89
- 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 (https://github.com/bats-core/bats-core), 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
Closed by Morten Linderud (Foxboron)
Wednesday, 03 March 2021, 16:50 GMT
Reason for closing: Fixed
Additional comments about closing: 1.2.1-2
Wednesday, 03 March 2021, 16:50 GMT
Reason for closing: Fixed
Additional comments about closing: 1.2.1-2
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
lib.patch (0.4 KiB)
https://packages.debian.org/bullseye/bats
https://github.com/Foxboron/archlinux-pkgbuilds/blob/master/bash-bats/PKGBUILD
It seems devtools does not properly set up the environment for the container.
not ok 8 summary passing tests
# (in test file test/bats.bats, line 54)
# `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
not ok 9 summary passing and skipping tests
# (in test file test/bats.bats, line 60)
# `[ "${lines[3]}" = "3 tests, 0 failures, 2 skipped" ]' failed
ok 10 tap passing and skipping tests
not ok 11 summary passing and failing tests
# (in test file test/bats.bats, line 75)
# `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
not ok 12 summary passing, failing and skipping tests
# (in test file test/bats.bats, line 81)
# `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
But it passes through $TERM and when $TERM is not set, it sets it to "unknown".
In my environment $TERM is "xterm-256color".
I can replicate the issues by meddling with $TERM.
https://lists.opensuse.org/opensuse-factory/2017-02/msg00502.html
https://github.com/bats-core/bats-core/issues/201