Pretty please. Send this as a bug report to [EMAIL PROTECTED]
Sending it here means that all of this important background data is not going to be tracked in the bug tracking system. From this point further I am not going to respond to this issue on this list.
Jeffrey Altman Lars Richter wrote:
Jeffrey Altman schrieb:A minidump in this case is not going to be useful because the relevant information is the panic data plus a description of how to reproduce the problem.Ok! I thought it could help!A public test case isn't possible, because we don't have a public cell.Then you have to provide enough details to permit me to reconstruct the test environment so that the problem can be reproduced.Here are the links we use: This is the link without problems, which I made by hand.pd_cpp_flexlm.h -> /afs/pd-ef.ef/buildbot/BUILD/HEAD_TMP/tools/license/cpp/library/src/../include/pd_cpp_flexlm.hThis is one link which is created by scripts, which we have problems with.pd_cpp_flexlm.h -> /afs/pd-ef.ef/buildbot/BUILD/HEAD_TMP/tools/license/cpp/library/src/../../libraray/include/pd_cpp_flexlm.hA shorter link of the same kind works without problems. README -> /afs/pd-ef.ef/tmp/ril/sw/php/../../README.txtI ask only so I can determine what priority to associate with the bug.If this is a minor inconvenience I am not going to rush out a new general release.It is not really critical. But we need a solution in further clients, because we don't want to stick in older releases. The only problem is, that I have to downgrade some systems to 1.5.21 in the build environment.Regards, Lars _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
