From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error
Date: Thu Aug 2 11:43:02 2001 [thread overview]
Message-ID: <20010802114250.A31039@cvs.gentoo.org> (raw)
In-Reply-To: <3B698F34.9070704@acm.org>; from chad.huneycutt@acm.org on Thu, Aug 02, 2001 at 01:34:44PM -0400
On Thu, Aug 02, 2001 at 01:34:44PM -0400, Chad M. Huneycutt wrote:
> >This was intentional so that are developers are reminded of bogus ebuilds. Chad
> >has already found a way to fix this (see the archives of about a week ago), but
> >to my knowledge no production ebuilds have yet been fixed.
> >
> Actually, I have fixed gzip and gdbm. I will fix the others by the end
> of this week. And I want to reiterate that all developers please look
> at my previous posts about info files and make sure they check any new
> ebuilds. I have seen a couple packages showing info errors lately.
Thanks, Chad. Yes, everyone should make sure that their new ebuilds don't install
bogus .info files.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-08-02 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15SG94-0004xg-00@cvs.gentoo.org>
2001-08-02 9:58 ` [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error Iain Craig
2001-08-02 10:06 ` Daniel Robbins
2001-08-02 10:19 ` [gentoo-dev] new-mirror Djamil ESSAISSI
2001-08-03 7:17 ` Djamil ESSAISSI
2001-08-02 11:39 ` [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error Chad M. Huneycutt
2001-08-02 11:43 ` Daniel Robbins [this message]
2001-08-02 12:56 ` Ben Lutgens
2001-08-03 6:54 ` Mikael Hallendal
2001-08-03 7:01 ` Chad M. Huneycutt
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=20010802114250.A31039@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.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