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#34726 - [namcap] cannot parse 4.1 pacman.conf file
Attached to Project:
Arch Linux
Opened by Brian BIdulock (bidulock) - Thursday, 11 April 2013, 04:39 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 April 2013, 07:29 GMT
Opened by Brian BIdulock (bidulock) - Thursday, 11 April 2013, 04:39 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 April 2013, 07:29 GMT
|
DetailsDescription:
namcap crahses on default 4.1 pacman.conf Additional info: * version 3.2.4-2 Steps to reproduce: Use default 4.1 pacman.conf file. namcap PKGBUILD # (any PKGBUILD) /usr/lib/python3.3/site-packages/pycman/config.py:125: InvalidSyntax: unable to parse /etc/pacman.conf, unrecognized option: 'LocalFileSigLevel' Workaround: Comment out LocalFileSigLevel in /etc/pacman.conf |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 11 April 2013, 07:29 GMT
Reason for closing: Duplicate
Additional comments about closing: https://bugs.archlinux.org/task/34591
Thursday, 11 April 2013, 07:29 GMT
Reason for closing: Duplicate
Additional comments about closing: https://bugs.archlinux.org/task/34591