From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Sun, 15 Nov 2015 15:29:47 -0500 [thread overview]
Message-ID: <1673.1447619387@ccs.covici.com> (raw)
In-Reply-To: <5648E8C3.5090509@gmail.com>
Dale <rdalek1967@gmail.com> wrote:
> Martin Vaeth wrote:
> > Neil Bothwick <neil@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
covici@ccs.covici.com
next prev parent reply other threads:[~2015-11-15 20:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:07 [gentoo-user] All sorts of digest verification failures Grant Edwards
2015-11-12 16:19 ` wabenbau
2015-11-12 16:42 ` [gentoo-user] " Grant Edwards
2015-11-12 16:45 ` Alan McKinnon
2015-11-12 16:54 ` Peter Humphrey
2015-11-15 9:59 ` Alan Mackenzie
2015-11-15 10:22 ` Matti Nykyri
2015-11-15 10:43 ` Peter Humphrey
2015-11-15 10:56 ` Matti Nykyri
2015-11-15 11:44 ` Peter Humphrey
2015-11-15 11:01 ` Alan Mackenzie
2015-11-15 11:15 ` Matti Nykyri
2015-11-15 19:33 ` Alan Mackenzie
2015-11-15 21:43 ` Matti Nykyri
2015-11-15 10:41 ` Neil Bothwick
2015-11-15 11:42 ` Neil Bothwick
2015-11-15 14:56 ` Martin Vaeth
2015-11-15 17:17 ` Neil Bothwick
2015-11-15 19:05 ` Martin Vaeth
2015-11-15 20:19 ` Dale
2015-11-15 20:29 ` covici [this message]
2015-11-15 21:02 ` Simon Thelen
2015-11-16 6:45 ` Martin Vaeth
2015-11-16 7:33 ` covici
2015-11-16 17:21 ` Martin Vaeth
2015-11-16 21:49 ` Marc Joliet
2015-11-16 22:32 ` Rich Freeman
2015-11-17 7:09 ` Marc Joliet
2015-11-15 20:43 ` Grant Edwards
2015-11-16 8:51 ` Dale
2015-11-16 1:39 ` walt
2015-11-16 9:33 ` Neil Bothwick
2015-11-16 9:48 ` Dale
2015-11-16 13:53 ` Neil Bothwick
2015-11-15 19:29 ` Alan Mackenzie
2015-11-12 16:59 ` Dale
2015-11-12 16:33 ` [gentoo-user] " Dale
2015-11-16 0:06 ` Dale
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=1673.1447619387@ccs.covici.com \
--to=covici@ccs.covici.com \
--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