Search Criteria
Package Details: bashate 2.1.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/bashate.git (read-only, click to copy) |
---|---|
Package Base: | bashate |
Description: | Code style enforcement for bash programs |
Upstream URL: | https://github.com/openstack/bashate |
Licenses: | Apache |
Submitter: | christoph.gysin |
Maintainer: | christoph.gysin |
Last Packager: | christoph.gysin |
Votes: | 5 |
Popularity: | 0.000000 |
First Submitted: | 2015-06-25 08:07 (UTC) |
Last Updated: | 2022-12-10 07:17 (UTC) |
Dependencies (3)
- python (python37AUR, python311AUR, python310AUR)
- python-pbr
- python-setuptools (make)
Latest Comments
1 2 Next › Last »
Sathors commented on 2021-10-11 20:04 (UTC)
Perfect @christoph.gysin, I've just tried it and everything is working great now. It also installs fine using
yay
. Thanks for the really fast fix.christoph.gysin commented on 2021-10-11 19:53 (UTC)
@Sathors Thanks for the update. The issue seems to be triggered if the build step is called in a directory that is not part of a git repository. Fixed in 2.1.0-2.
Sathors commented on 2021-10-11 19:19 (UTC) (edited on 2021-10-11 19:19 (UTC) by Sathors)
@christoph.gysin I have updated my previous comment to paste the error there. I was missing the double spaces at the end of each line to preserve the newlines.
To build it, I download the snapshot of the package (https://aur.archlinux.org/cgit/aur.git/snapshot/bashate.tar.gz), I extract the .tar.gz archive, I run
makepkg --syncdeps --rmdeps --install --clean
in the root of the directory (which contains the PKGBUILD) and then I stumble upon the error.christoph.gysin commented on 2021-10-11 17:53 (UTC)
@Sathors Please check how to properly format your comment with markdown. Then provide detailed steps to reproduce the problem. It builds fine for me.
Sathors commented on 2021-10-11 17:42 (UTC) (edited on 2021-10-11 19:14 (UTC) by Sathors)
With this version I have the same problem I had with the previous version, namely a "Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name bashate was given, but was not able to be found."
Thanks
christoph.gysin commented on 2017-03-25 09:46 (UTC)
dracorp commented on 2017-03-15 15:21 (UTC)
christoph.gysin commented on 2016-08-28 15:39 (UTC)
kseistrup commented on 2016-08-28 15:08 (UTC) (edited on 2016-08-28 15:11 (UTC) by kseistrup)
christoph.gysin commented on 2016-08-28 14:41 (UTC)
1 2 Next › Last »