-----BEGIN PGP SIGNED MESSAGE-----
Nils o. Janus wrote:
> Hi Brian,
> Check in the .ebuild files of bugzilla, wether the keyword ~alpha is entered there. If not, then inserting ~alpha into packages.keywords isnt sufficient.
> Either pass the complete path of the ebuild to emerge like 'emerge www-apps/bugzilla/bugzilla-version-xxx.ebuild', or edit the .ebuild file manually, insert the keyword alpha, run 'ebuild www-apps/bugzilla/bugzilla-version-xxx.ebuild digest' and emerge as usual.
Emerging packages by path is depreciated, do not do this. Editing the
.ebuild in overlay would work, but is not necessary. Instead in
/etc/portage/package.keywords add =CAT/PKG-VER ~* ~alpha
That should keyword it properly. If it doesn't respond and I'll look
into why it isn't working. It should though because I did it earlier
today on ppc ;)
> ---- Ursprüngliche Nachricht -----
> Von: "Brian C. Parkhurst"<brianp@×××××××.net>
> Gesendet: 20.09.05 20:09:45
> An: "email@example.com"<firstname.lastname@example.org>
> Betreff: [gentoo-alpha]
> I wanted to give bugzilla a chance on my alpha-AS800 but can't seem to get my
> unmask flags right.
> # emerge -puvD bugzilla
> These are the packages that I would merge, in order:
> Calculating dependencies
> !!! All ebuilds that could satisfy "bugzilla" have been masked.
> !!! One of the following masked packages is required to complete your request:
> - www-apps/bugzilla-2.20_rc2 (masked by: missing keyword)
> - www-apps/bugzilla-2.18.3 (masked by: missing keyword)
> - www-apps/bugzilla-2.20_rc1 (masked by: missing keyword)
> For more information, see MASKED PACKAGES section in the emerge man page or
> section 2.2 "Software Availability" in the Gentoo Handbook.
> # cat package.unmask
> # cat package.keywords
> >=www-apps/bugzilla-2* ~alpha
> Any thoughts?
> Brian Parkhurst