ok, I got it after add a file "repo_name" to /var/lib/layman/myown, the warning message disappeared
thanks very much 2010/6/29 Chen Huan <chenhu...@gmail.com> > thanks > > previously jabberd2 is being merged from my own overlay too > > in /var/lib/layman/myown, I just make the directory net-im/jabberd2/, there > is no other things in /var/lib/layman/myown > > Should I add some other things to the directory of my own overlay?? > > > > Did you previously rename your repo or pass PORTDIR_OVERLAY from the > command line (which can sometimes confuse portage). > === > No, i didn't do anything like that > > 2010/6/29 Albert Hopkins <mar...@letterboxes.org> > > On Tue, 2010-06-29 at 19:51 +0800, Chen Huan wrote: >> > I had done some hack on jabberd2, and I make a new ebuild for it, To >> > avoid >> > the new ebuild being overwrite when I execute "emerge --sync", I make >> > /var/lib/layman/myown for this ebuild >> > >> > when I emerged jabberd2, it's normal, but when I try to re-merge it, >> > the >> > output is : >> > >> > Calculating dependencies... done! >> > [ebuild R ] net-im/jabberd2-2.2.8 USE="berkdb ldap mysql pam ssl >> > zlib >> > -debug -memdebug -postgres -sqlite" 0 kB [?=>1] >> > >> > Total: 1 package (1 reinstall), Size of downloads: 0 kB >> > Portage tree and overlays: >> > [0] /usr/portage >> > [1] /var/lib/layman/myown >> > [?] indicates that the source repository could not be determined >> >> It's saying jabberd is being rebuilt, and orginally it was build from a >> repo that is ownknown, and now it will be built >> from /usr/lib/layman/myown. >> >> Did you previously rename your repo or pass PORTDIR_OVERLAY from the >> command line (which can sometimes confuse portage). >> >> >> >> >
