BACKGROUND
----------

OK, so I get a new Brother MFC-6710DW printer, which
includes ethernet. Since there is not (hplip) package
for Brother, I trying to use Layman to first add
an existing Overlay and then set up the printer
via Cups (localhost:631).

Amazingly, I found an overlay that looks to be for a brother
printer that is identical to mine, except it down not
have the memory stick slot (brother mfc6490cw).

Here it is on zugaina
(Successfully synchronized overlay "zugaina")

http://gpo.zugaina.org/Overlays/printer-drivers/
net-print/brother-mfc6490cw-cups

I thought once that layman is setup you could just update
the tree_list of packages (which I did) and then just
use emerge to install from a give Overlay repository?
(Yes, I modifies the /etc/make.conf

#LAYMAN
PORTDIR_OVERLAY="/usr/local/portage"
source /var/lib/layman/make.conf
(but this layman make.conf file is still empty)

So, I get this error:
# layman -f -a net-print/brother-mfc6490cw-cups-1.1.2_p2

Overlay "net-print/brother-mfc6490cw-cups-1.1.2_p2" does not exist.
(I also tried the name "net-print/brother-mfc6490cw-cups" to no avail)

Next, I've manually downloaded the ebuild to:
/usr/local/portage/net-print/brother-mfc6490cw-cups/



PROBLEM
-------
But I cannot use emerge to install it.
# emerge brother-mfc6490cw-cups
Calculating dependencies / * Manifest not found for
'/usr/local/portage/net-print/brother-mfc6490cw-cups/
brother-mfc6490cw-cups-1.1.2_p2.ebuild'

So now I need to hack the manifest and other files into this dir?
Any discussion, ideas, syntax or ebuild support files
(manifest et. al) are most welcome (Neil?)

Note: it's been a while since I've used the laymen scripts et. al.
so it's entirely possible I missed (fudged_up) the steps I gleaned
from the myriad of wikis to do this install.

rusty on Overlays,
James

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05.10.2012 17:38, Jamse wrote:
> BACKGROUND ----------
>
> OK, so I get a new Brother MFC-6710DW printer, which includes
> ethernet. Since there is not (hplip) package for Brother, I trying
> to use Layman to first add an existing Overlay and then set up the
> printer via Cups (localhost:631).
>
> Amazingly, I found an overlay that looks to be for a brother
> printer that is identical to mine, except it down not have the
> memory stick slot (brother mfc6490cw).
>
> Here it is on zugaina (Successfully synchronized overlay
> "zugaina")
>
> http://gpo.zugaina.org/Overlays/printer-drivers/
> net-print/brother-mfc6490cw-cups
>
> I thought once that layman is setup you could just update the
> tree_list of packages (which I did) and then just use emerge to
> install from a give Overlay repository? (Yes, I modifies the
> /etc/make.conf
>
> #LAYMAN PORTDIR_OVERLAY="/usr/local/portage" source
> /var/lib/layman/make.conf (but this layman make.conf file is still
> empty)
>
> So, I get this error: # layman -f -a
> net-print/brother-mfc6490cw-cups-1.1.2_p2
>
> Overlay "net-print/brother-mfc6490cw-cups-1.1.2_p2" does not
> exist. (I also tried the name "net-print/brother-mfc6490cw-cups" to
> no avail)
>
> Next, I've manually downloaded the ebuild to:
> /usr/local/portage/net-print/brother-mfc6490cw-cups/
>
>
>
> PROBLEM ------- But I cannot use emerge to install it. # emerge
> brother-mfc6490cw-cups Calculating dependencies / * Manifest not
> found for '/usr/local/portage/net-print/brother-mfc6490cw-cups/
> brother-mfc6490cw-cups-1.1.2_p2.ebuild'
>
> So now I need to hack the manifest and other files into this dir?
> Any discussion, ideas, syntax or ebuild support files (manifest et.
> al) are most welcome (Neil?)
>
> Note: it's been a while since I've used the laymen scripts et. al.
> so it's entirely possible I missed (fudged_up) the steps I gleaned
> from the myriad of wikis to do this install.
>
> rusty on Overlays, James
>

Hi James,

you'll have to add the complete overlay, e.g.:


layman -a printer-drivers

Afterwards you should be able to install the driver. The alternative
route would be to set up your own overlay. If you put a file inside
the normal portage tree, it will be removed after the next sync.
To create a Manifest you could issue "ebuild <path/to/foobar.ebuild>
manifest" but as stated above it would be removed on the next sync, if
you don't setup your own overlay. The easiest way would be to simply
add the overlay with "layman -a <overlayname>". If I recall correctly
you'll have to update the list of available overlays before doing so
via "layman -L"

WKR
Hinnerk



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQby2tAAoJEJwwOFaNFkYcVRUIAIr59Av0eL Ad2arl4YqBKhlI
KCXeTa/mgFEmu1KhxCotrXm8KspFHsXxl8zUXZpxusvE/vMaao4m0lJd1j1Ifjhl
CEWT3kcotPVo9PLGh6faTsZMjzvbm4MgIVzYowA2Gf/TsLPo/Bc21ho9wP1zOX0M
BE8ES/f3orftDzyGFysgAxNzdKMnpeDFCxtJGNMHCcQHn1YBAWtKP09e +XeHjOD1
3cN7UfSa5IuNXbS7lT+I9oP50kl/dImyYf+mAbvjLqopd86TlavpSWEOn1lnxKKx
iZq3rggdQb9TZRDY80xTRACSJ9JxfQbvkqzulDLrZXY57McazX 5Ky1UHmgCq9T8=
=SWN8
-----END PGP SIGNATURE-----

Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:


> > PROBLEM ------- But I cannot use emerge to install it. # emerge
> > brother-mfc6490cw-cups Calculating dependencies / * Manifest not
> > found for '/usr/local/portage/net-print/brother-mfc6490cw-cups/
> > brother-mfc6490cw-cups-1.1.2_p2.ebuild'

> > So now I need to hack the manifest and other files into this dir?
> > Any discussion, ideas, syntax or ebuild support files (manifest et.
> > al) are most welcome (Neil?)


> layman -a printer-drivers
I have /usr/local/portage/net-print/brother-mfc6490cw-cups
set up

I did generate the ebuild manifest by hand:

# ebuild brother-mfc6490cw-cups-1.1.2_p2.ebuild manifest
<snip>
2012-10-05 14:45:35 (653 KB/s) -
`/usr/portage/distfiles/mfc6490cwcupswrapper-1.1.2-2.i386.rpm'
saved [15650/15650]

Creating Manifest for
/usr/local/portage/net-print/brother-mfc6490cw-cups

> Afterwards you should be able to install the driver. >

This file is empty, but exists:
cat /var/lib/layman/make.conf <empty>
what should be in this file?

# layman -a printer-drivers

* Running... # /usr/bin/git clone
git://git.overlays.gentoo.org/proj/printer-drivers.git
/var/lib/layman/printer-drivers
Cloning into '/var/lib/layman/printer-drivers'...
remote: Counting objects: 38, done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 38 (delta 7), reused 0 (delta 0)
Receiving objects: 100% (38/38), 8.57 KiB, done.
Resolving deltas: 100% (7/7), done.
* Failed to add overlay "printer-drivers".
* Error was: Did not find a PORTDIR_OVERLAY entry in file
/var/lib/layman/make.conf! Did you specify the correct file?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05.10.2012 21:39, James wrote:
> Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:
>
>
>>> PROBLEM ------- But I cannot use emerge to install it. #
>>> emerge brother-mfc6490cw-cups Calculating dependencies / *
>>> Manifest not found for
>>> '/usr/local/portage/net-print/brother-mfc6490cw-cups/
>>> brother-mfc6490cw-cups-1.1.2_p2.ebuild'
>
>>> So now I need to hack the manifest and other files into this
>>> dir? Any discussion, ideas, syntax or ebuild support files
>>> (manifest et. al) are most welcome (Neil?)
>
>
>> layman -a printer-drivers
> I have /usr/local/portage/net-print/brother-mfc6490cw-cups set up
>
> I did generate the ebuild manifest by hand:
>
> # ebuild brother-mfc6490cw-cups-1.1.2_p2.ebuild manifest <snip>
> 2012-10-05 14:45:35 (653 KB/s) -
> `/usr/portage/distfiles/mfc6490cwcupswrapper-1.1.2-2.i386.rpm'
> saved [15650/15650]
>
> Creating Manifest for
> /usr/local/portage/net-print/brother-mfc6490cw-cups
>
>> Afterwards you should be able to install the driver. >
>
> This file is empty, but exists: cat /var/lib/layman/make.conf
> <empty> what should be in this file?
>
> # layman -a printer-drivers
>
> * Running... # /usr/bin/git clone
> git://git.overlays.gentoo.org/proj/printer-drivers.git
> /var/lib/layman/printer-drivers Cloning into
> '/var/lib/layman/printer-drivers'... remote: Counting objects: 38,
> done. remote: Compressing objects: 100% (32/32), done. remote:
> Total 38 (delta 7), reused 0 (delta 0) Receiving objects: 100%
> (38/38), 8.57 KiB, done. Resolving deltas: 100% (7/7), done. *
> Failed to add overlay "printer-drivers". * Error was: Did not find
> a PORTDIR_OVERLAY entry in file /var/lib/layman/make.conf! Did you
> specify the correct file?
>
>

Ok - you're trying two different approaches at the same time. I'd
recommend you to just use the printer-drivers overlay.

Normally layman should take care of the contents of
/var/lib/layman/make.conf. Maybe it doesn#t work because you created
an empty one. You could try to simply delete it and afterwards rerun
layman -a printer-drivers. If that doesn't solve your problem,
recreate the file with the following content:

PORTDIR_OVERLAY="
$PORTDIR_OVERLAY
"

Afterwards try layman -a printer-drivers again.

WKR
Hinnerk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQb09RAAoJEJwwOFaNFkYc99AH/RMbGP873Y64ZnuDDwPu9kuk
K9NzfMuhyvmSkLpJPhwuAfm0IPDPDqe7HJWb6CjSTyfW/FWaXTgp2kbAoszGLQ+I
slQXzEbs+0n176rN9YZlyu6CuWLh/istY6KtO2wkDH9g2uj4KeKzdB4wmWqFckUw
ZCBMNqqwlkO09eN214kNmpwmzc0lobahQetEHg3NWMFQ92m4nj yAQh8lzmKSKGnO
biE8ZC1QvwJZY6OJTVzF9m5DQboeDeOkRG2XIZ0FDyelysaXoj kpTPkMkMXFdbZ5
uR0IVfpqII7hPNMGgY8G+0gfkPTiV42gSNZaG+Jc2iFMb2YOPs m80jKcKd2i3/I=
=pVfT
-----END PGP SIGNATURE-----

Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:


> Ok - you're trying two different approaches at the same time. I'd
> recommend you to just use the printer-drivers overlay.

Yep know doubts, I looked at too many different wiki and other googled
resources. I could not find a simple here are the steps to installing
"printer" overlays, compiling them, making the config changes and
then testing via CUPS.

OK, I'll the print drivers first.

> Normally layman should take care of the contents of
> /var/lib/layman/make.conf. Maybe it doesn#t work because you created
> an empty one. You could try to simply delete it and afterwards rerun
> layman -a printer-drivers. If that doesn't solve your problem,
> recreate the file with the following content:

> PORTDIR_OVERLAY=" $PORTDIR_OVERLAY"

> Afterwards try layman -a printer-drivers again.

#layman -l
* printer-drivers [Git ]
(git://git.o.g.o/proj/printer-drivers.git )
* zugaina [Rsync ]
(rsync://gentoo.zugaina.org/zugaina-portage )

OK it's installed. I would think emerging it is next?
But that does not seem to work with emerge?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08.10.2012 14:52, James wrote:
> Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:
>
>
>> Ok - you're trying two different approaches at the same time.
>> I'd recommend you to just use the printer-drivers overlay.
>
> Yep know doubts, I looked at too many different wiki and other
> googled resources. I could not find a simple here are the steps to
> installing "printer" overlays, compiling them, making the config
> changes and then testing via CUPS.
>
> OK, I'll the print drivers first.
>
>> Normally layman should take care of the contents of
>> /var/lib/layman/make.conf. Maybe it doesn#t work because you
>> created an empty one. You could try to simply delete it and
>> afterwards rerun layman -a printer-drivers. If that doesn't solve
>> your problem, recreate the file with the following content:
>
>> PORTDIR_OVERLAY=" $PORTDIR_OVERLAY"
>
>> Afterwards try layman -a printer-drivers again.
>
> #layman -l * printer-drivers [Git ]
> (git://git.o.g.o/proj/printer-drivers.git ) * zugaina
> [Rsync ] (rsync://gentoo.zugaina.org/zugaina-portage )
>
> OK it's installed. I would think emerging it is next? But that does
> not seem to work with emerge?

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.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQc/elAAoJEJwwOFaNFkYccQgH/j5PPQOOLoz04NmohiiqpSCQ
6xZ6X3qq1KgzUlJOXnQ2YnQpbaVGB1vTGddXCxytPfqSucCVFW CZkP/HsqrShWss
f7u2SaXmTP4TDoqx0tFpyReRhhv7hZATcGH9PpWVc+G8iSnyB5 HJZOVzWFhPow/9
xXE3YxdKvEYPnru+LwjOBBVQJ1ktRsHbi2j6nQm5LTcZtSOrUq +OeEpRru5uswv5
ALruHbz8o90DeQycMyjXaDnwMcQ2o9IIdarVWSTaaxhCONB4OX C4XJ7egOJdC+Qa
DUB0myfNwKInn7hoqVV2cZys4tOIJ/+imiz0BYEKJR72roKm7B/chKFunWlooSE=
=e0Eu
-----END PGP SIGNATURE-----

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
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 /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).

Ideas?


James

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09.10.2012 20:19, James wrote:
> 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 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 /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).
>
> Ideas?
>
Step 1: remove anything layman/overlay-related from /etc/make.conf
except:
source /var/lib/layman/make.conf

Step 2:
layman -d printer-drivers
layman -a printer-drivers

Now the printer-drivers-overlay should be installed correctly.
Check if /var/lib/layman/make.conf contains:

PORTDIR_OVERLAY="
/var/lib/layman/printer-drivers
$PORTDIR_OVERLAY
"

maybe it has got other newlines or indentation, but the contents
should be this. If not, though something's strange then, try edit the
file manually to make it look like this.

Try:
emerge <ebuild-name>

It should work then.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQdG/rAAoJEJwwOFaNFkYcwyUIAMMvb8MFGBaFw2H8RnYvcw2N
AE+F+CqC0G7/uA05y/TN6sPQA94hqG0YiThzTx/KsenC+o5CBrCSsJnAss4lOyp3
auzuAyHS4hHCyKCEGFccqsymD0tjtEr+NnJkxpFr9KVo+Pgd0+ 6tmQn/z9W9NeSi
JXDKpuHvKaURQy5hxha8kr6cIxzAFpCDYEKnttCBgCQzH2jLzg uwFBlozWTNPa5L
aZ49XdmhMliwPs9YfVEj0587qqUZyDoGw0n63r+q0KHcup6LJ+ agu1FuQSdQINKX
ovjpBFk+D+FV0fLD5nFjgAXOYL2PXFC9LtnVcZ4BI9K3F+Wizc d8FCQyMYk/mbw=
=H312
-----END PGP SIGNATURE-----