| 1 |
On Fri, Dec 7, 2018 at 5:48 AM Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
> |
| 3 |
> On Friday, 7 December 2018 10:17:17 GMT Andreas Fink wrote: |
| 4 |
> > On Fri, 07 Dec 2018 10:14:45 +0000 |
| 5 |
> > |
| 6 |
> > Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 7 |
> > > And today, of course, there's an upgrade. That's another reason I |
| 8 |
> > > ditched it. Is there a way to force chromium to be not ~amd64 on a |
| 9 |
> > > ~amd64 system? |
| 10 |
> > |
| 11 |
> > Yes, I do that with this entry in /etc/portage/package.keywords: |
| 12 |
> > www-client/chromium -~amd64 |
| 13 |
> |
| 14 |
> Ah, yes, of course. Ta muchly. |
| 15 |
> |
| 16 |
|
| 17 |
You'll be doing a build shortly in any case: |
| 18 |
https://bugs.gentoo.org/672606 |
| 19 |
|
| 20 |
So, I'd hold off on any upgrades/downgrades/etc for a day or so until |
| 21 |
this hits if CPU time matters to you. |
| 22 |
|
| 23 |
-- |
| 24 |
Rich |
Archives