Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61960 - [proselint] check() returns failed tests
Attached to Project:
Community Packages
Opened by Andreas Baumann (andreas_baumann) - Saturday, 09 March 2019, 09:06 GMT
Last edited by Daniel M. Capella (polyzen) - Sunday, 10 March 2019, 06:52 GMT
Opened by Andreas Baumann (andreas_baumann) - Saturday, 09 March 2019, 09:06 GMT
Last edited by Daniel M. Capella (polyzen) - Sunday, 10 March 2019, 06:52 GMT
|
DetailsDescription:
... === 3 failed, 140 passed, 1 skipped, 2 xfailed, 43 warnings in 12.32 seconds === ... Additional info: * package version(s): 0.10.2-4 Steps to reproduce: asp export proselint cd proselint staging-x86_64-build 
log.txt
(68 KiB)
|
This task depends upon
Closed by Daniel M. Capella (polyzen)
Sunday, 10 March 2019, 06:52 GMT
Reason for closing: Upstream
Additional comments about closing: The proselint package seems to work properly. Looks like this will be fixed once upstream updates its dependencies, and would presumably not be an issue once the next release is ready to be packaged. If anything, file an issue upstream so this will be fixed sooner than later.
Sunday, 10 March 2019, 06:52 GMT
Reason for closing: Upstream
Additional comments about closing: The proselint package seems to work properly. Looks like this will be fixed once upstream updates its dependencies, and would presumably not be an issue once the next release is ready to be packaged. If anything, file an issue upstream so this will be fixed sooner than later.
Comment by Daniel M. Capella (polyzen) -
Saturday, 09 March 2019, 11:10 GMT
Problems persist even on the latest commit. Will look into it tomorrow.