Mailing List Archive

Hi,
On нд, 2004-10-24 at 11:38 -0500, Kris Kerwin wrote:
> Hi,
>
> I just ran 'emerge sync', which promptly deleted the following files and
> directories:
>
> $PORTDIR/overlay/
> $PORTDIR/tmp/
> $PORTDIR/tmp/timestamp.chk
>
Look in /etc/make.conf and uncomment PORTDIR_OVERLAY=/usr/local/portage
or change it if you wish (not recommended, no reason to do this). Then
do: #mkdir /usr/local/portage to create it. Put your ebuilds inside.
Otherwise when doing emerge sync (rsync portage-tree) it does sync both
ways adds AND removed from your $PORTDIR-tree - so your changes are
deleted. Overlay must be kept between emerges.
HTH
> When emerge attempts updating the portage cache, it quickly fails because
> these files/directories nolonger exist.
>
> Simply running 'mkdir overlay; mkdir tmp' fixes the problem. But while running
> 'emerge sync' again, emerge removes the files.
>
> I'm currently using portage version 2.0.51-r2.
>
> Thanks for the help.
>
> Kris Kerwin
>
> --
> gentoo-user@gentoo.org mailing list
>
--
Rumen Yotov <rumen_yotov@dir.bg>

I thought that PORTDIR_OVERLAY was supposed to be:

PORTDIR_OVERLAY=$PORTDIR/overlay/

Is this true?

Thanks in advance.

Kris Kerwin

On Sunday 24 October 2004 3:00 pm, Rumen Yotov wrote:
> Hi,
>
> On нд, 2004-10-24 at 11:38 -0500, Kris Kerwin wrote:
> > Hi,
> >
> > I just ran 'emerge sync', which promptly deleted the following files and
> > directories:
> >
> > $PORTDIR/overlay/
> > $PORTDIR/tmp/
> > $PORTDIR/tmp/timestamp.chk
>
> Look in /etc/make.conf and uncomment PORTDIR_OVERLAY=/usr/local/portage
> or change it if you wish (not recommended, no reason to do this). Then
> do: #mkdir /usr/local/portage to create it. Put your ebuilds inside.
> Otherwise when doing emerge sync (rsync portage-tree) it does sync both
> ways adds AND removed from your $PORTDIR-tree - so your changes are
> deleted. Overlay must be kept between emerges.
> HTH
>
> > When emerge attempts updating the portage cache, it quickly fails because
> > these files/directories nolonger exist.
> >
> > Simply running 'mkdir overlay; mkdir tmp' fixes the problem. But while
> > running 'emerge sync' again, emerge removes the files.
> >
> > I'm currently using portage version 2.0.51-r2.
> >
> > Thanks for the help.
> >
> > Kris Kerwin
> >
> > --
> > gentoo-user@gentoo.org mailing list

--
gentoo-user@gentoo.org mailing list

I thought that PORTDIR_OVERLAY was supposed to be:

PORTDIR_OVERLAY=$PORTDIR/overlay/

Is this true?

Thanks in advance.

Kris Kerwin

On Sunday 24 October 2004 3:00 pm, Rumen Yotov wrote:
> Hi,
>
> On нд, 2004-10-24 at 11:38 -0500, Kris Kerwin wrote:
> > Hi,
> >
> > I just ran 'emerge sync', which promptly deleted the following files and
> > directories:
> >
> > $PORTDIR/overlay/
> > $PORTDIR/tmp/
> > $PORTDIR/tmp/timestamp.chk
>
> Look in /etc/make.conf and uncomment PORTDIR_OVERLAY=/usr/local/portage
> or change it if you wish (not recommended, no reason to do this). Then
> do: #mkdir /usr/local/portage to create it. Put your ebuilds inside.
> Otherwise when doing emerge sync (rsync portage-tree) it does sync both
> ways adds AND removed from your $PORTDIR-tree - so your changes are
> deleted. Overlay must be kept between emerges.
> HTH
>
> > When emerge attempts updating the portage cache, it quickly fails because
> > these files/directories nolonger exist.
> >
> > Simply running 'mkdir overlay; mkdir tmp' fixes the problem. But while
> > running 'emerge sync' again, emerge removes the files.
> >
> > I'm currently using portage version 2.0.51-r2.
> >
> > Thanks for the help.
> >
> > Kris Kerwin
> >
> > --
> > gentoo-user@gentoo.org mailing list

--
gentoo-user@gentoo.org mailing list

Hi,
On нд, 2004-10-24 at 16:10 -0500, Kris Kerwin wrote:
> I thought that PORTDIR_OVERLAY was supposed to be:
>
> PORTDIR_OVERLAY=$PORTDIR/overlay/
>
> Is this true?
>
Of course not. If you do it this way after every rsync (emerge sync) you
lost the overlay contents (and changes) and have to put them again.
IMO the logic of the overlay is to have some ebuilds different from
these in portage (new, changed, edited, etc) so they must be persistent.
See again the reasons below.
HTH
> Thanks in advance.
>
> Kris Kerwin
>
> On Sunday 24 October 2004 3:00 pm, Rumen Yotov wrote:
> > Hi,
> >
> > On нд, 2004-10-24 at 11:38 -0500, Kris Kerwin wrote:
> > > Hi,
> > >
> > > I just ran 'emerge sync', which promptly deleted the following files and
> > > directories:
> > >
> > > $PORTDIR/overlay/
> > > $PORTDIR/tmp/
> > > $PORTDIR/tmp/timestamp.chk
> >
> > Look in /etc/make.conf and uncomment PORTDIR_OVERLAY=/usr/local/portage
> > or change it if you wish (not recommended, no reason to do this). Then
> > do: #mkdir /usr/local/portage to create it. Put your ebuilds inside.
> > Otherwise when doing emerge sync (rsync portage-tree) it does sync both
> > ways adds AND removed from your $PORTDIR-tree - so your changes are
> > deleted. Overlay must be kept between emerges.
> > HTH
> >
> > > When emerge attempts updating the portage cache, it quickly fails because
> > > these files/directories nolonger exist.
> > >
> > > Simply running 'mkdir overlay; mkdir tmp' fixes the problem. But while
> > > running 'emerge sync' again, emerge removes the files.
> > >
> > > I'm currently using portage version 2.0.51-r2.
> > >
> > > Thanks for the help.
> > >
> > > Kris Kerwin
> > >
> > > --
> > > gentoo-user@gentoo.org mailing list
>
> --
> gentoo-user@gentoo.org mailing list
>
--
Rumen Yotov <rumen_yotov@dir.bg>

On Sun, 2004-10-24 at 16:10 -0500, Kris Kerwin wrote:
> I thought that PORTDIR_OVERLAY was supposed to be:
>
> PORTDIR_OVERLAY=$PORTDIR/overlay/
>
> Is this true?
>

No, it will be cleared on sync. Evident by your problem :-)


--
Tom Wesley <tom@tomaw.org>

On Sun, 24 Oct 2004, Kris Kerwin wrote:

> I just ran 'emerge sync', which promptly deleted the following files and
> directories:
>
> $PORTDIR/overlay/
> $PORTDIR/tmp/
> $PORTDIR/tmp/timestamp.chk

That's right - this is exactly what rsync is supposed to do.

If you want to setup a local portage then put your stuff in
/usr/local/portage and set PORTAGE_OVERLAY in /etc/make.conf.


--
deckle /dek'l/ n.

[.from dec- and nybble; the original
spelling seems to have been `decle'] Two nickles; 10
bits. Reported among developers for Mattel's GI 1600 (the
Intellivision games processor), a chip with 16-bit-wide RAM but
10-bit-wide ROM. See nybble for other such terms.


--
gentoo-user@gentoo.org mailing list

On Sun, 24 Oct 2004, Kris Kerwin wrote:

> I thought that PORTDIR_OVERLAY was supposed to be:
>
> PORTDIR_OVERLAY=$PORTDIR/overlay/
>
> Is this true?

No, the overlay is for you to put your *own* stuff so that a sync doesn't
blow those changes away. Thus, by definition it has to be in a different
place (which is /usr/local/portage by convention).

Understand that when you sync your portage against a mirror you are asking
for your portage tree to match the mirror and so files are added and
removed as appropriate - since /usr/portage/overlay doesn't exist on the
mirror it will be deleted.


--
This can't happen

Less clipped variant of can't happen.


--
gentoo-user@gentoo.org mailing list