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

Re: don't upgrade! libpam problem!



On 01-06-27 Emmanuel Charpentier wrote:
> Sam Hartmann uttered :
> >It's libpam-modules.  A fixed deb is in incoming now.  I'm really

> >sorry about thi; I screwed up between testing the patch and doing the
> >final build and introduced a typo.  Yes, I know I suck.  I will be
> >more careful in the future.

> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

> Don't you test your "final build" ? Of a *vital* package ?? If possible at 
> all, on a separate machine ??? Oh, my ...

So you believe that Sam never tested his package? What makes you believe
so? If while testing your package before creating the final .deb, you
can break it and don't notice.

> This kind of *imbecility* gives some *real* arguments to tenants of 
> commercial development. No need to FUD anybody here : this is *real* 
> mispractice. Expect a lot of flak from the commercial development side, and 
> don't fight it : it will have been *well* *earned*.

There's no need to flame Sam and other debian developers here. Everyone
of us is working on debian in his free time and doesn't get payed by you
or anyone else. 

> I wonder how much people have been permanently locked out of their *only* 
> machines by this shortsightedness ... Has someone an idea on how to count 
> them ?

No, but if your unstable, it's your problem. Unstable is exactly what
the  name says, unstable and sometimes broken. If you use it, you should
have enough knowledge to deal with problems like this. If not, then stop
using unstable and switch to either testing or even better stable.

Christian
-- 
           Debian Developer (http://www.debian.org)
1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853

Attachment: pgpmnStL6XFRq.pgp
Description: PGP signature


Reply to: