Next ebuilds have joined keywords (like `~sh~sparc`) dev-cpp", "clucene", "2.3.3.4-r3 perl-core", "Parse-CPAN-Meta", "1.440.200 virtual", "mysql", "5.5 virtual", "awk", "0 Accordingly to PMS KEYWORDS is 'A whitespace separated list of keywords for the ebuild.' Reproducible: Always Can we have some kind of hook to prevent bugs like these?
(In reply to comment #0) > Next ebuilds have joined keywords (like `~sh~sparc`) > > dev-cpp", "clucene", "2.3.3.4-r3 KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos" Looks fine. > perl-core", "Parse-CPAN-Meta", "1.440.200 KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~ppc-aix ~x86-fbsd ~x64-freebsd ~x86-freebsd ~x86-interix ~amd64-linux ~ia64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris" Looks fine. > virtual", "mysql", "5.5 KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~sparc-fbsd ~x86-fbsd" It's fine. > virtual", "awk", "0 KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd ~x86-macos" > Accordingly to PMS KEYWORDS is 'A whitespace separated list of keywords for > the ebuild.' Whitespace in this context means spaces, newlines and various tabs. > Can we have some kind of hook to prevent bugs like these? I don't see a bug here. I'll patch you through to the PMS people to maybe get the wording clarified.
Yes all is OK. Sorry, it was my bug. :(