Hi,

> > > We would now like to get rid of this bug. What do you recommend:
> > >  * keep a Debian specific implementation and tag this bug wontfix
> > >  * reapply the patch to fix this bug, and report bugs on the packages that
> > >    uses this "feature"
> > 
> > Could you document and wait until etch release?
> 
> 
> Etch release?
> 
> We already delayed this for sarge release.....then tried to fix it
> (badly as you know). I don't want bug reports rotting in the BTS. I
> have no idea of the shadow devel team healt in more than 1 year and I
> prefer we fixed as many bugs as possible while we can.
> 
> Are these changes *that* invasive for pbuilder?

The ideal way to approach this is to announce a change, 
document that change, provide some environmental variable
support for that change (like POSIXLY_CORRECT)

Then change.

We've got quite a bit of tools in sarge that doesn't work with
this change, right?



regards,
        junichi
-- 
[EMAIL PROTECTED],netfort.gr.jp}   Debian Project


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to