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: Why does portage want to downgrade Grub?
Date: Sat, 12 Dec 2015 22:56:23 +0000	[thread overview]
Message-ID: <3D717B2A-1CB9-4DA8-B96D-E08602AD28B4@digimed.co.uk> (raw)
In-Reply-To: <n4hhf8$hlm$1@ger.gmane.org>

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

On 12 December 2015 16:19:52 GMT+00:00, Nikos Chantziaras <realnc@gmail.com> wrote:
> On 12/12/15 18:02, Mike Gilbert wrote:
> > On Sat, Dec 12, 2015 at 10:39 AM, Nikos Chantziaras
> <realnc@gmail.com> wrote:
> >>    emerge -auDN @world
> >>    ...
> >>    [ebuild     UD ] sys-boot/grub-2.00_p5107-r2 [2.02_beta2-r7]
> >> USE="-custom-cflags%" GRUB_PLATFORMS="-yeeloong%"
> >>
> >>
> >> I currently have 2.02_beta2-r7 installed. It's not masked or
> anything. But
> >> portage wants to downgrade to 2.00_p5107-r2.
> >>
> >> I don't have any clue why that is.
> >
> > Possibly a bad Manifest entry. rsync has been pretty broken this
> week.
> 
> Hm, indeed. grub-0.97-r16.ebuild was missing from the manifest, but
> it's 
> weird that this would affect 2.02_beta2-r7. It shouldn't, right?

If the manifest fails, all ebuilds in that directory are considered suspect. Is the version portage wants to downgrade to in an overlay? 
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1566 bytes --]

  reply	other threads:[~2015-12-12 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 15:39 [gentoo-user] Why does portage want to downgrade Grub? Nikos Chantziaras
2015-12-12 16:02 ` Mike Gilbert
2015-12-12 16:19   ` [gentoo-user] " Nikos Chantziaras
2015-12-12 22:56     ` Neil Bothwick [this message]
2015-12-13  2:44       ` Nikos Chantziaras

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=3D717B2A-1CB9-4DA8-B96D-E08602AD28B4@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