Package Details: yamllint 1.12.1-2

Git Clone URL: (read-only)
Package Base: yamllint
Description: A linter for YAML files.
Upstream URL:
Keywords: linter yaml
Licenses: GPLv3
Submitter: lilydjwg
Maintainer: lilydjwg (lilac)
Last Packager: lilac
Votes: 12
Popularity: 1.473772
First Submitted: 2016-06-24 09:33
Last Updated: 2018-10-19 12:05

Latest Comments

lilydjwg commented on 2018-10-20 09:49

polyzen: I will use predictable urls in the future.

polyzen commented on 2018-10-19 15:53

lilydjwg commented on 2018-10-19 04:49

polyzen: do you know the source url will always be in that format for all PyPI packages?

polyzen commented on 2018-10-18 05:49

To make things easier, please change the source to: source=("<>${pkgname::1}/$pkgname/$pkgname-$pkgver.tar.gz")

Please also run the tests: checkdepends=('python-nose')

check() {
  cd $pkgname-$pkgver
  python -m unittest discover tests

lilydjwg commented on 2017-08-04 01:03

psychoteadrink: it's fixed. However you'll wait python-pathspec to update if you use the AUR version.

psychoteadrink commented on 2017-08-03 11:49

Traceback (most recent call last):
File "/usr/bin/yamllint", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 3038, in <module>
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 3022, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 3051, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 657, in _build_master
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 971, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.6/site-packages/pkg_resources/", line 857, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pathspec>=0.5.3' distribution was not found and is required by yamllint

polyzen commented on 2017-02-28 03:26

I don't recall having seen it before.

It's removed, on my side.

lilydjwg commented on 2017-02-28 03:20

polyzen: because I added it to my template. Some packages need a UTF-8 locale.
Does it cause any problem for you?

polyzen commented on 2017-02-27 20:50

Why has `export LANG=en_US.UTF-8` been added?