| 1 |
On Mon, 5 Jun 2006 11:53:07 -0300, Daniel da Veiga wrote: |
| 2 |
|
| 3 |
> > That would only be true if he had unmerged pam-login before running |
| 4 |
> > emerge world. Portage doesn't unmerge blockers itself. |
| 5 |
|
| 6 |
> I didn't say he or portage unmerged it, I said he got caught in the |
| 7 |
> conflict. |
| 8 |
|
| 9 |
Withoput unmerging it, the new shadow would not be merged, so that |
| 10 |
particular problem could not occur. |
| 11 |
|
| 12 |
> May be a config file update pending or maybe it was just in |
| 13 |
> the middle of the merge when the outage occured, either way the |
| 14 |
> commands would solve it or not?! |
| 15 |
> |
| 16 |
> And, of course, portage would stop and thus not do anything, so, I |
| 17 |
> assume he may have unmerged pam-login in order for the emerge -uD |
| 18 |
> world even start... |
| 19 |
|
| 20 |
I had assumed that anyone reporting a login problem would mention that |
| 21 |
they had just removed the pam-login package, which only goes to show that |
| 22 |
neither of us should make guesses as to what someone else has done :) |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
If weather bureaus were honest, they would call themselves non prophet |
| 29 |
organizations |
Archives