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#23260 - [namcap] AttributeError: 'PacmanPackage' object has no attribute 'version'
Attached to Project:
Arch Linux
Opened by xduugu (xduugu) - Sunday, 13 March 2011, 14:40 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Sunday, 13 March 2011, 15:29 GMT
Opened by xduugu (xduugu) - Sunday, 13 March 2011, 14:40 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Sunday, 13 March 2011, 15:29 GMT
|
DetailsThe new namcap 3.0 throws an error when run on some packages. One package that triggers that error is glibc. It does not seem to be related to the compression since it also occurs on gzip'd files.
$ namcap /home/pkgcache/glibc-2.13-4-x86_64.pkg.tar.xz Traceback (most recent call last): File "/usr/lib/python3.2/runpy.py", line 160, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python3.2/runpy.py", line 73, in _run_code exec(code, run_globals) File "/usr/lib/python3.2/site-packages/namcap.py", line 274, in <module> process_realpackage(package, active_modules) File "/usr/lib/python3.2/site-packages/namcap.py", line 128, in process_realpackage rule.analyze(pkginfo, pkgtar) File "/usr/lib/python3.2/site-packages/Namcap/rules/shebangdepends.py", line 125, in analyze if p != None and q != None and p.version == q.version: AttributeError: 'PacmanPackage' object has no attribute 'version' |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Sunday, 13 March 2011, 15:29 GMT
Reason for closing: Fixed
Additional comments about closing: To be released in version 3.0.1
Sunday, 13 March 2011, 15:29 GMT
Reason for closing: Fixed
Additional comments about closing: To be released in version 3.0.1
Comment by Rémy Oudompheng (remyoudompheng) -
Sunday, 13 March 2011, 15:21 GMT
Fix is ready to be applied, thanks for the report.