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#17715 - [namcap] crashes on checking kbibtex package from AUR
Attached to Project:
Arch Linux
Opened by Arvid Norlander (AnMaster) - Tuesday, 05 January 2010, 20:29 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 07 February 2010, 13:33 GMT
Opened by Arvid Norlander (AnMaster) - Tuesday, 05 January 2010, 20:29 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 07 February 2010, 13:33 GMT
|
DetailsDescription:
I was installing kbibtex from AUR with yaourt and selected the option to check with namcap. To my surprise after a few seconds a traceback was printed from namcap: Traceback (most recent call last): File "/usr/bin/namcap", line 232, in <module> process_realpackage(package, active_modules) File "/usr/bin/namcap", line 129, in process_realpackage show_messages(pkginfo.name, 'W', ret[1]) File "/usr/bin/namcap", line 94, in show_messages print "%s %s: %s" % (name, key, m(msg[0]) % msg[1]) File "/usr/bin/namcap", line 79, in <lambda> return lambda s: tags[s] KeyError: 'L' I have saved the binary package and the build directory (considering what happened I decided to not install it), and can provide any of that on request (not sure you want a binary package attached). System is x86_64 in case that matters. All packages up-to-date as of 2010-01-05 20:00 UTC. The issue does not seem to affect any other package (tried a few). It is reproducible without using yaourt (see below). Additional info: * package version(s): namcap is version 2.4-1 * Config files: Which ones are you interested in? Steps to reproduce: 1. Get kbibtex from AUR. 2. Build it with makepkg -c 3. Run namcap on the resulting package. Notice that namcap exits with a traceback. Supposedly not supposed to happen even for (possibly) bad packages. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Sunday, 07 February 2010, 13:33 GMT
Reason for closing: Works for me
Additional comments about closing: cannot reproduce
Sunday, 07 February 2010, 13:33 GMT
Reason for closing: Works for me
Additional comments about closing: cannot reproduce
Will try on x86_64.
Using python 2.6.4-2.
Output of running namcap kbibtex-0.2.3-1-x86_64.pkg.tar.gz:
kbibtex W: Dependency included but already satisfied ('qt3')
kbibtex E: ELF file (opt/kde/lib/kde3/libkbibtexpart.so) outside of a valid path.
kbibtex E: ELF file (opt/kde/bin/kbibtex) outside of a valid path.
kbibtex W: Potential non-FHS man page (opt/kde/share/man) found.
kbibtex W: Potential non-FHS man page (opt/kde/share/man/man1) found.
kbibtex W: Potential non-FHS man page (opt/kde/share/man/man1/kbibtex.1) found.
kbibtex W: File (opt/kde/lib/kde3/libkbibtexpart.la) is a libtool file.
kbibtex E: Symlink (opt/kde/share/doc/HTML/en/kbibtex/common) points to non-existing /opt/kde/share/doc/HTML/en/common
kbibtex E: Insecure RPATH (opt/kde/lib/kde3/libkbibtexpart.so). If present, RPATH should be only /usr/lib.
kbibtex E: Insecure RPATH (opt/kde/bin/kbibtex). If present, RPATH should be only /usr/lib.
Package versions.
python 2.6.4-2
namcap 2.4-1
kbibtex 0.2.3-1