| 1 |
On Wednesday, October 11, 2017 11:34:48 AM CEST John Covici wrote: |
| 2 |
> On Wed, 11 Oct 2017 04:50:20 -0400, |
| 3 |
> |
| 4 |
> J. Roeleveld wrote: |
| 5 |
> > On Wednesday, October 11, 2017 9:54:05 AM CEST John Covici wrote: |
| 6 |
> > > Hi. In my latest world update, I have sys-fs/zfs and friends at |
| 7 |
> > > 0.7.1 and they all want to update to 9999. Does anyone know why this |
| 8 |
> > > should be -- normally 9999 is not in the normal update sequence. |
| 9 |
> > > |
| 10 |
> > > I am using the unstable gentoo, updated about 3 weeks ago. No harm |
| 11 |
> > > has come yet, but I have not done the update till I can figure out |
| 12 |
> > > what is happening here -- particularly if I need a rescue cd which is |
| 13 |
> > > using zfs 0.7.1. |
| 14 |
> > > |
| 15 |
> > > Thanks in advance for any ideas. |
| 16 |
> > |
| 17 |
> > check your keywords, how did you unmask zfs? |
| 18 |
> > |
| 19 |
> > Here are mine: |
| 20 |
> > |
| 21 |
> > $ grep -r zfs /etc/portage |
| 22 |
> > /etc/portage/sets/zfs:sys-fs/zfs |
| 23 |
> > /etc/portage/sets/zfs:sys-fs/zfs-kmod |
| 24 |
> > /etc/portage/package.keywords/zfs:=sys-fs/zfs-kmod-0.7.1 ~amd64 |
| 25 |
> > /etc/portage/package.keywords/zfs:=sys-fs/zfs-0.7.1 ~amd64 |
| 26 |
> > $ grep -r spl /etc/portage |
| 27 |
> > /etc/portage/sets/zfs:sys-kernel/spl |
| 28 |
> > /etc/portage/package.keywords/zfs:=sys-kernel/spl-0.7.1 ~amd64 |
| 29 |
> |
| 30 |
> Yep, I think you are correct, I had the 9999 in package.keywords and I |
| 31 |
> think this is what made portage do that. |
| 32 |
> When I commented them out, things are back to normal. |
| 33 |
> |
| 34 |
> Thanks again. |
| 35 |
|
| 36 |
That might have happened automatically as portage tends to want to unmask the |
| 37 |
latest version if it can't find an unmasked version that matches requirements. |
| 38 |
|
| 39 |
I always answer "no" to those requests and copy/paste the actual lines myself |
| 40 |
after checking they are really what I want. |
| 41 |
|
| 42 |
-- |
| 43 |
Joost |
Archives