| 1 |
On 12 December 2015 16:19:52 GMT+00:00, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 2 |
> On 12/12/15 18:02, Mike Gilbert wrote: |
| 3 |
> > On Sat, Dec 12, 2015 at 10:39 AM, Nikos Chantziaras |
| 4 |
> <realnc@×××××.com> wrote: |
| 5 |
> >> emerge -auDN @world |
| 6 |
> >> ... |
| 7 |
> >> [ebuild UD ] sys-boot/grub-2.00_p5107-r2 [2.02_beta2-r7] |
| 8 |
> >> USE="-custom-cflags%" GRUB_PLATFORMS="-yeeloong%" |
| 9 |
> >> |
| 10 |
> >> |
| 11 |
> >> I currently have 2.02_beta2-r7 installed. It's not masked or |
| 12 |
> anything. But |
| 13 |
> >> portage wants to downgrade to 2.00_p5107-r2. |
| 14 |
> >> |
| 15 |
> >> I don't have any clue why that is. |
| 16 |
> > |
| 17 |
> > Possibly a bad Manifest entry. rsync has been pretty broken this |
| 18 |
> week. |
| 19 |
> |
| 20 |
> Hm, indeed. grub-0.97-r16.ebuild was missing from the manifest, but |
| 21 |
> it's |
| 22 |
> weird that this would affect 2.02_beta2-r7. It shouldn't, right? |
| 23 |
|
| 24 |
If the manifest fails, all ebuilds in that directory are considered suspect. Is the version portage wants to downgrade to in an overlay? |
| 25 |
-- |
| 26 |
Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
Archives