RE:

Thanks, that’s the trick I was looking for.
I knew bugzilla wasn't keyworded for Alpha, and wanted to test it anyway.
The Gentoo handbook isn't very clear on this subject.  It seemed to imply that I
only needed the package.unmask and package.keywords files set.

Brian..


Quoting "Nils o. Janus" <[email protected]>:

> 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.
>
> Nils
> ---- Ursprüngliche Nachricht -----
>     Von: "Brian C. Parkhurst"<[email protected]>
>     Gesendet: 20.09.05 20:09:45
>     An: "[email protected]"<[email protected]>
>     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
>     >=www-apps/bugzilla-2*
>
>     # cat package.keywords
>     >=www-apps/bugzilla-2* ~alpha
>
>     Any thoughts?
>
>     Brian
>
>     [email protected]
>
>     --
>     Brian Parkhurst
>
> --
> [email protected] mailing list
>
>