[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How unstable is hamm?

<chuckle>  Yep, that's it!  But additionally, there is some sort of
problem with comerr that I encounted and after trying to get dselect to
choose an acceptable solution I finally gave up and forced.

Obviously it is a problem for any sysadm when required functions move from
one package to another and dselect fails to complete the new installation
with a removal of the old.  One tends to fell "kinda left high and dry"
since the changes are not necessarily clear or obvious.


On Fri, 5 Dec 1997, David Gaudine wrote:

> On Fri, 5 Dec 1997, bleach wrote:
> > I have also had dselect "render" my system incapabile of a full boot a
> > couple of times following an install session.  The last being a couple of
> > days ago and was an fsck check failure.  Dselect had removed libcom_err
> > which it seem caused e2fsck to fail to load.  Dselect displayed a conflict
> > and I forced an override--it worked.  I am probably remiss in that I have
> > not bothered to record in detail exactly what happened.
> It was more like, e2fslibsg removed e2fsprogs but didn't install
> e2fsprogsg to replace it.  I did some pouting about that on another
> mailing list.  I think the bottom line is, if you use Hamm you're
> getting the latest features and the latest bugs, so you have to be
> a bit of a gambler; it's usually fine, but there's no guarantee
> that nobody uploaded a bad package today.

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: