public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Mon, 16 Nov 2015 09:33:36 +0000	[thread overview]
Message-ID: <20151116093336.7bd41a38@digimed.co.uk> (raw)
In-Reply-To: <20151115173929.4f14ed80@a6>

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

On Sun, 15 Nov 2015 17:39:29 -0800, walt wrote:

> > 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...  
> 
> I did the same thing today (15 Nov) and it succeeded.
> 
> However, I ran the ebuild command on a non-broken ebuild.  Try
> repeating the same command on busybox 1.23.x or 1.24.x

Do you mean ebuild manifest? It doesn't matter which ebuild you run that
on, it creates a manifest for all ebuilds and files in the firsctory.

> I hope the gentoo devs will fix this bug before you have a chance to
> test my advice :)

According to https://bugs.gentoo.org/show_bug.cgi?id=565694 it has been
fixed, I synced too early this morning to pick that up.


-- 
Neil Bothwick

Be regular. Eat cron flakes.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-11-16  9:33 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
2015-11-16  1:39               ` walt
2015-11-16  9:33                 ` Neil Bothwick [this message]
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=20151116093336.7bd41a38@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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