public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Mon, 16 Nov 2015 02:51:33 -0600	[thread overview]
Message-ID: <56499915.1010800@gmail.com> (raw)
In-Reply-To: <n2aqpk$ri6$1@ger.gmane.org>

Grant Edwards wrote:
> On 2015-11-15, Dale <rdalek1967@gmail.com> wrote:
>
>> 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.
> If the digest failures are for packages you don't have installed, just
> removing the entire directory for each of the broken manifests is one
> temporary work-around.
>


Thing is, one of the ones that fails is a package that I have
installed.  That would be busybox and I think that is likely on
everyone's system so this would affect every Gentoo system out there.  I
think I read on -dev somewhere a while back that busybox ended up being
pulled in as part of the @system profile/set. 

Anyway, I figure they will have a fix before to long.  I just find it
hard to believe that with all the planning that was put into this, the
changelogs and these issues were missed.  It's not like they decided to
change this over a short time frame.  They been working on this for
ages.  Live and learn I guess.  ;-)

Dale

:-)  :-) 



  reply	other threads:[~2015-11-16  8:51 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
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 [this message]
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=56499915.1010800@gmail.com \
    --to=rdalek1967@gmail.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