public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: layman printer trouble
Date: Tue, 9 Oct 2012 18:30:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20121009T202745-685@post.gmane.org> (raw)
In-Reply-To: loom.20121009T200323-969@post.gmane.org

James <wireless <at> tampabay.rr.com> writes:

> 
> Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:
> 
> > Sounds fine up to here. Make sure you have a line "source
> > /var/lib/layman/make.conf" inside your make.conf and try to emerge the
> > driver. It should work then.
> 
> Something is wrong.
> 
> What I have:
> cat /etc/make.conf
> <snip>
> 
> LAYMAN
actually is "##LAYMAN"
> PORTDIR_OVERLAY="/usr/local/portage"
> source /var/lib/layman/make.conf
> 
> SO should this  be (?):
> PORTDIR_OVERLAY="/var/lib/layman"
> 
> cat /var/lib/layman/make.conf:
> ##PORTDIR_OVERLAY="/usr/local/portage"
> 
> PORTDIR_OVERLAY="$PORTDIR_OVERLAY"
> 
> Here is what I get:
> 
> # layman -a printer-drivers
> * Failed to add overlay "printer-drivers".
> * Error was: Overlay "printer-drivers" already in the local list!
> 
> # ls /var/lib/layman/      
> cache_ac494f50f5736be7871962c0dec7b3bb.xml  make.conf.old.layman  
> printer-drivers  make.conf  overlays.xml          zugaina

ls -r /var/lib/layman/printer-drivers/


Documentation  licenses  metadata  net-print  profiles  skel.metadata.xml

/var/lib/layman/printer-drivers/Documentation:
README.txt  bug-snippet.txt

/var/lib/layman/printer-drivers/licenses:
Brother

/var/lib/layman/printer-drivers/metadata:
layout.conf

/var/lib/layman/printer-drivers/net-print:
brother-mfc6490cw-cups  brother-mfc6490cw-lpr  min12xxw

/var/lib/layman/printer-drivers/net-print/brother-mfc6490cw-cups:
Manifest  brother-mfc6490cw-cups-1.1.2_p2.ebuild  metadata.xml

/var/lib/layman/printer-drivers/net-print/brother-mfc6490cw-lpr:
Manifest  brother-mfc6490cw-lpr-1.1.2_p2.ebuild  metadata.xml

/var/lib/layman/printer-drivers/net-print/min12xxw:
Manifest  metadata.xml  min12xxw-0.0.9-r2.ebuild

/var/lib/layman/printer-drivers/profiles:
eapi  repo_name


> ls -R /usr/local/portage/net-print
> 
> brother-mfc6490cw-cups  brother-mfc6490cw-lpr
> 
> ./brother-mfc6490cw-cups:
> Manifest  brother-mfc6490cw-cups-1.1.2_p2.ebuild
> 
> ./brother-mfc6490cw-lpr:
> brother-mfc6490cw-lpr-1.1.2_p2.ebuild
> 
> # eix printer-driver
> No matches found.
> 
> # emerge -pv printer-drivers
> These are the packages that would be merged, in order:
> Calculating dependencies... done!
> emerge: there are no ebuilds to satisfy "printer-drivers".
> 
> Obviously I've got something wrong.....(following too many guides).

Suggestions? Including starting over and following a step
by step howto?


James






  reply	other threads:[~2012-10-09 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 15:38 [gentoo-user] layman printer trouble Jamse
2012-10-05 18:57 ` Hinnerk van Bruinehsen
2012-10-05 19:39   ` [gentoo-user] " James
2012-10-05 21:21     ` Hinnerk van Bruinehsen
2012-10-08 12:52       ` James
2012-10-09 10:08         ` Hinnerk van Bruinehsen
2012-10-09 18:19           ` James
2012-10-09 18:30             ` James [this message]
2012-10-09 18:41             ` Hinnerk van Bruinehsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20121009T202745-685@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox