The buildd-logs[1] don't provide enough debug information? I know this doesn't answer your question, but I assume the portability issues you mention are all build problems in one of Debian's supported architectures, am I right? If so, the build logs[1] should give you more then enough help to track your problems down before asking for another upload, and therefore triggering another buildd run.
I hope I haven't missunderstood anything =] [1] http://buildd.debian.org/build.php Cheers On Ter, 2003-05-27 at 11:55, Mike Schacht wrote: > Hello, > > I am not an official debian developer, but I maintain a couple of > packages. One of them, kdirstat, is already in the official > distribution. I intend to apply as a NM soon, but in the meantime, > since the last update of kdirstat, I am having portability problems. I > have no resources for confirming a fix the these problems. My sponser > has access to the developer machines and can reproduce the problems on > the other architectures, but hasn't had time to fix the failures or > test my fixes. > This list of debian machines: http://db.debian.org/machines.cgi, shows > that some of the machines allow access by "all". There is no further > explanation of who qualifies as "all", or how someone who is "all" can > get access. > > The debian-admin list is given at the Admin contact for these machines, > but subscriptions are not open and archives are not available. > > Can anyone tell me if I might qualify for access to these machines for > debugging packaging portability problem purposes, and if how, how to > get it. > > Thanks, > > Mike Schacht [EMAIL PROTECTED] -- Leo Costela <[EMAIL PROTECTED]> | <[EMAIL PROTECTED]> | <[EMAIL PROTECTED]> Key Fingerprint: 8AE6 CDFF 6535 192F B5B6 5921 2262 D36F 7ADF 9466 "you must cut down the mightiest tree in the forest... with... a herring!"
signature.asc
Description: This is a digitally signed message part
