I just noticed earlier, that the table with the stable/testing versions available seems to not be up2date as an example app-antivirus/clamav: 1) it shows only amd64,x86 and sparc as testing(yellow) and the rest white when the ebuild says this: KEYWORDS="~amd64 ~ia64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x86-solaris" (it got ia64 keyworded recent6ly) 2) for 0.99.4-r1 it doesn't show that hppa stabilized it
as suggested on IRC CC'ing antarus
(In reply to Thomas Raschbacher from comment #0) > I just noticed earlier, that the table with the stable/testing versions > available seems to not be up2date > > as an example app-antivirus/clamav: > 1) it shows only amd64,x86 and sparc as testing(yellow) and the rest white > when the ebuild says this: KEYWORDS="~amd64 ~ia64 ~sparc ~x86 ~x86-fbsd > ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x86-solaris" (it got ia64 > keyworded recent6ly) > 2) for 0.99.4-r1 it doesn't show that hppa stabilized it So either the package object doesn't have the version (possible) or the link_version_to_ebuild is broken. I suspect the former due to over-eager dynamic content additions in ES. I think we need to modify the index to not auto-add fields, re-index and see if we can keep the site working that way. This will probably take some time for me to fix. -A
I would like to take a closer look at this issue, if you know of any existing package with this issue, please share.
We have since rewritten the app. -A
