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