On Thu, Mar 10, 2016 at 4:47 AM, Aaron M. Ucko <u...@debian.org> wrote: > "László Böszörményi (GCS)" <g...@debian.org> writes: >> Then I have to update the changelog closing the bugreport and rebuild >> the package. :) > > I do see how that could get a little frustrating. It's too bad there's > no lightweight way for you to publicly indicate awareness of a build > failure short of filing a report yourself. I can send you an email in advance.
>> No problem, next time I should wait more on you to file the bugreport. > > You know, you could also perform more sanity checks *before* > uploading... ;-) My machine is so old that I'm happy it works and compiles packages once in a reasonable time. But sure, there's ccache and I should have realized documentation is built in the indep targets only - that buildds don't execute. It was degrading when I've patched a problem in an upstream source and started compiling. While it was going, I've sent the patch upstream. Some time later I got the answer, he patched the source, compiled and tested the issue which is fine now. My box was still compiling that source... :-/ I will be able to buy a new one this summer or autumn. You are still right, I should do more sanity checks before uploading. Offtopic: as I know, DebConf'17 will be close to you. Any plans to attend it? Regards, Laszlo/GCS
