| 1 |
On 16/11/2017 03:49, Ian Zimmerman wrote: |
| 2 |
> On 2017-11-15 18:40, Neil Bothwick wrote: |
| 3 |
> |
| 4 |
>> Why is it trying to install the 9999 version? Is that unmasked? |
| 5 |
>> |
| 6 |
>> Are you running stable or testing? |
| 7 |
>> |
| 8 |
>> What does "grep -r glibc /etc/portage" say? |
| 9 |
>> |
| 10 |
>> I don't think you posted the command that started all of this? |
| 11 |
> |
| 12 |
> For some reason, these horrible dependency dumps never seem to happen to |
| 13 |
> me. Why is that? Maybe because I run a "mostly stable" system? I do |
| 14 |
> have some very few "testing" packages enabled (ie. with ~amd64 flag). |
| 15 |
> They all fit into a single terminal screen. |
| 16 |
|
| 17 |
Running ~stable is likely the major reason, but of curse only you will |
| 18 |
ever know for sure. |
| 19 |
|
| 20 |
The whole point of ~arch[1] is to help get packages ready for stable. |
| 21 |
Unstable users find the dependency snags that the single maintainer |
| 22 |
can't weed out, we report them and log bugs and they get fixed. When the |
| 23 |
package is stabilized, most of those funny bugs ought to be gone and |
| 24 |
fixed. Yu mail can be read as proving that this system is working as |
| 25 |
intended :-) |
| 26 |
|
| 27 |
|
| 28 |
[1] It may or may not be documented to be this way, but it is how the |
| 29 |
larger community are mostly using it. |
| 30 |
|
| 31 |
-- |
| 32 |
Alan McKinnon |
| 33 |
alan.mckinnon@×××××.com |
Archives