| 1 |
On Mon, 5 Aug 2013 21:10:27 -0400, Walter Dnes wrote: |
| 2 |
|
| 3 |
> > I can't remember what it was now, and it may have been avoidable by |
| 4 |
> > making virtual/udev-206 (or whichever version it was that needed a |
| 5 |
> > higher udev version than eudev could provide). It's moot now as eudev |
| 6 |
> > has been updated and portage is happy again, but it would be a |
| 7 |
> > concern if this happened regularly. |
| 8 |
> |
| 9 |
> I ran into this. Here is what I think happened... |
| 10 |
> |
| 11 |
> - I specified "sys-fs/eudev-1.2-r1-beta ~amd64" (or something similar) |
| 12 |
> in my /etc/portage/package.keywords file |
| 13 |
> - I ran "emerge --sync". On that particular day, it removed the beta |
| 14 |
> version ebuild, and replaced it with eudev-1.2.ebuild |
| 15 |
> - "emerge --changed-use --deep --update @world" could no longer find an |
| 16 |
> unmasked version of sys-fs/eudev that satisfied virtual/udev. So it |
| 17 |
> fell back to a version of sys-fs/udev |
| 18 |
> - My workaround, *UNTIL SUCH TIME AS EUDEV HITS STABLE AMD64*, is... |
| 19 |
> <sys-fs/eudev-9999 ~amd64 |
| 20 |
> in my /etc/portage/package.keywords file. |
| 21 |
> |
| 22 |
> This specifies to accept the highest ebuild number that is smaller |
| 23 |
> than 9999 (the "bleeding edge" version). |
| 24 |
|
| 25 |
nothing that complicated, I have nothing in package.{un,}mask for eudev. |
| 26 |
Something was pulling in virtual/udev-206, which no eudev releases at the |
| 27 |
time could satisfy (except possibly the 9999 version but those are masked |
| 28 |
by default) so portage needed to uinstall eudev and install udev to fulfil |
| 29 |
the dependency. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
Sisko:"I won't be condescending to you this episode, Dr. Bashir." |
Archives