From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: More ebuild failing (install step)
Date: Fri, 8 Sep 2006 00:08:13 -0700 [thread overview]
Message-ID: <7573e9640609080008x3e1d16bai4e4f8c1f40807eb3@mail.gmail.com> (raw)
In-Reply-To: <87hczj5vd0.fsf@newsguy.com>
On 9/7/06, reader@newsguy.com <reader@newsguy.com> wrote:
> "Richard Fish" <bigfish@asmallpond.org> writes:
>
> > This would be a real problem for install, as it would result in the
> > source tree being removed and recreated...obviuosly in an unconfigured
> > and uncompiled state.
> >
> > This is odd, and I'm still looking for the solution...
> >
>
> And may be why there is no recent ebuild of samba.
Nope. I get the same effect with samba-3.0.23a and samba-3.0.23, both
in the portage tree.
Looks like the problem comes from the samba-3-gentoo-0.3.14.tar.bz2
archive, which contains an entry for "./" dated from 2005-10-06. This
causes the work directory to have that date when the archive is
extracted, and confuses ebuild a bit because the distfile now has a
more recent date than workdir, so it thinks it needs to recreate
workdir.
You can work around this problem by running "ebuild ... merge",
"ebuild ... package", or just "emerge =net-fs/samba-3.0.23c".
http://bugs.gentoo.org/show_bug.cgi?id=146801
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-08 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 13:23 [gentoo-user] More ebuild failing (install step) reader
2006-09-06 20:24 ` Richard Fish
2006-09-07 1:57 ` [gentoo-user] " reader
2006-09-07 5:34 ` Richard Fish
2006-09-07 15:59 ` reader
2006-09-07 19:03 ` Richard Fish
2006-09-07 19:25 ` reader
2006-09-07 19:28 ` reader
2006-09-08 7:08 ` Richard Fish [this message]
2006-09-08 19:01 ` reader
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=7573e9640609080008x3e1d16bai4e4f8c1f40807eb3@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.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