| 1 |
Burton Samograd <kruhft@×××××××××××××.org> writes: |
| 2 |
|
| 3 |
>> !!! Type "ebuild foo.ebuild digest" to generate a digest. |
| 4 |
>> |
| 5 |
>> Ok, so I tried to do what the error message suggested: |
| 6 |
>> |
| 7 |
>> % emerge ltmodem-8.22.1.5.ebuild digest |
| 8 |
>> Calculating dependencies \!!! doebuild: |
| 9 |
> |
| 10 |
> Read what it said to do and what you typed very carefully :) |
| 11 |
|
| 12 |
Sorry, I should have said that I tried ebuild too and it failed just |
| 13 |
the same (that's why I also tried emerge, just in case): |
| 14 |
|
| 15 |
% ebuild ltmodem-8.22.1.5.ebuild digest |
| 16 |
!!! doebuild: /usr/portage/src/ltmodem/ltmodem-8.22.1.5.ebuild not found. |
| 17 |
portage: aux_get(): (1) couldn't open cache entry for src/ltmodem-8.22.1.5 |
| 18 |
(likely caused by syntax error or corruption in the src/ltmodem-8.22.1.5 ebuild.) |
| 19 |
portage: doebuild(): aux_get() error; aborting. |
| 20 |
|
| 21 |
I don't understand why it is looking for src/ltmodem-8.22.1.5. where |
| 22 |
does the "src" come from? |
| 23 |
|
| 24 |
> Another thing you should do is move your own ebuilds to another |
| 25 |
> directory outside of the main portage tree because they will get |
| 26 |
> deleted every time you do an 'emerge rsync'. This can be done by |
| 27 |
> setting PORTDIR_OVERLAY to a local portage directory structure |
| 28 |
> (/home/user/ebuilds) and put them in there. |
| 29 |
|
| 30 |
Ah!!! this actually worked. Apparently being embedded in an |
| 31 |
appropriate portage directory structure is important. Thanks very |
| 32 |
much. |
| 33 |
|
| 34 |
Cheers, |
| 35 |
|
| 36 |
-- |
| 37 |
Dr. Denys Duchier Denys.Duchier@×××××××××.de |
| 38 |
Forschungsbereich Programmiersysteme (Programming Systems Lab) |
| 39 |
Universitaet des Saarlandes, Geb. 45 http://www.ps.uni-sb.de/~duchier |
| 40 |
Postfach 15 11 50 Phone: +49 681 302 5618 |
| 41 |
66041 Saarbruecken, Germany Fax: +49 681 302 5615 |
Archives