Re: [Pkg-shadow-devel] Bug#276419: [Pbuilder-maint] Shall Debian's su conform to other implementations
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]
Re: Bug#276419: [Pkg-shadow-devel] Bug#276419: [Pbuilder-maint] Shall Debian's su conform to other implementations
The ideal way to approach this is to announce a change, Which is what we are doing now. We neglected to do so the first time (mostly because we didn't anticipate this would break pbuilder so much) and this is why we reverted the change very quickly. document that change, provide some environmental variable It will be documented. We have a ready document, written by the original bug reporter, which documents the changes and gives recommendations for fixing affected usage of su. We didn't want to send it now because it's a long and deeply technical document and we first wanted to get input from people, like you, who are already aware of the issue. 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? From what Nicolas investigated, not that much. He only found dchroot and pbuilder up to now. Nicolas does not pretend to have a complete investigation but I trust him when he mentions he tried as widely as possible. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#276419: [Pkg-shadow-devel] Bug#276419: [Pbuilder-maint] Shall Debian's su conform to other implementations
Hi, 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? From what Nicolas investigated, not that much. He only found dchroot and pbuilder up to now. Nicolas does not pretend to have a complete investigation but I trust him when he mentions he tried as widely as possible. FWIW, pbuilder in sid is fixed since 0.129 (17 August 2005), and I am hoping that will probagate into some stable backports, so that practically, pbuilder side is ready for the new su. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#276419: [Pkg-shadow-devel] Bug#276419: [Pbuilder-maint] Shall Debian's su conform to other implementations
FWIW, pbuilder in sid is fixed since 0.129 (17 August 2005), and I am hoping that will probagate into some stable backports, so that practically, pbuilder side is ready for the new su. Well, this is actually great news as pbuilder was by far the main blocker for this change. Sorry for having bugged you, then. (removing Junichi and the pbuilder list from CC) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Pbuilder-maint] Shall Debian's su conform to other implementations
Hi, Unfortunately, this broke pbuilder (see #317264), and other Debian packages (e.g. dchroot). So this patch was (at least temporarily) removed, and the current behavior documented. 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? regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-shadow-devel] Bug#276419: [Pbuilder-maint] Shall Debian's su conform to other implementations
Quoting Junichi Uekawa ([EMAIL PROTECTED]): 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? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]