On Wednesday, 15 August 2018 09:50:09 BST Franz Fellner wrote:
> 
> Am Mi., 15. Aug. 2018 um 11:29 Uhr schrieb Peter Humphrey <
> 
> [email protected]>:
> > Hello list,
> > 
> > While trying to get a USB printer recognised on an Atom box, I found
> > this, immediately after emerge --sync && eix-update:
> > 
> > (atom) peak / # eix -c kyocera
> > [N] net-print/kyocera-1x2x-mfp-driver (--): Printer descriptions (PPDs)
> > and filters for Kyocera 1x2x MFP
> > [N] net-print/kyocera-mita-ppds ((~)8.4-r1{tbz2}): PPD description files
> > for (some) Kyocera Mita Printers
> > Found 2 matches
> > 
> > (atom) peak / # emerge -pv net-print/kyocera-1x2x-mfp-driver
> > net-print/kyocera-mita-ppds
> > 
> > These are the packages that would be merged, in order:
> > 
> > Calculating dependencies  ... done!
> > 
> > !!! All ebuilds that could satisfy "net-print/kyocera-1x2x-mfp-driver"
> > have been masked.
> > !!! One of the following masked packages is required to complete your
> > request:
> > - net-print/kyocera-1x2x-mfp-driver-1.1203-r1::gentoo (masked by:
> > missing keyword)
> > 
> > (atom) peak / # grep kyocera /etc/portage/package.keywords
> > net-print/kyocera-1x2x-mfp-driver
> > net-print/kyocera-mita-ppds
> > 
> > I wonder whether the "1x2x" is confusing portage.

> It's ~amd64 only. So if you get missing keyword, could it be you are on
> x86?

This is an X86 box (Atom N270), but it's more complex than that:

(atom) peak / # equery w net-print/kyocera-1x2x-mfp-driver
!!! No packages matching 'net-print/kyocera-1x2x-mfp-driver'
(atom) peak / # ls -l /usr/portage/net-print/kyocera-1x2x-mfp-driver
total 7.0K
drwxr-xr-x 2 portage portage 1.0K Sep  6  2017 files
-rw-r--r-- 1 portage portage 3.4K Jan 15  2018 
kyocera-1x2x-mfp-driver-1.1203-r1.ebuild
-rw-r--r-- 1 portage portage  317 Dec 12  2017 Manifest
-rw-r--r-- 1 portage portage  529 Sep  6  2017 metadata.xml

Thus my usual use of portage tools failed, so I didn't get as far as seeing
this:

(atom) peak / # grep KEYWORDS 
/usr/portage/net-print/kyocera-1x2x-mfp-driver/*ebuild
KEYWORDS="-* ~amd64"

Something does seem to be, if not broken, somewhat bent.

-- 
Regards,
Peter.




Reply via email to