repoen 23618 stop I'm sorry, but saying that I should not use debmake because it is buggy does not fix the bug and the bug should not be closed!
Corrupting files in packages that I am building is very serious indeed, and if I didn't set the severity to important or greater, I probably should have. debstd issues no warnings about it, and it took me several hours to figure out the problem, since this is a package with a source tree of over 100 megs and each rebuild takes in excess of 30 minutes. (Not only that, but the install method is complex and I looked everywhere else first, assuming that "it could not possibly be debstd") Santiago Vila <[EMAIL PROTECTED]> writes: > debstd is not supposed to guess that. stripping a library using > just strip --strip-debug is ok for 95% of cases, if your case is in the > remaining 5%, then the debstd provided by debmake is not suitable for your > package. I would suggest either: > > a) debstd-ize your debian/rules Eh? debian/rules already uses debstd. > b) copy debstd to your debian directory and change the debstd invocation > by "debian/debstd" (probably adding a chmod +x debian/debstd in the build > target). Then you can fine-tune your own debstd according to the special > requirements of your package. OK, this could be a possibility then -- comment out that part. But still, I don't think it's a good solution to require me to hack the source. Further, there is no documentation anywhere that indicates that debstd may corrupt files. > I do not consider this to be a bug in debstd. You are welcome to reassign it to the appropriate package (binutils?) then, but it is not fixed and should not be closed. -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | ----------------------------------------------------------------------------+ Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]