> > I think it's stupid to change a completely built package to fix an > > obscure build bug. Really, what's the point. Conformance to the policy
I definitely disagree. Being able to build a package twice in a row is a release goal and rightfully so. Calling this obscure creates a bad taste in my mouth actually. > > for conformance's sake. The users will have to install an updated > > package with not a single bit changed. Right, but at least they will be able to install it. The alternative would have been to remove the package from testing. But then you might not care or want to see it in testing given that the -doc package is not available either. If so feel free to request its removal. I was under the impression the package should be in lenny. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
