Dale <rdalek1...@gmail.com> wrote:
> Martin Vaeth wrote:
> > Neil Bothwick <n...@digimed.co.uk> wrote:
> >> I deleted the busybox directory from the tree then ran emerge --sync.
> >> The error is still there
> > You have the same files that I have.
> > Unfortunately, only now I actually did:
> >
> > $ grep busybox-9999 Manifest
> > EBUILD busybox-9999.ebuild 8580 [...]
> >
> > ???
> > I have the same wrong size recorded in the Manifest!
> > No idea why portage didn't yell at me - there seems
> > to be another bug involved.
> >
> > So, sorry, my previous conjecture was wrong.
> >
> > The only information which I can give you currently,
> > is that probably all mirrors contain the same broken Manifest
> > in the moment.
> >
> > *Perhaps* (a very wild conjecture!) the reason why this Manifest
> > got not updated is the same bug which caused portage not to yell
> > at me, despite the broken Manifest.
> >
> > As a temporary hack, calling "ebuild manifest" on that file is
> > probably the only reasonable way to proceed, but this problem
> > must be fixed, of course...
> >
> >
> >
>
>
> Wasn't there a emerge option to ignore the manifest? I seem to recall
> there used to be one but it was a LONG time ago. Of course, if someone
> has tinkered with something that would be a bad thing to do.
I thought I remembered something where the manifest no longer checks the
ebuild, just the file in distfiles -- I thought I remembered seeing this
somewhere. It was at a time when we got all the manifests all at once.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
