Summary: | [Regression] app-portage/portage-utils-0.1.29+: qatom gives incorrect version number in certain cases | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | P Purkayastha <ppurka> |
Component: | Current packages | Assignee: | Portage Utils Team <portage-utils> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
P Purkayastha
2008-05-14 05:07:26 UTC
(In reply to comment #0) > qatom from app-portage/portage-utils-0.1.29 gives incorrect version number > usually when there is a number in the package name and when we give only the > package name as an argument to qatom. Bug is still present in app-portage/portage-utils-0.4 and corrupts output also if we give some-category/package as an argument. > Reproducible: Always > > Steps to Reproduce: > 1. emerge "=portage-utils-0.1.29" > 2. qatom v86d > 3. > > Actual Results: > (null) v86d 86d > > Expected Results: > (null) v86d (null) > (yet another) Steps to Reproduce 1. qatom dev-python/PyQt4 Actual results 1. dev-python PyQt4 4 Expected results 1. dev-python PyQt4 (null) Further investigation shows that bug concerns packages with number in package name but only if this number is last or penultimate char. Qatom produces buggy output at for example: * number as penultimate char of package name: app-arch/q7z app-cdr/k3b www-client/w3m sys-fs/ntfs3g * number as ultimate char of package name: x11-base/xorg-x11 x11-libs/libX11 sys-apps/memtest86 Currently there are 478 packages in official portage tree that are connected with this issue. |