1 |
On Tue, 2010-06-29 at 19:51 +0800, Chen Huan wrote: |
2 |
> I had done some hack on jabberd2, and I make a new ebuild for it, To |
3 |
> avoid |
4 |
> the new ebuild being overwrite when I execute "emerge --sync", I make |
5 |
> /var/lib/layman/myown for this ebuild |
6 |
> |
7 |
> when I emerged jabberd2, it's normal, but when I try to re-merge it, |
8 |
> the |
9 |
> output is : |
10 |
> |
11 |
> Calculating dependencies... done! |
12 |
> [ebuild R ] net-im/jabberd2-2.2.8 USE="berkdb ldap mysql pam ssl |
13 |
> zlib |
14 |
> -debug -memdebug -postgres -sqlite" 0 kB [?=>1] |
15 |
> |
16 |
> Total: 1 package (1 reinstall), Size of downloads: 0 kB |
17 |
> Portage tree and overlays: |
18 |
> [0] /usr/portage |
19 |
> [1] /var/lib/layman/myown |
20 |
> [?] indicates that the source repository could not be determined |
21 |
|
22 |
It's saying jabberd is being rebuilt, and orginally it was build from a |
23 |
repo that is ownknown, and now it will be built |
24 |
from /usr/lib/layman/myown. |
25 |
|
26 |
Did you previously rename your repo or pass PORTDIR_OVERLAY from the |
27 |
command line (which can sometimes confuse portage). |