public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Smith <chris.rs@xtra.co.nz>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New cvs.eclass
Date: Sun, 20 Apr 2003 10:42:05 +1200	[thread overview]
Message-ID: <200304201042.05354.chris.rs@xtra.co.nz> (raw)
In-Reply-To: <200304191404.52622.danarmak@gentoo.org>

On Sunday 20 April 2003 02:04, Dan Armak wrote:
> On Friday 18 April 2003 14:11, Dan Armak wrote:
> > Hello everyone,
> >
> > I've rewritten cvs.eclass. I'll test all cvs euilds once again now and
> > then commit the new eclass and ebuilds if noone objects. Extra testing
> > from
>
> anyone
>
> > else welcome.
>
> No objections recieved and everything tests out ok. I'll commit it in a few
> minutes, and update the kde-cvs page accordingly.

Hi Dan,

When I try and emerge the CVS Kopete (using your latest ebuilds) I get this 
output here:

--snip--
chris local # PORTDIR_OVERLAY=/usr/local/portage emerge kopete
Calculating dependencies ...done!
>>> emerge (1 of 1) net-im/kopete-5 to /
>>> Unpacking source...
 * Running cvs -q -f -z4 update -dP with anoncvs.kde.org:/home/kde for 
kopete/...
cvsro server: cannot open directory /home/kde/kopete: No such file or 
directory
cvsro server: skipping directory
 * Copying kopete/ from /usr/portage/distfiles/cvs-src/kde...
/usr/sbin/ebuild.sh: line 126: cd: //usr/portage/distfiles/cvs-src/kde/kopete: 
No such file or directory
 * Running cvs -q -f -z4 update -dP with anoncvs.kde.org:/home/kde for 
kde-common/admin...
U ChangeLog
U Doxyfile.am
U Doxyfile.global
U Makefile.common
U acinclude.m4.in
U am_edit
U compile
U conf.change.pl
U config.guess
U config.pl
U config.sub
U configure.in.bot.end
U configure.in.min
U cvs-clean.pl
U cvs.sh
U debianrules
U depcomp
U detect-autoconf.sh
U install-sh
U libtool.m4.in
U ltmain.sh
U missing
U mkinstalldirs
U nmcheck
U ylwrap
 * Copying kde-common/admin from /usr/portage/distfiles/cvs-src/kde...
>>> Source unpacked.
grep: Makefile.am: No such file or directory
*** Creating aclocal.m4
aclocal: `configure.ac' or `configure.in' is required
make: *** [cvs] Error 1

!!! ERROR: net-im/kopete-5 failed.
!!! Function kde_src_compile, Line 107, Exitcode 1
!!! no configure script found, generation unsuccessful
--snip--

Any Ideas? To state the obvious, it's looking in /home/kde on the CVS server 
for some reason, which is why it would fail. But why is it doing that?

-- 
Removing the straw that broke the camel's back does not necessarily
allow the camel to walk again.



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-19 22:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 14:11 [gentoo-dev] New cvs.eclass Dan Armak
2003-04-18 14:18 ` [gentoo-dev] Re: [gentoo-core] " Dan Armak
2003-04-18 14:21   ` Dan Armak
2003-04-18 14:27     ` Peter Ruskin
2003-04-18 14:46       ` Dan Armak
2003-04-18 19:40         ` John Ziniti
2003-04-18 18:49           ` Norberto BENSA
2003-04-18 17:30     ` Norberto BENSA
2003-04-19 20:18       ` Dan Armak
2003-04-19 14:04 ` [gentoo-dev] " Dan Armak
2003-04-19 22:42   ` Chris Smith [this message]
2003-04-20  2:44     ` Dan Armak
2003-04-19 17:50 ` Alexander Futasz
2003-04-19 21:40   ` Dan Armak
2003-04-19 21:43     ` Dan Armak

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=200304201042.05354.chris.rs@xtra.co.nz \
    --to=chris.rs@xtra.co.nz \
    --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