public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Preissler <tomjohn@gmx.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Creating digest for new subtree fails
Date: Mon, 9 Dec 2002 14:42:21 +0100	[thread overview]
Message-ID: <20021209134221.GA2222@zeus.tpfm.de> (raw)
In-Reply-To: <003d01c29f5c$aeed7380$fd0010ac@voyager>

* Martin Cooper wrote on 09 Dec 2002:

> 
> ----- Original Message -----
> From: "Thomas Preissler" <tomjohn@gmx.de>
> To: <gentoo-dev@gentoo.org>
> Sent: Sunday, December 08, 2002 1:34 PM
> Subject: [gentoo-dev] Creating digest for new subtree fails
> 
> 
> > Hello,
> >
> > I just made an opera-shared-6.11 ebuild. The problem is, that
> > portage/net-www/opera-shared does not exist, so I created it and put
> > my ebuild there.
> >
> > Creating the digest fails with this message:
> >
> <snip>
> 
> Hi,
>     I had the same problem, so I did an 'emerge portage' then added the
> following setting to /etc/make.conf :-
> 
>     PORTDIR_OVERLAY=/usr/local/portage
> 
> Not sure the emerge of portage actually made any difference, but after
> performing both steps, everything worked as expected.

Oh, my problem was, that I used emerge instead of ebuild.


Greetz,
Tom

-- 
Preissler Thomas                       Registered Linux User #265745
GPG-Key: 1024D/C21DAB7F                       http://counter.li.org/

printk("Entering UltraSMPenguin Mode...\n");
	2.2.16 /usr/src/linux/arch/sparc64/kernel/smp.c

--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2002-12-09 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 13:34 [gentoo-dev] Creating digest for new subtree fails Thomas Preissler
2002-12-08 18:20 ` [gentoo-dev] SOLVED (was: Re: [gentoo-dev] Creating digest for new subtree fails) Thomas Preissler
2002-12-09  8:26 ` [gentoo-dev] Creating digest for new subtree fails Martin Cooper
2002-12-09 13:42   ` Thomas Preissler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021209134221.GA2222@zeus.tpfm.de \
    --to=tomjohn@gmx.de \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox